WebSphere Commerce EnterpriseWebSphere Commerce Professional

Synchronizing an authoring server with a production server

If you create your authoring server after creating a production server, you must synchronize your production and authoring server to ensure that the authoring server accurately reflects your production server. You should also synchronize your authoring server and production server if at any point your production-ready data on the authoring server does not accurately reflect your production server. This can be caused by changes made directly on the production server, either one large change or a series of smaller, incremental changes that cause the information about the authoring server and production server to no longer be synchronized.

Procedure

  1. Use the stagingcopy utility to copy all data from the production server database to the production-ready database on the authoring server.

    For more information, review Staging server limitations and Troubleshooting: Staging server.

  2. Use the fileloader utility to load any managed files from the production server file system to the production-ready database on the authoring server.
  3. Deploy the JSP, HTML, and image files for your store from the production server to the authoring server:
    1. Compress the following directory on the production server into one file:
      • WC_eardir/Stores.war
      When creating the compressed file, store only relative path information about the files.
    2. Ensure that the following directory on the authoring server is empty:
      • WC_eardir/Stores.war
    3. Move the compressed file from the production server to the authoring 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 you created in step 3a. For example, 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. Ensure that the paths to files in the Stores.war directory on the authoring server mirror the paths to file in the Stores.war directory on the production server.
  4. Stop and restart the authoring server instance.