Install > Installing WebSphere Commerce > Installing WebSphere Commerce using the custom installation > Create a WCS instance > Mandatory post-instance creation tasks

Use IBM HTTP Server for i

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

After the WCS instance is created successfully, do the following steps:

Procedure

1. On the remote Web server machine, verify that the following Web server configuration files exist:

   • WC_USER/instances/instance/httpconf/httpconf.conf

   • WC_USER/instances/instance/httpconf/plugin-cfg.xml

   • WC_USER/instances/instance/httplogs

   • WC_USER/instances/instance/web

   • WC_USER/instances/instance/web/index.html

2. On the remote Web server machine, assign a certificate to the HTTP server. Refer toWeb server post-instance creation tasks.

3. On the remote Web server machine, open a QShell session and issue the command:

   chmod -R 755 /QIBM/UserData/CommerceServer70/instances/instance

4. As a check, ensure the WCS instance and associated Web server start successfully.

5. Log into the WebSphere Administrative Console.

6. Navigate to...

   Servers | Web servers | webserver1 | Additional Properties | Remote Web server management

   Enter the remote_user and remote_password. Click OK.

7. Save the changes.

8. On the Web servers panel, check the box for webserver1 and click Generate Plug-in.

9. On the Web servers panel, check the box beside webserver1 and click Propagate Plug-in.

10. Log out of the Administrative Console.

11. Restart the WebSphere Commerce Web server.

12. On IBM i, 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_PROFILE/installedApps/WC_instance_cell/WC_instance.ear)) SUBTREE(*ALL) SAVACT(*YES)

    Where

    templib

    is the temporary library the save file is created in.

    savf

    is the save file created

13. Use FTP in binary mode to copy the save file from the WebSphere Commerce machine to the remote Web server machine.

14. On the remote Web server machine, start a System i Navigator session.

15. Create the following directory:

    WC_PROFILE/installedApps/WC_instance_cell

    The directory that is created must be identical to the directory on the WebSphere Commerce machine.

16. On the remote Web server machine, restore the save file that was created in step 12. Use the following command:

    RST DEV('/qsys.lib/templib.lib/savf.file) OBJ(('WC_PROFILE/installedApps/WC_instance_cell/WC_instance.ear)) SUBTREE(*ALL) ALWOBJDIR(*OWNER)

17. On the remote Web server machine, assign the correct permissions to the Web server objects. Issue the following commands:

    CHGAUT OBJ(WC_PROFILE) USER(QTMHHTTP) DTAAUT(*RX) SUBTREE(*ALL)
    CHGAUT OBJ(WC_PROFILE) USER(QTMHHTTP) DTAAUT(*RWX) SUBTREE(*ALL)

18. On the remote Web server machine, only static content files are required. Remove the following files:

    WC_PROFILE/installedApps/WC_instance_cell/WC_instance.ear/*.jsp
    WC_PROFILE/installedApps/WC_instance_cell/WC_instance.ear/*.jar
    WC_PROFILE/installedApps/WC_instance_cell/WC_instance.ear/*.rar

19. Restart the WebSphere Commerce Web server.

Results

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

+

Search Tips   |   Advanced Search