In this scenario, the staging server is created after the production server is running and contains data such as store information, orders and users. This scenario occurs when the decision to use a staging server is made after setting up and running the production server.
The following high-level steps describe how to create a staging server after the production server is running and contains data:- Install WebSphere Commerce and create an instance on the staging server machine. During staging server instance creation, ensure that you select the Use Staging Server check box on the Database panel to configure the instance as your staging server. To avoid complexity and performance issues, it is best to have two physically different machines for your staging and production machines.
- Synchronize the staging server with the production server
- Use the staging server utility stagingcopy to synchronize the staging server database with the production server database. The staging copy utility copies content data from the production database to the staging server database. It does not copy transactional data since, in general, transactional data does not have to be staged.
- Manually copy file assets such as JSP files and java code from the production server file system to the staging server file system.
- Make store changes to the staging server instead of the production server.
- Test your store to ensure it functions as you expect.
- Propagate the data from the staging server to the production server.
- Propagate database data using the stageprop utility.
- Propagate files using a file transfer utility.
- For store changes, repeat steps 3 through 5.