Migrate CEM Policy Actions and Statements Between Environments

Products

• Compliance Event Manager

Issue/Introduction

How do you migrate or clone Compliance Event Manager (CEM) policy actions and statements from one environment (e.g., Sandbox) to another (e.g., Dev/Production)?

Environment

Compliance Event Manager (CEM)

Resolution

Perform a full migration of policies and actions by copying the underlying MAPDB dataset using standard z/OS utilities, such as IEBCOPY. This method is the most efficient when the target environment is a clean slate or when an overwrite is intended.
Migration Steps

1. Allocate the MAPDB in the target environment (e.g., Dev or Production).
2. Copy the dataset from the source environment to the target environment using IEBCOPY.
3. Restart the CEMALERT and CEMMON tasks after the import/copy is complete to load the new policy definitions into memory.

Important Notes:

1. Master MAPDB: Maintaining a 'master' MAPDB and copying it (or using shared DASD) is currently the only supported method to share policy across systems.
2. Export Utility (CEMXPORT): Use this utility to produce a viewable document; however, it cannot be used to move policy sets between MAPDBs.
3. CEMPOLU Utility: Broadcom does not support or recommend using CEMPOLU for this process due to the potential for errors or database corruption.