Deprecated feature

Setting up a clustered environment to use a separated store archive

You can separate the store web application archive (WAR) from the WebSphere Commerce enterprise archive (EAR) and set up a clustered environment that uses the separated EAR. When the store separation process completes, a new store EAR is created that contains an copy of the store WAR. The original store WAR within the WebSphere Commerce EAR is disabled. With this separation, the storefront assets for your WebSphere Commerce instance are included either within the store EAR or the WebSphere Commerce EAR and referenced by the store EAR through a shared library.

Before you begin

Ensure that you complete the following tasks:

Procedure

  1. Create a WebSphere Commerce instance.
    For more information, see the following topics:
  2. Separate the store WAR from the WebSphere Commerce EAR for your WebSphere Commerce instance.
  3. Back up the WebSphere Application Server administrative configuration. By backing up the administrative configuration, you can restore the original configuration if the clustering fails during the clustering process. For more information, see the Backing up and recovering the application server environment topic.
  4. Federate the WebSphere Commerce node into a deployment manager cell.
  5. Cluster your WebSphere Commerce environment. You can set up a clustered environment with vertical cluster members or horizontal cluster members.
  6. Configure the shared library and class loader for use in the clustered environment.
    1. SolarisLinuxAIXLog on as the non-root user.
    2. In a command-line utility, go to the following directory:
      • For IBM i OS operating systemSolarisLinuxAIXWC_installdir/bin
      • WindowsWC_installdir\bin
    3. Run the following command:
      • For IBM i OS operating systemSolarisLinuxAIX./config_ant.sh -buildfile WC_installdir/components/store-separation/xml/syncClassLoader.xml -DinstanceName=demo
      • Windows.\config_ant.bat -buildfile WC_installdir\components\store-separation\xml\syncClassLoader.xml -DinstanceName=demo
  7. Regenerate the WebSphere Application Server web server plug-in configuration file.
  8. On your web server, update the path to the plugin-cfg.xml file within the web server configuration file.
  9. Restart the web Server.
  10. Restart the cluster.

Results

The store WAR for your WebSphere Commerce instance is separated from the WebSphere Commerce EAR. You can deploy any future changes into the appropriate EAR without affecting the other EAR.

Note: If you add a node or cluster member, you must update the shared library and class loader to work with the new node or member. To update the library and class loader to work with a new node or cluster member:
  1. In a command-line utility, go to the following directory:
    • For IBM i OS operating systemSolarisLinuxAIXWC_installdir/bin
    • WindowsWC_installdir\bin
  2. Run the following command:
    • For IBM i OS operating systemSolarisLinuxAIX./config_ant.sh -buildfile WC_installdir/components/store-separation/xml/syncClassLoader.xml -DinstanceName=demo
    • Windows.\config_ant.bat -buildfile WC_installdir\components\store-separation\xml\syncClassLoader.xml -DinstanceName=demo

What to do next

After you separate the store WAR, update any store functions and processes that use assets that were included within the default store WAR. Update these functions and processes to point to the new location of the store assets in the store EAR.

When your store developers create or change store assets, the assets can be deployed into the new store EAR with the WebSphere Commerce Build and Deployment tool. For more information, see Deploying new and changed store assets into a separated store EAR.