Creating a staging server

You can create a staging server to test your WebSphere Commerce installation before moving to production.

About this task

The staging server should be run on a separate system or system partition from your production server.
Note: The staging server needs to be federated using the same deployment manager as the production server. Otherwise, the managed files will not be propagated into the production EAR because the deployment manager is not aware of the production node. You can use the FileProp utility to determine whether the environment is federated. If the environment is federated, the FileProp utility propogates the files to the production server. If the environment is not federated, the FileProp utility places the names of new and changed files into the FileProp log file and you must manually copy the managed files from the staging server to the production server.


  1. Install WebSphere Commerce and its supporting software using the custom installation option of the WebSphere Commerce installation wizard.
  2. Install WebSphere Commerce maintenance.
    Note: Your staging server and production server should be on the same maintenance level.
  3. Prepare the staging server to connect to the production database:
    1. Install a database client suitable for communication with your production database.
    2. Catalog the remote production database so that is accessible from your staging server.
  4. Create a WebSphere Commerce instance as a staging server:
    1. Start the WebSphere Commerce Instance Creation wizard.
    2. Complete the pages of the wizard.
      Note: If you are creating an instance using an existing database and creating a new schema, the DBA username and password is required, but not requested by the wizard. To work around this issue, create a file, manually specify the DBA username in the file, and pass the password as a parameter when creating the instance silently. For more information, see Creating a WebSphere Commerce instance silently.
    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 WebSphere Commerce instance will be a production WebSphere Commerce instance.
    4. Ensure that caching is not enabled in the Cache page.
    When the instance creation process complete, you will have a staging instance.
  5. Install the WebSphere Commerce feature pack.
  6. Enable WebSphere Commerce features, including Foundation, which will create your search server.
  7. Enable custom tables for staging
  8. Configure your database for staging.
  9. Federate the staging instance to your production server.
    See WebSphere Commerce federation for more information on federating your WebSphere Commerce environment.

What to do next

Testing the site on a staging server