HTTP Server for i

Secure, powerful, and complete

Overview

Getting Started

Documentation

Support

Compatibility Considerations

If you are applying a new release of HTTP Server for i, applying a group PTF containing a new level of Apache, or implementing ASF Jakarta Tomcat function, you will need to take into account potential incompatibilities.

Also visit Limitations and Known Problems and Getting Started for other important considerations.

	Differences between Releases of HTTP Server for i
	Differences between Levels of Apache on HTTP Server (powered by Apache)
	Differences between ASF Jakarta Tomcat on iSeries and Other Types of Servlet Engines

In V5R4, the following changes should be noted.

• Logs are now tagged with CCSID UTF-8 (1208).

  All messages contained in custom, error, FRCA, and script logs are encoded in UTF-8.

• Existing modules must be recompiled.

  As of V5R4, third party modules must be recompiled with locale object type *LOCALEUTF. This creates an environment where locale-dependent C runtime functions assume that string data is encoded in UTF-8. APR and HTTP APIs expect data in UTF-8 and will return data in UTF-8. Note that several APIs have additional functions that allow a CCSID to be set to indicate the encoding of the parameters being passed. Conversion functions between UTF-8 and EBCDIC have been added. Be sure to review APIs used by your module to be aware of current changes.

In V5R3, the following changes should be noted.

• Java CGI is no longer supported

  Java CGI is no longer supported with IBM HTTP Server for i. Java CGI was supported on past releases with Java Developer Toolkit (JDK) Version 1.1 only. There is no support for JDK levels other than 1.1. Since JDK 1.1 is no longer shipped with the 5722-JV1 product in V5R3, Java CGI is no longer supported with IBM HTTP Server (5722-DG1) in this release.

• Configuration update for Tomcat 3.2.4

  If you use Apache Software Foundation’s Jakarta Tomcat 3.2.4 that is shipped with IBM HTTP Server, you need to update your Tomcat configuration to use version 1.3 of the Developer Kit for Java (5722-JV1). This change is necessary because Version 1.2 of the Developer Kit for Java has been removed in V5R3.

• Error log file expanded

  The DDS format for the HTTP server Error Log file has been expanded to include more information. The QHTTPSVR/QAZHBERR file has been updated to contain two additional fields. The ERRLVL and ERRTXT fields have been appended to the ERRSRC record format. Programs accessing this file should have LVLCHK(*NO) specified.

• HTTP Server (Original) withdrawn

  HTTP Server (original) has been withdrawn from the IBM HTTP Server for i (5722-DG1) product in V5R3.

  If you use HTTP server, you must migrate your HTTP Server (original) configurations to HTTP Server (powered by Apache). Web applications that include static (HTML) pages, CGI programs, or Server Side Includes (SSI) do not require migration and are fully supported on HTTP Server (powered by Apache).

  A migration wizard is provided with the IBM Web Administration for i5/OS interface to assist in the migration. You should migrate from the HTTP Server (original) to HTTP Server (powered by Apache) before you install V5R3. The migration wizard is available with the IBM Web Administration for iSeries interface in V5R1, V5R2, and V5R3. The migration is recommended prior to V5R3 so that you can test the migration to HTTP Server (powered by Apache) while continuing to serve production Web sites using HTTP Server (original) during the migration. Original server configurations stored in QUSRSYS/QATMHTTPC will not be altered or deleted during a V5R3 install. This will allow you to migrate original server configurations to HTTP Server (powered by Apache) after installing V5R3, should you choose to do so. Original server instances stored in QUSRSYS/QATMHINSTC will be removed during a V5R3 install so that they no longer appear on the IBM Web Administration for i5/OS interface after installation of V5R3. Original server instances will be deleted, but original server configurations will be left to allow for migration.

Back to top

Starting with Apache 2.0.47, there are no significant compatibiilty differences between the available levels of HTTP Server (powered by Apache).

Always be sure to load the latest PTFs to get the most current fixes for HTTP Server for i.

To determine the level of Apache on your system enter, for example:
STRTCPSVR SERVER(*HTTP) HTTPSVR("APACHEDFT" '-V')
Note: The command was entered on a V5R3 system.

You will see details similar to the following.
(This server is using Apache 2.0.52.)

Back to top

Following are examples of items which are not available with the Java Servlet and JavaServer Pages engine based on technology from the ASF Jakarta Tomcat project:

• Support of WebSphere Branded Products:
  • WebSphere Commerce Suite, WebSphere Payment Manager, WebSphere Host Publisher, WebSphere Transcoding Publisher, etc.
• Connection Pooling 
• J2EE Compliance
• Enterprise JavaBeans
• Domino Integration
• Multi-node Administration
• Distributed Security
• Workload management
• Clustering/cloning
• Directory Services
• J2EE client application support
• Javamail

For solutions which require the above features, consider using the WebSphere Application Server.

Back to top