MKS Implementer 2006 Administration Guide

Multiple Remote Productions Same Changes: Scenario 14
Overview
Remote System Scenarios
In this scenario, you distribute the same changes to multiple remote systems on a different
promotion request than the local version of production environment. This scenario ensures
the production system remains synchronous with the development system.
Development Tasks
This is the typical task sequence from the start of a programming change to completion.
1 Check out. Developer checks out to a personal library, project library, or shared
development library. The developer checks out from the local production version.
2 Develop and test. Developer codes, compiles, and tests programs.
3 Promote to local production.
Developer creates the promotion request targeting an environment.
Developer can compile the promotion request into the work library. Typically, you
compile just for the first environment.
Administrator moves the members/objects into the production environment.
4 Promote and distribute to remote production.
Developer creates the promotion request targeting an environment group.
Administrator moves the members/objects into the remote production
environments. You can perform the moves to the different environments at different
times, if needed. Many options exist for distributing the changes to the remote
system.
45