Administer > Stage server

Test the site on a staging server

1. Configure the staging server.

2. If production server is running, synchronize staging server with production server
   1. Copy data to the staging database.
   2. Copy files to the staging server.

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

4. Publish data to the production database.
   

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

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

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

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

9. Repeat steps 1 to 7 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

Stage server utilities
Stage server
Managed files

Related reference

Troubleshoot: Staging server
Stage server limitations

+

Search Tips   |   Advanced Search