Create the staging environment before the production environment

The staging environment can be created either immediately before the production environment, for example, a few minutes or hours. The staging environment can also be used as a development environment for a longer period of time, for example days or months, before the production environment is created. This is the most common and easiest scenario to set up. The following high-level steps describe how to setup the staging environment before the production environment:

1. Deploy a new environment for staging purposes. Ensure that when the running the initdb_db2_sample.sh or initb_oracle_sample.shscript, the "staging" option is specified to create the schema and triggers required for a staging environment.

2. On the staging environment, create the store and its assets. For example, create a catalog and upload product information such as images and create users such as Marketing and Catalog managers.

3. Test the store to ensure it functions as you expect.

4. When the store is ready to run on the production environment, propagate the data from the staging environment to the production environment.

   • Ensure content is published in Watson Content Hub.

   • Publish database data using the stagingprop utility.

The stagingcopy command, which copies the production data to the staging environment is not required in this scenario, but can be used to synchronize the staging environment and the production environment if their databases are no long synchronized.

Related tasks
Creating a staging environment