For IBM i OS operating system

Configuring a remote HTTP server for IBM i

Set up your system to use IBM HTTP Server for IBM i remotely.


  1. Ensure that you installed the WebSphere Application Server web server plug-in.
  2. On the remote Web server machine, verify that the following Web server configuration files exist:
    • WC_userdir/instances/instance_name/httpconf/httpconf.conf
    • WC_userdir/instances/instance_name/httpconf/plugin-cfg.xml
    • WC_userdir/instances/instance_name/httplogs
    • WC_userdir/instances/instance_name/web
    • WC_userdir/instances/instance_name/web/index.html
  3. Change the user profile on your remote machine, so that the library of the remote instance is set to the current library. To complete these changes, run the following command:
    CHGUSRPRF USRPRF(instance_name) CURLIB(instance_name)
    The name of the WebSphere Commerce instance.
  4. On the remote Web server machine, assign a certificate to the HTTP server.
  5. On the remote Web server machine, open a Qshell session and issue the command:
    chmod -R 755 /QIBM/UserData/CommerceServer80/instances/instance_name
  6. As a check, ensure the WebSphere Commerce instance and associated Web server start successfully.
  7. Log into the WebSphere Administrative Console. Navigate to Servers > Web servers.
  8. Click webserver1. Under Additional Properties click Remote Web server management. Enter the remote_user and remote_password. Click OK.
  9. Save your changes.
  10. On the Web servers panel, check the box for webserver1 and click Generate Plug-in.
  11. Propagate the plug-in configuration file by following the steps in Copying the plugin-cfg.xml file to Web server.
  12. On the Web servers panel, check the box beside webserver1 and click Propagate Plug-in.
  13. Log out of the WebSphere Administrative Console.
  14. Restart the WebSphere Commerce Web server.
  15. On the WebSphere Commerce machine, create a save file in a temporary library. Issue the following command:
    SAV DEV('/qsys.lib/templib.lib/savf.file) OBJ(('WC_profiledir/installedApps/
    WC_instance_name_cell/WC_instance_name.ear)) SUBTREE(*ALL) SAVACT(*YES)
    is the temporary library the save file is created in.
    is the save file created
  16. Use FTP in binary mode to copy the save file from the WebSphere Commerce machine to the remote Web server machine.
  17. On the remote Web server machine, start a System i Navigator session.
  18. Create the following directory:
    The directory that is created must be identical to the directory on the WebSphere Commerce machine.
  19. On the remote Web server machine, restore the save file that was created in step 15. Use the following command:
    RST DEV('/qsys.lib/templib.lib/savf.file) OBJ(('WC_profiledir/installedApps/
    WC_instance_name_cell/WC_instance_name.ear)) SUBTREE(*ALL) ALWOBJDIR(*OWNER)
  20. On the remote Web server machine, assign the correct permissions to the Web server objects. Issue the following commands:
  21. On the remote Web server machine, only static content files are required. Remove the following files:
  22. Restart the WebSphere Commerce Web server.
  23. You must update the web server machine with a new Stores.war file every time that you perform an action that updates the static web content inside the application. For example, Store Publishing, and Upload Logo. The Stores.war is located in the following directory: WC_profiledir/installedApps/cell_name/WC_instance_name.ear/Stores.war Ensure that the path to this file is the same on the web server node and the WebSphere Commerce node.


The IBM HTTP Server for IBM i is configured to run remotely with an IBM i machine.