 Welcome to the Control and Reporting Facility Migration video. In this video, you will see how to migrate existing Control and Reporting Facility Report definitions into the new Control and Reports, and how to replace and update jobs that run these reports in Control and Client. In Control and Immunversion 918, you can no longer run Control and Reporting Facility Reports and Jobs, so instead you need to migrate to Control and Reports. You don't need to migrate the BMC Supply Reporting Facility Templates, only your own templates need to be migrated. New BMC templates are included in Control and Reports, such as Alerts, Active Jobs, Job Definitions and so on. Control and Reporting Facility Migration is a three-part process which consists of the following. Part 1. Pre-installation planning and installation of Control and Immunversion 918, including Control and Automation API. Part 2. Migration of your old data and reports into Control and Reports, and about three job definition. You need to define a job using Automation API, and then update the Jobs and Control and Imclient using the command Defined in Automation API. Before installing version 918, we need to plan the migration by using the RF Jobs Analyzer Utility, which comes with the installation CD. The Utility generates a report which contains the following information, identification of hosts that run Reporting Facility, detailed information about each job that runs these reports which will need to be updated, and view general warnings about the migration process. To start the process, from the installation DVD, go to Setup, Underscore Files, Tools Reporting. Move to Reports, Underscore Jobs, Underscore Analyzer folder to a specific Control MEM server where we want to run the Utility. In this case, you will see we have moved it to the Desktop Reporting directory, but it can be anywhere on your EM server. Let's open a Kappan prompt. Go to the Reports, Underscore Jobs, Underscore Analyzer folder and type the following command. Run, Underscore RF, Underscore Jobs, Underscore Analyzer and press Enter. A summary appears on screen. To see the details of the report, open the text file, the location of which is mentioned here. Let's open the text file. In this example, you will see at the top of the report there is a general summary which shows we have two jobs running on the host. If we scroll down, you can see a breakdown of both jobs. The first job is a Control M OS job. You can see the job name, folder name and other details including the command which will need to be updated later. The second job is a Control M Reports job. Again, you can see the job details. Finally, note the general warnings. Need to check if there are OS jobs containing scripts which run EM Reports CLI. Let's remind for us that EM Reports CLI EXE is no longer supported. These two jobs need to be updated which we will deal with later. Now we can proceed with installation. The next step is to install Control MEM version 918. Ensure that we do not upgrade the Control M client running the EM Reports CLI EXE until the migration process has ended. Now we can proceed with the migration. The next step is to migrate reporting facility report definitions to the new Control M Reports. Need to run the EM Reports CONV CLI EXE utility. This utility converts existing reporting facility RPT files to Control M Reports JSON files. On the CD, go back to the same directory as before and this time move the report conversion CLI folder to the reporting facility client machine which we identified in the RF jobs and aligns utility report. You will see we have placed it in the reporting folder but it doesn't have to be in any particular location. Before we start, we need to find out where the RPT files are located. By default, the files are in EM installation, default, data, reporting and templates. We've also created a new file for the new reports, reporting conversion CLI, converted reports. Now let's convert the folders by running the utility. Go to the report conversion CLI folder and type the following. EM report CONV CLI.EXE-S source folder where the RPT files are located, hyphen D destination folder where the new files will be located. Press Enter. You can see both the Alert Sample Report and Job Definition Sample Report have been converted. There is also confirmation of the source and destination folders. To check, let's open the destination folder and you'll see both reports are now in the folder plus a report conversion summary. Let's open this file and you'll see details of the conversion. Now we can import those reports into CTRL-M reports. From the V918 client, open CTRL-M reports. Click report and then select load from file. Navigate to the converted reports folder. Firstly, select Alert Sample Report and click Open and then click Save. Review the contents and verify the output. Let's do the same for the Job Definition Sample Report. Select load from file, click Open and then click Save. Again, review the contents and verify the output. The reports have now been migrated into CTRL-M reports. As like any other report, you can edit, generate or delete the report as you wish. For more information, see CTRL-M reports online help. Part three, Job Definitions. In CTRL-M Client, the following job types no longer run. CTRL-M Report and OS Jobs running the EM Report CLI command. These jobs need to be updated by doing the following. Define a new command in Automation API. Ensure that you have already installed a configured Automation API before you start. For more information, see Automation API online help. Then you need to manually update the jobs in CTRL-M Client with the new command defined in Automation API. Let's define a job in Automation API. In this example, we have two reports that we have defined and want to run in Automation API. Alerts underscore sample underscore report and Job underscore definition underscore sample report. Let's start with the Alerts sample report. Open a command line and type the following. CTM reporting report, get. Then the name of the report we want to order, which is alert underscore sample underscore report. Then the report output format is PDF-O and the full name of the output file, which is C-Temp Alerts PDF. Press Enter, and you'll see the output has now been generated. Let's do the same for the Job definition sample report. Again, let's type CTM reporting report, get Job underscore definition underscore sample PDF-O C-Temp Job definition PDF, press Enter, and you'll see that Job definition output file has been generated. Now go to the temp file and we can see both files. Click Alerts file and then do the same for Job definition. The final step is to update report jobs and control them client. Open the client and you'll see we have two jobs that run reports that need to be updated. OS jobs running EM reports CLI, and this example runs the Job definition sample report and control them report job type, and this example runs the sample alerts report. For the OS job running the EM report CLI EXE, we need to update the command. So in the command field, delete the current command and replace it with the one defined in Automation API, which is CTM reporting report, get Job underscore definition underscore sample PDF-O C-Temp definition PDF, and then click OK. As the control them report job type doesn't run, we've created a new OS job type. Open the OS job type and you will see we have copied the details in the command line at the command that we defined in Automation API. CTM reporting report, get alerts sample report, PDF-O C-Temp alerts PDF, then click OK. You can then delete the control them report job type. You can edit or change any of the other definitions as usual, ensure that the environment where you run the new report jobs is set up correctly and has access to all the environmental variables required to run Automation API. Check in the jobs and then click order. Let's go to the monitoring domain and we can see that their jobs ended okay. This now concludes the migration process. For more information about reporting facility migration, see the reporting facility migration online help.