Migration

Note: If you are running Commerce Server/400, consider the references to Web Server/400 in this documentation to mean Commerce Server/400. Both products are interchangeable except for the security enhancements added to Commerce Server/400.

End Web Server/400 Before Installation

All currently running Web servers must be ended with the ENDWWW command before installing the Web Server/400 or Commerce Server/400 upgrade. Also ensure that no product commands or menus are running. Use the WRKACTJOB command to verify there are no servers and commands running.

You may see older version restored (CPF3722) messages in the joblog when migrating to the new version. These messages are normal and are generated because one or more of the product libraries have been backed up with a save command that had the update history (UPDHST) parameter set to *YES.

Migrating from Web Server/400 version 1.3 or Commerce Server/400 versions 1.0 and 1.0a

Update the Content Type Configuration File

A new content type was added to the content type configuration file. Using the WRKWWWCTP command, add the entry application/x-webulator400-keys using option 1.


     Content type                    Extensions
     ---------------------------     -------------
     application/x-webulator400-keys wky

Create a plugin.wky file

Create a file named plugin.wky in your document root directory on your AS/400. If you have not changed the defaults, this will be /WWWServ/WebDocs. This file can contain any data you like; it must exist, but the contents are not important.

Migrating From Web Server/400 Version 1.2.

This section should be read by all customers migrating from a previous version of Web Server/400.

Evaluate authorization user storage

If you are using user authentication, read about user storage and decide whether you want to migrate stream files to database files.

Update the Content Type Configuration File

A new content type was added to the content type configuration file. Using the WRKWWWCTP command, find the current entry for application/octet-stream and add the extensions using option 2.


     Content type                    Extensions
     ---------------------------     -------------
     application/octet-stream        exe dll

Evaluate default CCSIDs

The Content CCSID default has changed from 850 to 819. The new File CCSID configuration value also defaults to 819. This should work better for most users than the old way. If you wish, you can override the defaults.

Server Administrator Address Has Been Removed

This configuration value has been removed. As it was not being used previously, this should not be noticable to most users. If, however, you have a program which sets this value through the CHGWWWCFG command, you will need to change the program.

Consider changing Domain name lookup.

The default for this is Normal, which looks up a host name for every request. For performance, we ship a configuration file to all new customers that sets this to Minimal.

Migrating From a Web Server/400 Version Prior to 1.2

This section should be read by all customers migrating from a version of Web Server/400 earlier than version 1.2. Make the changes below, then make the changes suggested for users of Web Server 1.2.

Using a Server User Profile other than WWWUSER

If you are using a server user profile other than the default of WWWUSER, then that user profile's job description needs to be changed to WWWSERVER/WWWJOBD. More information on this can be found under the STRWWW command.

Updating the Content Type Configuration File

A couple of new content types were added to the content type configuration file. Using the WRKWWWCTP command, find the current entry for each of the content types listed below and add the specified extensions using option 2.


     Content type                    Extensions
     ---------------------------     -------------
     application/octet-stream        pcl
     text/html                       html3 ht3

Updating from Version 1.0

Customers updating directly from version 1.0 should follow the migration instructions provided separately. If you are not sure what version you are running, display the data area WWWSERVER/VERSION using the command DSPDTAARA WWWSERVER/VERSION. If this data area does not exist, you are probably running version 1.0.