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.

Procedure

1. Run the stagingprop utility. If the store is published on your staging server, the staging triggers pick up the database activity on your STAGLOG table.
2. 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.
3. Deploy your store archive from the authoring server to the production server:
   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.zip Stores.war

   2. Deploy the compressed file 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 > Enterprise Application.
      3. Select WC_instance_name (for example, WC_demo). 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 4a. 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.
   3. After you successfully deploy your file, verify that the paths to files in the store WAR directory on the production server mirror the paths to files in the store WAR directory on the staging server.
4. Rebuild the WebSphere Commerce search index.
5. Stop and restart the production server instance.