Prerequisites

The Control-M Module is being installed as a part of the ProcMan installation. It requires that also the Universal Object Module is installed, but this is what the ProcMan installation takes care about. The prerequisites for ProcMan itself are described in the documentation ProcMan – Install and Customize.

To be able to perform queries and updates in Control-M, the Control-M Module requires a technical user, having the following permissions in the Control-M Enterprise Manager:

1. Folders tab (permission to read and update Folders in Control-M)

Full access; Control-M: *; Library *; Folder *;

2. Run As Users tab (permission to write jobs that “run as” on specific hosts for all jobs deployed)

Control-M: *; Run As: *; NodeID/Group: *

3. Privileges- Category: Client Access (permission to use Automation API)

Control-M, Utilities, EM API, BIM WEB UI: Full

• Category: Control-M Configuration Manager (permission to get Automation API Token)

Control-M Configuration Manager: Full

• Category: Monitoring and Administration Tools (permission to run and use Control-M Reports)

CLI: Full

BIM Reports: Full

Forecast Reports: Full

The Control-M Module uses reports to obtain lists of required Control-M objects. For this purpose the reports must be defined in the Control-M Enterprise Manager systems. The report definition files are stored in the ProcMan installation package in hos_CTM/var/ctm/report/*.em.json. To import the report definitions from the files into Control-M, go in the Enterprise Manager Client→Tools→Control-M reports. In the upcoming reports tool click + Report→Load from file and select a *.em.json file containing the definition. After the definition has been loaded click Save. This way the Control-M reports must be defined from the files in the path above one by one, in all Control-M Enterprise Manager systems which should be accessed by ProcMan. When the Control-M Module requests a report, the Control-M Enterprise Manager generates the result in a temporary report *.csv file in the data/reporting/Generated subdirectory of its installation on the Control-M Enterprise Manager server and sends then the content of the file to the Control-M Module. Old temporary report files are automatically deleted by Control-M after reaching a report retention period, which is configurable in the Control-M options (10 days by default).