Initial Webulator/400 Setup

The following steps must be performed before running the Webulator/400 Version 1.1 for the first time.

1. Install Web Server/400 Version 1.3 or Commerce Server/400 Version 1.0
   Webulator/400 requires either Web Server/400 Version 1.3 or Commerce Server/400 version 1.0. If you have not already done so, install it first.

2. Install Webulator/400 Version 1.1
   After the server has been installed, you are ready to install the Webulator/400 Version 1.1 code.

3. Start Web Server/400 or Commerce Server/400
   If you are reading the documentation online, you may want to start the server in order to get access to the links pointed to by this file. Otherwise you can restart the server after the initial setup has been completed.

4. Create a Webulator/400 Alias
   If you are migrating from Web Server/400 Version 1.0 or 1.1, you must add a new Web Server/400 alias that will allow users access to Webulator/400 URLs. If you are not migrating from an earlier release, both Web Server/400 and Commerce Server/400 ship a default Webulator/400 alias named /WWW5250/.

   To add a new alias you can run the WRKWWWALS command and provide a name such as WWW5250 for the Alias field and the value *WEBULATOR for the Source type field (the Value field may be left blank).

5. Run the CHGWWWCFG command to enable Webulator/400
   • Set the Directory Based Configuration File (ACCGBLFILE) Field
     The Web Server/400 and Commerce Server/400 configurations allow you to specify a Directory Based Configuration file. While this entry was optional in earlier versions of the Web Server/400, it is now required if you wish to run Webulator/400. The easiest way to setup Webulator/400 is to use the sample Directory Based Configuration file that is shipped with the Webulator/400 product. You can use this file by setting the Directory based configuration field to /WWWSERV/CFG/WBLMACC.CFG.

     If you already have an entry in the Directory based configuration field, it is recommended that you temporarily replace your current configuration file with the Webulator/400 sample Directory Based Configuration file to test and get familiar with the functionality of Webulator/400. After you feel comfortable with its functionality, you can then modify your existing Directory Based Configuration file to include the desired new entries for Webulator/400.

     All Webulator/400 configuration values will be set to their default values when using this file.

   • Set the Webulator/400 User File Path (WBLUSRFILE) Field
     You must set the path of the Webulator/400 user file if you plan to take advantage of the automatic signon capabilities of Webulator/400. The easiest way to setup Webulator/400 to use automatic signon is to reference the sample User File that is shipped with the Webulator/400 product. This file can be used by setting the Webulator/400 User File Path field to /WWWSERV/CFG/AUTH/WBLUSR.CFG.

     This file is shipped with no entries since it is not possible to know the user ids or passwords on your system. You must add your own entries to this file using the WRKWBLUSR command before it will be useable by Webulator/400.

     It is beneficial to use the sample user file because of the authority settings that are shipped with this file.

   • Set the Maximum Webulator/400 Sessions (WBLMAXSSN) Field
     You can optionally set the maximum number of simultaneous Webulator/400 sessions that will be allowed. If you do not specify this entry, a default of 20 sessions will be used.

   • Set the Disable Webulator/400 (DISABLEWBL) Field
     You must set the Disable Webulator/400 entry to *NO to configure the server to automatically start Webulator/400 during its startup process.

6. Evaluate Signon Method
   The sample Directory Based Configuration file (/WWWSERV/CFG/WBLMACC.CFG) that is shipped with Webulator/400 contains a root directory entry with a signon method of signon screen. "Signon screen" was chosen because of its ease of setup, but it does have some potential security considerations. If you are not comfortable having a signon screen available even for a short period of time, you should change the signon type to a different value before restarting or reconfiguring Web Server/400. This value can be set through the Sign-on method field through option 10 of the WRKWWWDIR command or directly through the CHGWBLCFG command.

7. Add Additional Webulator/400 Directory Entries
   The sample Directory Based Configuration file (/WWWSERV/CFG/WBLMACC.CFG) that is shipped with Webulator/400 contains only the Webulator/400 root directory entry and no child directories. You can optionally add more Webulator/400 directory entries by running the WRKWWWDIR command. Please note that all Webulator/400 directory entries must start with /*META/WEBULATOR/. Therefore, the Webulator/400 root directory will always be named /*META/WEBULATOR/. If you want to add a new directory entry off of the Webulator/400 root, you can add an entry such as /*META/WEBULATOR/STATUS/. By creating additional directories, you can have multiple URLs that will have different characteristics (such as which user will automatically be signed on).

8. Check AS/400 Virtual Terminals
   Verify that the AS/400 system value QAUTOVRT is at a large enough number so that Webulator/400 can automatically create additional virtual terminal devices if needed.

9. Start your Web Server
   Start either Web Server/400 or Commerce Server/400. It will start Webulator/400 during its startup process.

   If your server is already started, then you may run the Set WWW Configuration Values (SETWWWCFG) command which will reconfigure the server which in turn will start Webulator/400. Please note that in the future when you reconfigure Webulator/400, the new configuration values will take effect for all new sessions only. Please refer to Reconfiguring Webulator/400 for more information.