MKS Implementer 2006 Administration Guide

Chapter 3: Implementer Administration
102
Key Considerations
You can define application paths at the environment level and at the project level. If you
use both environment paths and project paths, the project path is the default path in
check out and create request when a project with a defined path is specified. For details,
see “Project-based Application Paths” on page 142.
Each application path can have a standard path and an emergency path that represents
the flow member/objects follow from the initial check out to the final promotion into
production.
A standard path typically has a development environment (*TST) or library in the first
sequence. The next sequence can be optional QA environments or environment groups
(*QAC). The first production environment (*PRD) on the path must be the environment
you check out from. For an environment group, the primary environment in the group
must be the environment you check out from. Subsequent production environments or
environment groups are allowed depending on your development model.
An emergency path typically allows check out from production to development, and
promotion directly from development back to production. You can modify this flow as
needed.
To define a standard or emergency path for an environment
1 From the Work with Environments panel, type option 17=Standard path, or option
18=Emergency path, and press ENTER to display the respective Environment Path panel.
This panel allows you to create, change, delete, and display paths. The top environment
or library represents development. The first production environment on the path is the
check out from environment.