Approval profiles
For each migration scheme, an approval profile specifies from zero to five approver roles, defining the types of user who must approve a change package before it can be migrated. A change package is fully approved when all of the applicable approver roles have approved it.
For example, the following table shows an approval profile called NORMAL.
Approval profile: NORMAL | |||||
---|---|---|---|---|---|
Migration scheme | Approver role | ||||
1 | 2 | 3 | 4 | 5 | |
WRK2DEV | |||||
DEV2TEST | APPDEV | PROJMAN | |||
TST2PROD | TESTER | PROJMAN | CICSADMN | OPSMAN |
Suppose you want to migrate a change package from your work environment to development using the WRK2DEV migration scheme, and then from development to test using the DEV2TEST migration scheme, and then from test to production using the TST2PROD migration scheme. If you assign the NORMAL approval profile to this change package, then:
- Migrating from work to development requires no approvals
- Migrating from development to test requires the approval of a developer and a project manager
- Migrating from test to production requires the approval of a tester, a project manager, a CICS® administrator, and an operations manager