SolarisLinuxAIXWindows

For IBM i OS operating systemWindowsAIXLinuxSolaris Configuring a remote web server

If the web server is installed on a different node from WebSphere Commerce, create a WebSphere Commerce instance; then complete configuration of the web server node.

Procedure

  1. Ensure that you installed the WebSphere Application Server web server plug-in as described in WindowsInstalling the WebSphere Application Server Web server plug-inLinuxInstalling the WebSphere Application Server Web server plug-inAIXInstalling the WebSphere Application Server Web server plug-inSolarisInstalling the WebSphere Application Server Web server plug-in.
  2. Ensure that you enabled SSL on the web server node.
  3. For IBM i OS operating systemChange 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)
    Where:
    instance_name
    The name of the WebSphere Commerce instance.
  4. Propagate the plug-in configuration file by following the steps in Copying the plugin-cfg.xml file to Web server.
  5. If it does not exist, create directories on the web server node so that you have the following path available on the web server node:
    • WC_profiledir/installedApps/cell_name

    Ensure that the path for WC_profiledir is the same on the web server node and the WebSphere Commerce node.

  6. Copy the following directory from the WebSphere Commerce node to the web server node:
    • WC_profiledir/installedApps/cell_name/instance_name.ear
    Ensure that the full paths on the web server node and the WebSphere Commerce node are the same.
    Note:

    WindowsRemove any JSP and JAR files from the WC_instance_name.ear directory on the web server. Only static-content files should be in this directory on the web server.

    For IBM i OS operating systemSolarisLinuxAIX
    • Ensure that the web server read and execute permissions on all files and directories in the WC_profiledir/installedApps/ directory on the web server machine are correct.

      If the permissions on the files and directories are incorrect, you might not be able to access WebSphere Commerce.

    • Remove any JSP and JAR files from the WC_instance_name.ear directory on the web server. Only static-content files should be in the WC_instance_name.ear directory on the web server.
  7. 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.
    Note:

    WindowsRemove any JSP and JAR files from the WC_instance_name.ear directory on the web server. Only static-content files should be in this directory on the web server.

    SolarisLinuxAIX
    • Ensure that the web server read and execute permissions on all files and directories in the WC_profiledir/installedApps/ directory on the web server machine are correct.

      If the permissions on the files and directories are incorrect, you might not be able to access WebSphere Commerce.

    • Remove any JSP and JAR files from the WC_instance_name.ear directory on the web server. Only static-content files should be in the WC_instance_name.ear directory on the web server.
  8. WebSphere Commerce EnterpriseWindowsWebSphere Commerce ProfessionalFor Microsoft IIS users:
    1. On the WebSphere Commerce node copy file:
      • WC_installdir/config/deployment/webserverconfig/IIS/addCommerceAliases.js
      to any directory on the remote IIS node. This directory is denoted by IISdir.
    2. On the remote IIS node, check the contents of file IISdir/addCommerceAliases.js. Ensure all aliases and paths are correct.
    3. On the remote IIS node, start a command prompt session and issue the following command: 
      cscript.exe IISdir/addCommerceAliases.js
      This command will add all the necessary aliases to the Microsoft IIS web server configuration for WebSphere Commerce and WebSphere Commerce Payments.
    Note: If you receive message Input Error: There is no script engine for file extension ".JS" refer to technote 1172559 to resolve the error. Attempt the cscript again.
  9. Open the following file in a text editor: WC_profiledir/properties/soap.client.props Change the property com.ibm.SOAP.requestTimeout from the default value of 180 to 6000.
  10. Copy the following file:
    • SolarisLinuxAIXconfigureweb_server_name.sh
    • Windowsconfigureweb_server_name.bat
    from the plugins/bin directory in your web server install directory to WAS_installdir/bin on your application server.
    Note: If the web server and WebSphere Application Server are on different platforms, then the configureweb_server_name script must be copied from the plugins/bin/crossPlatformScripts directory on your web server rather than from the plugins/bin directory.
  11. Start your WebSphere Commerce server.
  12. Run the script file you copied:
    • SolarisLinuxAIXWAS_installdir/bin/configureweb_server_name.sh -profileName profile_name -user configAdminUser -password configAdminPassword
    • WindowsWAS_installdir/bin/configureweb_server_name.bat -profileName profile_name -user configAdminUser -password configAdminPassword
    Note: The script calls the WAS_installdir/bin/configureWebserverDefinition.jacl file to configure the following web server definitions:
    • Creates an unmanaged node definition
    • Creates the web server definition
    • Maps the existing application to the web server defnition
  13. If your web server is configured to use only IPv6, change the custom properties for the WebSphere Commerce server JVM:
    1. In the WebSphere Application Server administrative console for the WebSphere Commerce server, expand Servers > Server Types. Click WebSphere application servers. In the list of application servers, select your server.
    2. On the Configuration tab, expand Java and Process Management and click Process definition > Java Virtual Machine > custom properties.
    3. Click New. On the Configuration tab, enter the following name and value:
      Name Value
      java.net.preferIPv6Addresses true
    4. Click Apply > Save directly to the master configuration.
  14. Stop and restart the web server.
    WebSphere Commerce EnterpriseWindowsWebSphere Commerce ProfessionalNote: Microsoft IIS, you must stop and restart all Microsoft IIS related services and applications. See Microsoft IIS documentation for instructions on how to stop and start these services and servers.