Migration through multiple environments

When you use a change package to migrate resource definitions from a source CICSĀ® configuration to a target CICS configuration, CICS Configuration Manager automatically adds to the change package the newly migrated resource definitions in the target CICS configuration. This behavior is known as propagation. Propagation enables you to add resource definitions to a change package once only, and then progressively migrate that change package onwards through multiple environments without updating the change package for each migration.

The following figures illustrate propagation in a simplistic scenario: you create or update a resource definition in a development environment (represented here by a CICS configuration named DEVT); you use a change package to migrate the resource definition from development to a test environment (TEST); and then you use the same change package to migrate the resource definition from test to a production environment (PROD).

First, you create or update a resource definition in a development environment. Then you create a change package, add the resource definition to the change package, mark the change package as being ready for use with the "development to test" migration scheme, and then use that migration scheme to migrate the change package:

Figure 1. First migration, from development to test: you add the resource definition to the change package

After migration from development to test, the change package refers to the resource definition in development and also to the migrated resource definition in test:

Figure 2. After migration from development to test

Note that, if the "development to test" migration scheme uses transformation rules, then the resource definition in development and the resource definition in test might be different.

Next, you mark the change package as being ready for use with the "test to production" migration scheme, and then you use that migration scheme to migrate the change package. This migrates the resource definition from test to production:

Figure 3. Second migration, from test to production: no need to update the change package

The resource definition in development is not a candidate for migration with the "test to production" migration scheme, and so it plays no part in this migration.

After migration from test to production, the change package refers to resource definitions in all three environments:

Figure 4. After migration from test to production

Later, if you edit the same resource definition in development, you can reuse the same change package to migrate the resource definition again from development to test, and then test to production.


Information Information

Feedback


Timestamp icon Last updated: Friday, 1 November 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//ccv-migration-multiple.htm