You may need to perform the following tasks; however, this manual does not include instructions on how to:
Deploy Mr. XML Publisher to JEE application servers.
If you are deploying Mr. XML Publisher to a JEE application server, you must know the deployment details of your server. Mr. XML Publisher has been successfully deployed and tested on the following JEE application servers:
JBoss 4.2.1.GA
IBM WebSphere Application Server 6.1
BEA WebLogic Server 10.0
GlassFish V2 / Sun Java System Application Server 9.1
Geronimo 2.0.1 (both Jetty6 and Tomcat6)
Suggestions for deploying to each JEE application server on which Mr. XML Publisher has been tested are provided in Deploying to a JEE Application Server.
Compile/install/configure your XML tools.
Mr. XML Publisher can use any executable in your XML tool chains, but you must compile/install/configure each tool according to its documentation. Most Linux distributions give you the option of installing some of the XML tools you need. Windows systems usually do not include them.
Set up an XML Catalog system.
Many Linux distributions install at least a partly working XML Catalog system. On Windows, usually no XML Catalog system is installed. You must make sure that your server's XML Catalog system is working prior to deploying Mr. XML Publisher.
Write XSL.
Mr. XML Publisher does not include any XSL. You must write your own XSL or use XSL provided for you. The DocBook XSL distribution provides a great deal of value at no cost.
Implement user authentication and authorization in your web container or JEE application server.
If you wish to enforce user authentication and/or authorization, you must know how to do that using a web.xml file and the security facilities provided by your web container or JEE server. Mr. XML Publisher can use authentication and/or authorization; however, to activate them, you must at least be knowledgeable of web app security as implemented in a web.xml file. Additionally, you may need to know details of an LDAP server or relational database server used in your organization's authentication process.
Configure and/or optimize your server's networking.
Unless you specifically turn it off, database connection pooling in Mr. XML Publisher is automatic. By default, Mr. XML Publisher logs the time taken to create each file whose data is pulled from a data store. Suggestions on how to maximize your server's networking performance are provided in Hardware and System Optimizations.