The following is a list of tests which will help you determine if the server has been configured properly for access. The intention of the list is to check the basic areas of access and should not be considered to be a comprehensive set of tests. These tests also apply to Commerce Server/400 running as a regular HTTP server (i.e., not serving documents securely using SSL). Additional test cases are available for testing a site protected using SSL.
In order to perform the following tests the server must be started on the AS/400 and a Web browser must be running on the workstation.
WWWServ/WebDocsin the default configuration. Attempt to access the URL
http://your.system.name/substituting your AS/400 system's host name or IP address for the
your.system.namepart of the URL. The home page shipped with the Web Server/400 product should be displayed. The actual file brought back to the browser should be the
index.htmfile found in the
http://your.system.name/QDLS/URL substituting your AS/400 system's host name or IP address for the
your.system.namepart of the URL. This should bring up the Dynamic Indexing view of the directory
/qdls/found on your system.
QDLShas been configured as an alias pointing to the
/QDLS/directory. See the URL Locations section for further explanation about why an alias is needed to access the
/QDLS/directory when the default source type is not set to *QDLS. The resultant dynamic index should contain a
Samples/directory which, if clicked on, should contain other sample file(s) to view.
http://your.system.name/QSYS/URL substituting your AS/400 system's host name or IP address for the
your.system.namepart of the URL. This should result in a forbidden message indicating that the server is not configured to allow access to the QSYS library. Attempt to access the
http://your.system.name/QSYS/WWWSAMPLES.LIB/URL. This should bring up the a Dynamic Indexing view of the library
WWWSAMPLESrestored on your system through the Web Server/400 install. The dynamic index should show multiple files residing within the library. Both of the QSYS examples used the
QSYSalias. See the URL Locations section for further explanation about why an alias is needed to access the
QSYSdirectory when the default source type is not set to *QSYS. Also see the include libraries configuration section to determine how to allow access to other libraries.