Chapter 8 XML Component Administration

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.

Apache Axis can be used with a variety of other protocols; however, the only bindings defined in this document describe how to use Apache Axis with HTTP and the HTTP Extension Framework.

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.

This chapter provides the following information:

Directories and Subsets for XML Components

The directories in Table 8-1 are created when you install the XML components:

Table 8-1 Directories and Subsets for XML Components

Directory	Contents	Subsets
/usr/internet/xml/xml/cocoon/	Java libraries for Cocoon	IAEXMLJLIB
/usr/internet/xml/xml/lib	Java libraries for Xerces, Xalan, FOP, and Batik	IAEXMLJLIB
/usr/internet/xml/axis/	Apache Axis libraries and samples	IAEXMLJLIB
/usr/internet/docs	Component documentation	IAEXMLJLIB, IAEXMLCLIB
/usr/internet/xml/uddi4j	UDDI4J libraries and samples	IAEXMLJLIB
/usr/local/bin	Libxml2 tools	IAEXMLCLIB
/usr/local/lib	Xerces C++, Xalan C++ , and Libxml2 libraries	IAEXMLCLIB
/usr/local/include/xml	Xerces and Xalan C++ header files	IAEXMLCLIB
/usr/local/include/libxml2	Libxml2 header files	IAEXMLCLIB

 

Apache Axis Server Administration

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.

	Note: The Apache Axis Server requires that the Tomcat Servlet Engine be started using Java Version 1.3.1 or greater. If you have multiple Java versions installed on your system, see the Secure Web Server Administration Guide for more information on selecting a Java environment for Tomcat. The Apache Axis client API also requires Java Version 1.3.1 or greater. If this is not the default version on your system, you must specify the full path to the appropriate Java commands when using this library.

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.

Managing the Apache Axis Server

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:

http://hostname:port/axis/

For more information on how to deploy, undeploy, or list available services, refer to the Apache Axis User's Guide; installed in the /usr/internet/docs/axis directory or available on line at

http://xml.apache.org/axis/

Enabling and Disabling the Apache Axis Server

To enable or disable the Apache Axis Server:

1. From the Manage Components menu, choose Apache Axis Server. The current status of the Axis Server is displayed (enabled or disabled).

2. If the status of the Apache Axis Server is enabled, click on the Disable button to disable the server. Conversely, if the current status is disabled, click on the Enable button to enable the server.

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.

Apache Cocoon Servlet Administration

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:

http://xml.apache.org/cocoon

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.

Managing the Apache Cocoon Servlet

When you install the IAEXML subset, a Web application directory is created in /usr/internet/httpd/tomcat/cocoon. Place all files needed by the Cocoon Servlet in this directory.

Code examples, included in the IAEXML subset, can be accessed from the following Web site:

http://localhost:port/cocoon/samples/

Enabling and Disabling the Cocoon Servlet

To enable or disable the Cocoon Servlet:

1. From the Manage Components menu, under XML Tools, choose Apache Cocoon Servlet. The Apache Cocoon Servlet page is displayed.

2. From the Apache Cocoon Servlet page, choose Enable/Disable Apache Cocoon Servlet. The current status of the Cocoon Servlet is displayed (that is, enabled or disabled).

3. If the status of the Apache Cocoon Servlet is enabled, click on the Disable button to disable the servlet. Conversely, if the current status is disabled, click on the Enable button to enable the servlet.

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.

Viewing the Cocoon Log Files

Cocoon logs information in the /usr/internet/httpd/tomcat/cocoon/WEB-INF/logs directory in the following files:

• access.log— Contains information on which pages were requested, the time of request, and the processing time required.

• core.log— Provides warning and error messages produced by Cocoon's core components.

• error.log— Contains all error messages produced by the Cocoon servlet.

• sitemap.log— Provides warning and error messages related to the sitemap components of Cocoon.

To view the log files from the Administration utility:

1. From the Manage Components menu, under XML Tools, choose Apache Cocoon Servlet. The Apache Cocoon Servlet page is displayed.

2. From the Apache Cocoon Servlet page, choose View Cocoon Logs. The View Cocoon Logs menu is displayed.

3. From the View Cocoon Logs menu, choose the desired log file. The contents of the selected file is displayed. For example, the View Core Log page displays the contents of the core.log file.