Publishing a store from the staging server

If you create a store on your staging server after you create a production server, you can publish the new store. To publish the store, you must synchronize your production and staging server.

About this task

IBM is aware of an error that occurs when you attempt to publish a store that belongs to a staging instance, which was created on WebSphere Commerce Version 8 Fix pack 8 or earlier. Exception errors occur when the stagingprop utility tries to propagate access control policy data into the production database. For more information about the issue, see JR55762.
Note: This issue does not occur if you migrated from WebSphere Commerce Version 7. Review the following procedure carefully and complete the steps based on your situation.


  1. Go to the WC_installdir/bin directory.
  2. Propagate staged data and managed files from the production-ready data to the production server by running the stagingprop utility.
    If the store is published on your staging server, the staging triggers pick up the database activity on your STAGLOG table.
    1. Review the following topic to verify whether your environment is affected by the issue that is reported in JR55762.
      If your environment is affected, you need to run script fixes only once to resolve the issue. Stagingprop utility fails when propagating access control policy data.
    2. If you are not affected, run the stagingprop utility. For information about how to run the utility, see stagingprop utility.
  3. Propagate the data. To further propagate the files into the production environment, use the rsync utility. For more information, see Publishing data to the production database.
  4. Package and deploy the following files.
    1. Compress your store WAR directory on the authoring server into one file:
      1. In a command-line utility, go to the WC_eardir directory.
      2. Run the following command:

        zip -r Stores.war

    2. Package the following assets into a partial application.
      • WC_eardir/xml/member/MemberRegistrationAttributes.xml
      • WC_eardir/properties/tools/stores/*
      • WC_eardir/LOBTools.war/WEB-INF/src/xml/commerce/store/propertiesViews/yourStorefontAssetStore/*
    3. Deploy your compressed store archive from the authoring server to the production server:
      1. Open the WebSphere Application Server administrative console.
      2. In the WebSphere Application Server administrative console, select Applications > Application Types > WebSphere enterprise application.
      3. Select WC_instance_name (for example, WC_demo) and then click Update.
      4. Select Replace, add, delete multiple files.
      5. Specify the path to the file. Select Local file system, and enter the name of the compressed file that you created in step 4.a. For instance, Temp_dir/tempzip
      6. Click Next.
      7. Click OK.
      8. After the update completes, click Save to Master configuration to save your changes. Click Save.
    4. Repeat step 4.c to deploy the partial application.
    5. After you successfully deploy your files, verify that the paths on the production server mirror the paths of the files that you deployed from the authoring server.
  5. Rebuild the WebSphere Commerce search index.
  6. Stop and restart the production server instance.