Administer > Stage server

Create a staging server

Overview

The staging server should be run on a separate system or system partition from the production server.

Federate to the same deployment manager as the production server. Otherwise, managed files will not be propagated into the production EAR because the deployment manager is not aware of the production node.

Procedure

1. Install WebSphere Commerce and its supporting software using the custom installation option of the WebSphere Commerce installation wizard.

2. Prepare the staging server to connect to the production database:

   1. Install IBM Data Server Client for communication with the production database.

   2. Catalog the remote production database so that is accessible from the staging server.

3. Create a WCS instance as a staging server:

   1. Start the WebSphere Commerce Instance Creation wizard.

   2. Complete the pages of the wizard.

   3. On the Staging page of the wizard, ensure that you select...

      Use staging server

      If you do not select this check box, the resulting WCS instance will be a production WCS instance.

   4. Ensure that caching is not enabled in the Cache page.

   When the instance creation process complete, we will have a staging instance.

4. Enable custom tables for staging
   

5. Configure the database for staging.

6. Federate the staging instance to the production server.

7. Test the site on a staging server

See also

1. Create a staging server on a migrated environment
2. Configure databases for use with the staging utilities
3. Enable custom tables for staging

Related concepts

Stage server

Related tasks

Configure databases for use with the staging utilities
Create triggers for custom tables

Related reference

Create the staging server before the production server
Create the staging server after the production server

+

Search Tips   |   Advanced Search