Migration from HTTP Server (Original) to HTTP Server (powered by Apache)
If you are currently using the IBM HTTP Server (Original) and must migrate your configuration to the IBM HTTP Server (powered by Apache), you have two choices for doing this. If you are already familiar with Apache configuration, you may choose to migrate your configuration manually. You can also use the migration wizard shipped with IBM HTTP Server for i.
Note: V5R2 is to be the final release to support HTTP Server (Original)
For more information about differences between the two servers as well as details about migration, see Redbook: Chapter 8. Migration from HTTP Server (Original) to (powered by Apache).
The HTTP Server Administration interface contains a wizard that will migrate an original server configuration to an Apache configuration. The migration wizard will read the original server configuration, may prompt you for input about how to perform the migration, and will then generate an equivalent Apache configuration for your web site.
The migration wizard does not alter or destroy the original server configuration in any way. Therefore, you can run the migration wizard against a given original server configuration multiple times. Since the original server configuration is not altered or destroyed, you can migrate and test your new Apache server while your production HTTP server (Original) remains active. Just remember to change your new Apache server's listening ports and log files while testing it, since your original production server will still be using them.
The migration wizard will display a summary page that will provide details about the migration. After doing a migration, you should print the summary page for future reference since there is no log file created to record this information. For some original server directives there is no migration available for Apache. Portions of the original server configuration that could not be migrated will be indicated on the summary page.
If the migration wizard is unable to perform a reliable migration of the original server directive to an Apache equivalent, the migration tool will insert the original server directive into the Apache configuration on a comment line (line beginning with '#' character).
Note that the migration wizard does not correct problems in an original server configuration, so any problems with the configuration are likely to be carried forward during the migration.
After migrating, it is strongly recommended that you:
- Inspect the summary page to find out if there were portions of the configuration that could not be migrated. If migrations could not be performed, it may be necessary to perform some manual migrations.
- Inspect the resulting Apache configuration to determine if any original server directives were written to the file as comment lines. This is an indicator that the directive was not migrated.
- Complete a full set of testing on the web site being served with HTTP Server (powered by Apache). It is important to not only test the accessibility of your web site for your clients, but also make sure your web site is properly protected from those that are not authorized.
To bring up the migration wizard on the Adminstration interface, you must create a new HTTP server (powered by Apache) that is based on an original server. In the web administration forms click the "Setup" tab and then click "Migrate Original to Apache." You then can select the original server configuration that you wish to migrate and proceed through the migration wizard forms.
| 
