Installation


Installing Webulator/400

Important Pre-Installation Instructions

Performance Problems Due to Domain Name Server Configuration

Significant performance problems can occur due to an incorrect configuration of the remote name server within the OS/400 TCP/IP. The remote name server, also known as a Domain Name Server (DNS), is used by the Webulator to query the host name of a machine requesting a session. If this configuration specifies a search first parameter of *REMOTE and the remote DNS does not respond, the Webulator will have to wait for the query to time-out (the number of retry attempts configured also extends the amount of time the request waits before failing). If you do not have a DNS available to you either from your Internet service provider or internally within your organization, you should leave the server address blank and specify *LOCAL for the search first parameter. This should correct your time-out delay, which in turn will increase the speed of the Webulator. The only other side effect to this configuration change is that the access log file will contain the IP address of the machine requesting the document, not the host name.

Problems Starting the Webulator Due to Local Host Name Configuration

The Webulator/400 product requires a local host name to be set either through the TCP/IP configuration, CFGTCP command option 12 (Change local domain and host names) or through the Webulator/400 server host name configuration value. The error message displayed on the STRWBL command indicating this error condition is: "The local host name could not be determined and was not explicitly set."

Installation Instructions

If migrating from a previous version, please read the migration instructions before continuing with the installation. Installing Webulator/400 on the AS/400 requires the following steps:

  1. Sign on the AS/400 as QSECOFR or another user profile with a user class of *SECOFR. Special authorities are required to successfully install the server's objects.
  2. Ensure the system value QALWOBJRST is set to either *ALL or *ALWPGMADP. The Webulator/400 service program WBLVAUTSRV adopts authority for the purpose of validating user profiles and passwords. The Webulator documentation; sign on methods, includes more information on this topic. QALWOBJRST can be reset, if needed, after the installation is successfully completed.
  3. Run the system command LODRUN to install the server from the supplied product tape.

    Note: Prompt the command to change the tape device if the default is not appropriate.

    The install should take approximately 5 to 20 minutes depending on the tape device and AS/400 model. The install program displays a message when it is finished indicating the install was successful.

    If any problems occur during the install:

    1. Check the joblog to determine the cause of the error.
    2. Correct the problem.
    3. Re-run the installation command.
    4. If problems persist, please contact support.

Objects Installed

The following objects were created/restored on the AS/400 by the installation program:

Uninstalling Webulator/400

There is not an uninstall command or program. The following steps can be followed to delete the product:
  1. CALL WEBULATOR/RMVQSYS
    Deletes product objects that were copied into the QSYS library.
  2. DLTLIB LIB(WEBULATOR)
    Delete the product library.
  3. Delete the \Wbl directory (and all of the sub-directories and stream files). If access with the appropriate authority is available to IFS from a PC then it is recommended to use a deletion program that supports recursive/sub-directory deletion (if available).
  4. DLTUSRPRF USRPRF(WBLUSER)
    Delete the WBLUSER user profile. WRKOBJOWN can be used to check if there are any remaining objects on the system before deleting the product user profile.