Installation

Installing Web Server/400 or Commerce Server/400

Important Pre-Installation Instructions

Checking Your Tape Device

We have identified a problem in V3R1 on systems that have migrated/slip-installed from V2R3 to V3R1. The new SAV and RST commands CPF with a CPF3768 (i.e., Device not valid for command) when a valid IFS path for the tape device is provided. Since the server installation uses the RST command, the following steps need to be performed to ensure a successful installation:

Use the following command to display the tape device using an IFS path:

WRKLNK '/QSYS.LIB/xxxxx.DEVD' where xxxxx is your tape device (e.g., TAP01)
If the attribute of the tape device is set to TAP you are okay and can proceed with the installation. Otherwise you must delete and re-create the tape device. The system will set the attribute of the tape device to TAP when creating the new tape device. Be sure to write down the attributes of the tape device before deleting. The RST command requires that the tape device have a TAP attribute.

OS/400 PTF Levels

Web Server/400 and Commerce Server/400 have been tested with OS/400 cumulative PTF package TC96016 under V3R1 and TC96086 under V3R6. For best results, these packages or later packages should be applied to your systems.

Additional V3R1 PTFs not included in the cumulative PTF package listed above should be applied to improve system stability. Please load the following PTFs on your system.

The PTFs MF10372, MF10794, MF10795, and MF11235 for the product 5763999 should be applied. Without these PTFs the Web server may, in rare circumstances, abend while calling a system TCP/IP function.
PTF SF26297 for the product 5763SS1 should be applied if you use scripts written in Rexx/400. Without this PTF, performing a SAY with no expression will cause the Rexx/400 script to cause an exception.
PTF SF31797 for the product 5763SS1 should be applied if you use Client Access/400. Without this PTF, the system will assign a zero code page, which is invalid, to a file created in IFS when the user's CCSID is not set to 65535.

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 Web server to query the host name of a machine requesting a document. If this configuration specifies a search first parameter of *REMOTE and the remote DNS does not respond, the Web server 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 Web server. 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 Web server Due to Local Host Name Configuration

The Web Server/400 and Commerce Server/400 products require 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 Web Server/400 server host name configuration value. The error message displayed on the STRWWW 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. When upgrading from Web Server/400 to Commerce Server/400, the Web Server/400's code is replaced with the Commerce Server/400's code. Installing Web Server/400 or Commerce Server/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.
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 10 to 30 minutes depending on the tape device and AS/400 model (NOTE: RISC AS/400s may take longer if not using a RISC installation tape due to the extra time it takes to convert IMPI programs to RISC programs). 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 WWWUSER was created. WWWUSER has no password, a user class of *USER, and no special authorities. The product user profile WWWUSER owns all of the objects installed. WWWUSER was also added to the system directory.
The product user profile WWWUSER was granted *USE authority to job queue QSYSNOMAX.
The product library WWWSERVER was restored. WWWSERVER 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 WWWSERVER 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 WWWSERVER 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. Both programs manipulate all I/NET Web product objects (i.e., Web Server/400, Commerce Server/400 and Webulator/400).
A product job description named WWWJOBD was created in library WWWSERVER. The job description was setup to use the job queue QSYSNOMAX. The product user profile WWWUSER was changed to use the created job description.
The library WWWSAMPLES was restored. WWWSAMPLES contains sample documents that are used to demonstrate how objects in QSYS are accessed.
A folder named WEBDOCS was restored. WEBDOCS contains other folders and documents that are used to demonstrate accessing objects in QDLS.
A directory named WWWServ was restored into the root of the IFS file system. WWWServ contains many other directories and stream files. WWWServ contains the following directories:
- Cfg directory contains server configuration files. The shipped configuration files are saved in a sub-directory named Shipped.
- Logs directory is the default location of server log files.
- WebDocs directory is the default server document root. The Shipped directory off of the WebDocs directory contains all of the server's publications and sample content organized in directories. The /WWWServer/WebDocs/ directory structure is as follows:
```
Icons   : Sub-directory containing product icons
Shipped : Product sub-directory
   /Pubs     : Server documentation
   /Samples  : Sample content
```
  Important note: The server's sample content and publications will always be shipped in the 'Shipped' directory. Users should not place content in this directory for it may be deleted or over-written in the future.
- WWWUser directory is WWWUSER's home directory.
- Key directory is used by Commerce Server/400 to store commerce keys.
- Tmp directory is used by Commerce Server/400 for caching.
The library WWWCGI was restored. WWWCGI is the default script library.