Chapter 8 XML Component Administration
Table of Contents
The XML components provide commercial-quality, standards-based XML solutions. These components include: Xerces XML parsers in C++ and Java, Xalan XSLT stylesheet processor in C++ and Java, FOP XSL formatting objects in Java, Batik Scalable Vector Graphics (SVG) toolkit in Java, Cocoon XML-based Web publishing in Java, and Apache Axis. All are from the Apache XML Project. Internet Express also includes the UDDI4J Java Client Library from IBM that provides an API that can be used to interact with a UDDI registry, and libxml2 XML parser and toolkit in C developed by the Gnome project.
Apache Axis is an implementation of the SOAP (Simple Object Access Protocol) submission to the W3C. SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. Apache Axis, which is a follow-on project to Apache SOAP, is an XML-based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined data types, and a convention for representing remote procedure calls and responses. Axis improves on the previous Apache SOAP project with increased speed, flexibility, and stability and adds WSDL support.
The Universal Description, Discovery and Integration (UDDI) Project is a comprehensive, open industry initiative enabling businesses to discover each other and define how they interact over the Internet and share information in a global registry architecture. The UDDI project is the building block that enables businesses to quickly, easily and dynamically find and transact with one another via their preferred applications. The UDDI4J Java Client Library is a class library that generates and parses messages sent to and received from a UDDI server.
The directories in Table 8-1 are created when you install the XML components:
Table 8-1 Directories and Subsets for XML Components
As part of the IAEXMLJLIB subset, Internet Express installs the Apache Axis client API for invoking SOAP services. The Apache Axis Server is installed and configured by the IAESOAP subset. The base directory for the Axis webapp is /usr/internet/xml/axis/webapp.
To use the Apache Axis client API, set your classpath to include axis.jar, commons-discovery.jar, commons-logging.jar, jaxrpc.jar, saaj.jar, and wsdl4j.jar from the /usr/internet/xml/axis/lib directory. You also need xercesImpl.jar and xmlParserAPIs.jar from the/usr/internet/xml/xml/lib directory.
The Internet Express Administration utility allows you to enable and disable the Apache Axis Server. The Apache Axis Server is initially enabled running as a Tomcat Servlet and is accessible at the URL:
After you enable or disable the Apache Axis Server, the AdministrationSecure Web Server utility makes the necessary configuration changes and the public instance and Tomcat process are restarted. A status message is displayed. This process will enable or disable the Apache Axis Server on all availableSecure Web Server public instances of the (1.3 and 2.0) and Tomcat.
The IAEXML subset installs and configures the Apache Cocoon Servlet. Prerequisite subsets include the IAETOMCAT and IAEXMLJLIB subsets. The Apache Cocoon Servlet will be configured on all available public instances of the Secure Web Server (1.3 and 2.0) and Tomcat.
Cocoon can be used for the automatic creation of HTML from XML files as well as XSL:FO rendering to PDF files. It also can be used for client-dependent transformations such as WML formatting for WAP-enabled devices. For more information on Cocoon's capabilities, see the Cocoon documentation at:
Internet Express Version 5.9 upgraded Cocoon is to the Cocoon Version 2 code level. Because Cocoon Version 2 is nearly a complete rewrite of the original Cocoon project, to serve custom pages you must add configurations to the sitemap.xmap configuration file located in the /usr/internet/httpd/tomcat/cocoon directory. In addition, the main cocoon configuration file has changed and is now called cocoon.xconf. This file is located in the /usr/internet/httpd/tomcat/cocoon/WEB-INF directory. See the comments in these files and Cocoon documentation for more information on customizing the Cocoon configuration.
After you enable or disable the Apache Cocoon Servlet, the AdministrationSecure Web Server utility makes the necessary configuration changes and the public instances and Tomcat process are restarted as necessary. A status message is displayed. This process will enable or disable the Cocoon Servlet on all available public instances of the Secure Web Server (1.3 and 2.0) and Tomcat.