| External Applications | ||
|---|---|---|
 | Deployment |  |
| External Applications | ||
|---|---|---|
| | Deployment | |
Mr. XML Publisher transforms XML into formatted output using command-line tools, such as the libxml2 tools (http://xmlsoft.org/), or Java-based XML processing tools, such as the Xerces Java parser and Saxon (http://xerces.apache.org/xerces-j/, http://saxon.sourceforge.net/). The command arrays that perform the transformations need access to whatever tools you are using. Those tools must exist on the server and on the path of the user who owns the web container or JEE server process.
The cost of your Mr. XML Publisher software license included limited support for setting up your server's initial formats and the command arrays that implement the processing behind those formats. However, after installation, you need to take control yourself.
Any application or script that can be executed from the command line can be used by Mr. XML Publisher, including executable binaries, shell scripts, ant scripts, Perl scripts, etc. Details on how that is done are covered in COMMAND Arrays . If your server does not have installed the command-line tools used in XML processing tool chains, it is recommended that you install the libxml2 tools.
Source code for the libxml2 tools can be downloaded from: http://xmlsoft.org/. Precompiled libxml2 binaries for Windows are available at: http://www.zlatkovic.com/libxml.en.html.
In addition to an XSL transformer, depending on the formats the server will offer, you may need to install additional XML processing software. You might consider the following:
JavaHelp — http://java.sun.com/javase/technologies/desktop/javahelp/download_binary.html
Windows HTML Help Workshop — http://www.microsoft.com/downloads/
To provide HTML Help formatting from a Linux/Unix server, consider installing Wine. You would install the Windows HTML Help Workshop in Wine and then run the HTML Help compiler as a command-line option to Wine. See HTML Help COMMAND Array for Linux/Unix for an example. More information on Wine is at: http://www.winehq.org/.
Plain Text — http://elinks.or.cz/
The key to getting your XML processing tool chains to work from within Mr. XML Publisher is to first get them working from your server's command line.
Although Mr. XML Publisher itself does not require access to an XML Catalog system, many XML processing tools do. You will almost certainly need to ensure that you have a working XML Catalog system available to the XML tools on your server.
If you find that an XML Catalog system is not installed and properly configured on your server, one of the best available resources to help with the task is Bob Stayton's excellent book, DocBook XSL: The Complete Guide. Its discussion of XML Catalog systems can be applied in general, not just to DocBook. The entire book can be read online (http://www.sagehill.net/docbookxsl/). The chapter on XML Catalog systems is at: http://www.sagehill.net/docbookxsl/Catalogs.html.
Most Linux/Unix operating systems provide an option to install an XML Catalog system, or an XML Catalog system is installed as part of an XML tools package. On Windows, you must manually perform the installation and configuration.
The native Windows libxml2 package from http://www.zlatkovic.com/libxml.en.html uses the XML_CATALOG_FILES and SGML_CATALOG_FILES environment variables to locate catalog files. One solution is to set an XML_CATALOG_FILES environment variable that points to "C:\etc\xml\catalog". Then, in that file, use the standard "file:///dir/filename" syntax to point to DTDs and other resources just like you would in Linux/Unix.
| |  | |
| Required Java Versions |  | Deploying to Tomcat |