Migrating Reporting Facility reports

This procedure describes how to migrate reports from the old Reporting Facility to the new Control-M Reports.

To migrate Reporting Facility reports:

1. Identify hosts in the old environment that run jobs that execute Reporting Facility reports, by running the rf_jobs_analyzer utility, as described in Identification of Hosts running Reporting jobs.

   NOTE: The rf_jobs_analyzer utility does not affect your currently installed version of Control-M. It is recommended that you execute the utility prior to your migration process and then review your previously defined jobs that execute Reporting Facility reports.

2. Install the new Control-M/EM version (including Control-M/EM Server, Control-M client, and Control-M Automation API).

   NOTE: Ensure you do not upgrade current Control-M clients that are running EmReportcli.exe until the migration process has ended.

   If you are running a Control-M/EM Server and Client on the same Windows machine, upgrade affects both Server and Client. However, for a limited time, you may continue using the Reporting Facility side-by-side with Control-M Reports, by installing a Control-M client version 9.0.00 under a new instance name prior to the upgrade. This enables you to continue viewing your old reports while moving to use the new Control-M Reports. For more information about installation, see Introduction to Control-M installation.

3. From the host(s) that you identified in step 1, convert Reporting Facility reports files (*.rpt) to Control-M Reports format (*.JSON), by Running the EmReportConvcli.exe utility.
4. Import the converted reports into Control-M reports in the new Control-M client instance, as described in Importing converted reports into Control-M Reports.
5. Create/modify and then delete jobs that execute Reporting Facility reports, as described in Control-M Report job definition.