Request Header Type Migrator

The Request Header Type Migrator contains the additional option Replace Existing special cmds? If the validation to be migrated references PPM special commands that already exist in the target PPM instance, you can decide whether or not to replace them. This includes both parent and children special commands. (The default value is No.) Regardless of their values, PPM automatically re-creates special commands that are missing from the destination instance.

Figure 10-12. Request Header Type Migrator

For information about most of the fields in this migrator, see Defining Entity Migrators.

Configuration Considerations

The Request Header Type Migrator also transfers the following information:

• Validations referenced by fields

• Environments referenced by validations

• Special commands referenced by validations

• Special commands referenced by other special commands

• Ownership group information for the request header type

The Request Header Type Migrator transfers references to environments from validations, but does not create an environment. If the referenced environment does not exist in the destination instance, the migration fails. In this case, you must create the missing environment manually in the destination instance.