MKS Implementer 2006 Administration Guide

Chapter 2: Understanding Implementer
26
combining them in an environment group. These extra database libraries are either for
training and testing, or for a second division of the organization that uses the same program
libraries but requires separate data.
The example given is for multiple production database libraries, but you could also use this
for multiple database environments for a quality assurance environment. In this case, the
extra database files libraries are usually for different test databases.
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 full production environment.
2 Develop and test. Developer codes, compiles, and tests programs.
3 Promote to production.
Developer creates the promotion request targeting an environment group. The
environment group has the check out From environment as the first environment.
The database environments are also part of this environment group.
Developer can compile the promotion request into the work library.
Administrator moves the members/objects into the production environments. You
can perform the moves to the different environments at different times.
Setup Tasks
The setup tasks required for this scenario are as follows:
1 Create an Environment task. Define the following environments:
Production, one production environment for the complete application.
Database files environment (for production), one production environment for each
database files library.
Development environment, one development environment for all developers, or
specific environments per developer or project.
2 Create an Environment Group task. Define the following environment group:
Production, one environment group that combines the full production environment
with the database files environments.
3 Create a User Profile task. Define user profiles for the following user roles:
Developer checks out members/objects, performs development, and creates a
promotion request targeting the quality assurance environments. The developer
compiles the promotion request in the work library.
Administrator creates projects and moves the promotion request to production.