ENDWWWcommand. Ensure that no product commands or menus are running. Also ensure that the Merchant/400 API is not currently being called by another job (this applies to product re-install only). Use the
WRKACTJOBcommand to verify that there are no servers, commands, or other jobs running that may be executing the API.
LODRUNto install Merchant/400 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 2 to 15 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 that the install was successful.
If any problems occur during the install:
WWWServwas restored into the root of the IFS file system when Commerce Server/400 was installed.
WWWServcontains many other directories and stream files that are used by Web Server/400 or Commerce Server/400. Merchant/400 publications were restored into the
I/NET storeapplication were restored into the
WWWMRCHcontains the sample
I/NET Storeapplication that is used to demonstrate how the API functions. Don't forget to add this library to the list of Script Libraries (with the
ADDWWWSCPLcommand) before attempting to run the sample application.
Important note: Merchant/400'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. In addition,
I/NET Store application will always be installed into the
WWWMRCH library and the
/WWWServ/WebDocs/Shipped/Merchant directory. The contents of these
areas should be duplicated by the user to another library and directory for actual use, as
they may be deleted or over-written in the future.