Synchronizing an authoring server with a production server

If you create your authoring server after creating a production, 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 on the authoring server and production server to no longer be synchronized.

To synchronize an authoring server with a production server:

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

    If the stagingcopy utility fails while copying merchant tables, ensure that the member_id is an organization or member group, not a user in the MEMBER table. Although not recommended, if the member_id is a user, manually copy the referenced user's record from the source database to the target database in both the USER and MEMBER tables.

    For more information, review Staging server limitations and Troubleshoot: 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. Copy the JSP, HTML, and image files for your store from the production server to the authoring server:

    1. Compress the contents of the following directory on the production server into one file:

      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:

    3. Transfer the compressed file from your production server to the Stores.war directory on the authoring server.

    4. Extract the contents of the compress file into the Stores.war directory on the authoring server.

    5. 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.

Related concepts

Workspaces
The stagingcopy utility and the production database
Managed files

Related tasks

Create an authoring server
Copy data to the staging database
Start and stopping WebSphere Commerce


Related Reference


Staging server limitations
stagingcopy utility
fileloader utility
Troubleshoot: Staging server