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:

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.
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.
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:

A user profile named WBLUSER was created. WBLUSER has no password, a user class of *USER, and no special authorities. The product user profile WBLUSER owns all of the objects installed.
The product user profile WBLUSER was granted *USE authority to job queue QSYSNOMAX.
The product library WEBULATOR was restored. WEBULATOR contains all of the product code. Product commands, a message file, menus, and panel groups were copied into library QSYS. Two utility programs are provided in library WEBULATOR that can be used to maintain the product objects that are copied into QSYS:
1. CPYQSYS: Copies product commands, message file, menus, and panel groups into library QSYS. This program may be needed after installing a new release of OS/400.
2. RMVQSYS: Removes product objects from library QSYS. If the product objects are removed from QSYS, either WEBULATOR will need to be added to the library list to access commands and menus or the commands and menus must be fully-qualified with the product library. This program needs to be run after each installation of product code.
Neither program requires any parameters.
A product job description named WBLJOBD was created in library WEBULATOR. The job description was setup to use the job queue QSYSNOMAX. The product user profile WBLUSER was changed to use the created job description.
A product authorization list named WEBULATOR was created. The authorization list is used to secure public authority to all of the Webulator's commands. By default, only users with *ALLOBJ special authority have access to running Webulator/400 commands. Additional users can be granted authority to running Webulator commands by adding the users to the WEBULATOR authorization list.
A physical file named INSTLOG was created in the WEBULATOR product library. INSTLOG is used by Webulator/400 to record each time the product or a product fix is installed.
A directory named WBL was restored into the root of the IFS file system. WBL contains many other directories and stream files. WBL contains the following directories:
- Cfg directory contains Webulator/400 configuration files. The shipped configuration files are saved in a sub-directory named Shipped.
- Logs directory is the default location of Webulator/400 log files.
- Pubs directory is the default location of Webulator/400 online publications.
- PlugIns directory contains files needed to enable browser keyboard support for Webulator/400 sessions.
- Images directory contains images that are used by Webulator/400.
- Key directory is used by Webulator/400 to store commerce keys.
- Tmp directory is used by Webulator/400 for caching.

Uninstalling Webulator/400

There is not an uninstall command or program. The following steps can be followed to delete the product:

CALL WEBULATOR/RMVQSYS
Deletes product objects that were copied into the QSYS library.
DLTLIB LIB(WEBULATOR)
Delete the product library.
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).
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.