Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
We configure the communication with the Control-M Enterprise Manager systems in etc/hwm_universal_interface_config.php this way:
Action for the developer requests:
Action for the tester approval and the deployment into the test environment:
Action for the planner approval and the deployment into the production environment:
Action for the process report:
Action for the cleanup on process deletes:
Action for the Object Browser:
In the rules file we will specify for the purpose of this example only simple rules for checking and changing the folder definitions.
We will check, that the folder and job names start with 'D' for DEV, with 'T' for TEST and with 'P' for PROD. If a description for a folder or job is missing a warning shall be displayed.
On change we will change the folder and job names and datacenters accordingly to the environment in which the folder definition is being moved.
After creating the configuration file etc/hos_ctm_dev_test_prod_rules_config.php as a copy of the sample file etc/hos_ctm_rules_config.php.sample and editing it, the configuration file looks like this:
In the we define the Object Browser definition for the Control-M folders, using the previously defined action:
After creating this definition the planers should be able to start the Control-M Object Browser:
In the n we define actions which will be called by the Control-M process activities.
In this example we will use one configuration file in all actions. After creating the configuration file etc/hos_ctm_dev_test_prod_call_config.php as a copy of the sample file etc/hos_ctm_call_config.php.sample and editing it, the configuration file looks like this (normally it would contain also descriptions in comments, but for the purpose of this document we removed them):
While editing the configuration file we have decided that: the process ID will be 'CTM_DEV_TEST_PROD', that the action names will be 'CTM_DEV_TEST_PROD_OPEN', 'CTM_DEV_TEST_PROD_TEST' and 'CTM_DEV_TEST_PROD_CLOSE', that the name of the repository archive will be 'CTM', that the process parameter prefix will be 'CTM.GNRL.', that the prefixes of object key and data parameters will be 'CTM.KEY.' and 'CTM.DATA.' , that there will be object key parameters 'CTM.KEY.SYSTEM', 'CTM.KEY.SERVER' and 'CTM.KEY.FOLDER' containing the information about the system, server and folder name of a folder definition in the process and that there will be an object data parameter 'CTM.DATA.DEF' containing the folder XML definition. Further we have specified expressions for how the system and key information of a folder definition will be evaluated from the object parameters.
In the process definition we define the parameters we need, using proper parameter name prefixes:
In the process definition the previously defined actions have to be assigned to the activities and the process cleanup:
In the we define the Control-M process:
After creating this definition the developers should be able to start a new Control-M process: