Test a site on a staging server

1. Setup your staging server:

   1. Configure the staging server.

   2. Enable custom tables for staging.

   3. Configure your database for staging.

   4. If you set up your production and staging servers at the same time, skip this step. If your production server is already running, it contains data that must be copied to the staging server.

      1. Copy data to the staging database.

      2. Copy files to the staging server.

2. Update and test the site on the staging server.

3. Publish data to the production database.

4. Publish managed files to the WebSphere Commerce EAR on the production server.

5. Copy the non-managed files to the production server.

6. Manually propagate any database schema changes from the staging database to the production database.

7. (optional) Delete staged data from the STAGLOG table.

   Once data is published to the production database, entries in the STAGLOG table are marked as "published". These entries will not be published again. You might want to keep the information in the STAGLOG table for auditing or troubleshooting purposes.

   Delete staged data from the STAGLOG table if performance of the stagingprop utility is slow.

Repeat steps 2-8 each time changes are made to the files or database data on the staging server. These steps can be automated in a script and scheduled to run at off-peak hours to minimize performance impacts to the production server.

 

Related Concepts

Staging server
Managed files