Migration


End Webulator/400 Before Re-Installing

All currently running Webulator servers must be ended with the ENDWBL command before re-installing the Webulator/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 Webulator/400 version 1.1

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

Evaluate and duplicate Web Server/400 and Commerce Server/400 configuration files
Many of the configuration elements that are part of Webulator/400 were also required by Web Server/400 and Commerce Server/400. These include many of the server related configuration items like port, logging files, request processors, content CCSID, initial library list, and access controls, as well as Webulator session characteristics. Files that have previously been used for Web Server/400, Commerce Server/400 and previous versions of Webulator/400 may be modified and tailored to function with this version of Webulator/400.

Using the directory based migration command utility
The MIGWBLWBL command has been designed to act as an aid during the installation and setup of version 2.x of Webulator/400. It provides the ability to migrate the configuration values that are found in a Webulator/400 (version 1.x) directory based configuration file to the appropriate Webulator/400 version 2.x session based configuration file.

Only contents of the directory based configuration file will be migrated. Other aspects of the Webulator/400 configuration should be reviewed, duplicated, and modified manually. Values relating to non-Webulator/400 directories will not be reflected in the new Webulator/400 session configuration. As a result, <LIMIT> definitions that were previously inherited from the root directory by all Webulator/400 sessions will not be migrated and should be evaluated and added to the session based configuration manually.

Evaluate socket port
Previous versions of Webulator/400 typically shared the socket port (usually port 80) between server HTTP requests and Webulator session requests via Web Server/400 or Commerce Server/400. Since Webulator/400 now includes its own server support, the ability to share ports with the HTTP server is no longer possible. The default port for Webulator/400 sessions is now 5061. You have the option to run with a separate port number (eg. 5061) or, with multihome support, you can execute Webulator/400 sessions at another domain name or IP address using port 80.

Evaluate session name entries
In previous versions of Webulator/400, virtual terminal access was enabled through the HTTP serving capabilities of Web Server/400 or Commerce Server/400. This required a special distinction for Webulator/400 sessions within the Directory Based Configuration file - namely /*META/WEBULATOR directory entries. Webulator/400 version 2.0 no longer requires this distinction and, as a result, the Webulator Session entries cannot include the /*META/WEBULATOR prefix and instead begin with a root session defined as /. The MIGWBLWBL command automatically modifies these entries during the migration of the directory based configuration.

Limits section definition entries are no longer needed
Webulator/400 uses specific HTTP form method types to process interactive session information between the server and the browser. Since previous versions of Webulator/400 shared access control characteristics with Web Server/400 or Commerce Server/400, those products added a level of granularity that are not required for Webulator/400. This includes specific <limit> sections for varying method types. Since the HTML forms used by Webulator sessions relate to specific methods, it is no longer necessary to include the <limit> or </limit> section entries in the session based configuration. The MIGWBLWBL command removes these entries during the migration of the directory based configuration.

Evaluate header and footer file entries
Previous versions of Webulator/400 allowed for the inclusion of separate information at the top and bottom of every 5250 display. This information was stored in files and placed within the resulting HTML code when the Webulator/400 page is sent to the browser. Version 2.0 permits these entries to contain either a file name or a URL. New configuration sub-entries have been added to identify the type of entry (file or URL) that is contained in the header or footer configuration. As a result, a type and file CCSID must be included when specifying a file. The MIGWBLWBL command adds these entries (assuming the job's CCSID) during the migration of the directory based configuration.

Certain default definition values have been modified
In past versions of Webulator/400, mainstream browsers did not support all of the advanced functionality available in the product. Because of this, previous versions of the product shipped with certain functions disabled. Fortunately, browsers have advanced quickly with their support of advanced fuctionality and as a result, Webulator/400 Version 2.0 now ships with its advanced functions enabled. In addition, user feedback has indicated that some of our default values shipped in past versions of the product were not wanted. As a result of this, Webulator Version 2.0 has changed the following default configuration values:

Evaluate the resulting configuration
The resulting configuration values should be evaluated to ensure that the new Webulator/400 configuration will function as desired and in a similar fashion to the original (version 1.1) configuration. Use the CHGWBLSVR CHGWBLSSN, or WRKWBLSSN commands to modify other aspects of the Webulator/400 configuration.

Migrating From IBM's Workstation Gateway

This section should be read by all customers migrating from the Workstation Gateway (WSG) TCP/IP product option from IBM.
Using the migration command utility
The MIGWSGWBL command provides the ability to migrate the configuration values that are pertinent to AS/400 Workstation Gateway (WSG) to an appropriate Webulator/400 session configuration.

Contents of the INACTTIMO, DTARQSTIMO, DSPSGN, TOPBNRURL, BOTBNRURL, and CCSID parameters of the CHGWSGA command will be migrated in the following process:

The Port value for the "wsg" service in WRKSRVTBLE will also be migrated and placed in the Port Master Configuration value, as well as the first exit program found (controls WSG signon) that is registered for the QAPP0100 exit point. This will be placed in the Signon Method value of the session based configuration.

Evaluate the resulting configuration
The resulting configuration values should be evaluated to ensure that the new Webulator/400 configuration will function as desired and in a similar fashion to the WSG configuration. Use the CHGWBLSVR CHGWBLSSN, or WRKWBLSSN commands to modify other aspects of the Webulator/400 configuration.