Contained in this Manual

Contained in this Manual
	Introduction

This manual includes instructions on how to:

Deploy Mr. XML Publisher using Tomcat 6.0.x.
Tomcat is the most popular web container and is used in several JEE application servers. See Deploying to Tomcat.
Configure Mr. XML Publisher on Linux to use DocBook XML, DocBook XSL, uploaded DocBook XSL customization layers, and the libxml2 tools.
You can use Mr. XML Publisher with any XSLT processor (Saxon, Xalan, xsltproc, etc.) and with any operating system that supports a web container at version 2.4 of the Java Servlet specification (or greater). The combination of Linux, Tomcat, DocBook XML, DocBook XSL, and the libxml2 tools provides a good fit for Mr. XML Publisher. Thus, it is the environment used for most of this manual's examples.^[2] For details, see Server Administration.
Specify the formats offered by the server.
Processing for each format offered in the user interface is implemented via a series of commands in a tool chain, which in Mr. XML Publisher administration lingo is called a "command array." Each format's command array is specified in a <context-param> element within Mr. XML Publisher's web.xml file. When formatting an uploaded XML project, each command in a format's command array is run in turn as an external subprocess. The output of each command becomes the input of the next. See Command Arrays: Special web.xml <context-param> Elements and COMMAND Arrays .
Control the ENVIRONMENT in which each command runs.
Each command can be run in a unique, custom ENVIRONMENT, and you can use all legal switches and options for a command. See COMMAND Arrays and ENVIRONMENTs.
Control Mr. XML Publisher using its web.xml file.
The web.xml file contains many <context-param> elements used for administration and configuration. For example, you can:
- Set a size limit for uploaded project archives.
- Allow/disallow files in projects based on mime-types.
- Set limits on data pulled from databases (size, timeout, etc.).
- Turn on/off internal JDBC connection pooling.
- Set ownership and permissions on files in unpacked projects prior to processing.
- Choose whether to retain uploaded project files on disk after servicing a request (for specific users or for all users).
The <context-param> elements in Mr. XML Publisher' web.xml file are discussed in detail in web.xml <context-param>s.
Customize the user interface.
The user interface is built with HTML, JSP, Java applets, CSS, and JavaScript. All files used to build the user interface are provided as source code. None are initially shrunk or obfuscated. Thus, they can be easily modified. See User Interface Customization.
Control logging.
Mr. XML Publisher uses the Apache Software Foundation's log4j package to provide logging services. See Logging.

^[2]Mr. XML Publisher is optimized for DocBook XML. Other DTDs and schemas are supported only through special arrangements and customization of server-side class files.