Case 3.1. CIMPLICITY Test Bed Project Deployed to Production System

Case Description

A Project is developed in the test bed and deployed in production.

Recommended Procedure

• Use a managed project for the test bed and the deployed project.
• Make sure that no configuration applications are open through the process except where specifically noted.
• Make sure that change management operations are not performed on either system except as specified in this use case
• For the test bed and production system, use project management recommended procedure to ensure that managed data is up-to-date.

Procedure

1. Modify the managed characteristics of the test bed local project to point to the production project in Change Management.
2. Compare latest test bed project with the current production project in Change Management.

1. Identify independently managed files that are in the current production project, but not in the test bed version.
2. Confirm that all differences are acceptable.
3. Re-configure the managed characteristics of the test bed project to point to the test bed project.
4. Shutdown the production system.
5. Make a backup copy of the local production project directory.
6. Modify the managed characteristics of the production local project to point to the test bed project in Change Management.
7. Right-click Project in the Workbench.
8. Select Manage>Get Latest on the Popup menu.

Note: This method is used so that runtime data that is not managed remains in the production project. If this is not desired do a Fetch Project instead of following this procedure.

1. Delete any files that were not in the test bed project.
2. Modify any non-CIMPLICITY configuration changes that were made to support the requirements change.
3. Modify the managed characteristics of the local production project to point to the production project in Change Management.
4. Check out the production project from Change Management.

Important: Do not overwrite the local copy.

1. Check in the production project.
2. Start the production project.
3. Perform a configuration update.
4. Start the production project to resume production

Notes and Issues