 Welcome to the ControlM Reports Job Definition video. In this video, you will see how to define and run a ControlM Reports job in ControlM Version 918. In ControlM Client Version 918, defining a ControlM Reports job is a three-part process which consists of the following. Part 1. Installation and Configuration of Automation API, including the CLI. Part 2. Defining a report job command in the CLI. And Part 3. Defining an OS job in ControlM Client with a command defined in the CLI. Note that the following jobs no longer run in ControlM Client. ControlM Report and OS jobs running the EM Report CLI EXE command. If you have these jobs, they need to be replaced in ControlM Client with a new OS job. For more information about updating these jobs, see ControlM Migration Documentation over the ControlM Reporting Facility Migration video. Part 1. Installation and Configuration of Automation API. We need to do the following. Check the node npm versions. Download, install and test the CLI and define, set and verify the ControlM Environment. Part 1. Step 1. Check the node and npm versions. If you don't have the minimum requirements, go to node.js.org.en. Download, run the installer and follow the on-screen instructions. Let's check we have the required versions. Type node-v, press enter and you will see the version. Now type npm-v, press enter and again you will see the version. Step 2. Download, install and test the CLI. We need to download a CTM CLI TJZ node package. You can do this on Workbench or from a ControlM instance. If you want to run Workbench, see Automation API online help. In this example, we would download the CLI from a ControlM instance. So for many browsers, type the following. The ControlM instance, code on 8443, Automation-API, CTM-CLI.TJZ and press enter. Download the file. You can place the file in any directory, but we have moved it to the C drive because we want to run it from there. Install the CLI by typing the following command. npm-g installctm-cli.TJZ and press enter. You then see a series of messages that the TJZ file has been extracted. Now let's test the CLI. Type the following command CTM and press enter. You now see a list of commands. You can now run those commands in the CLI. Part one, step three, setting up the ControlM environment. In this step, we need to do the following. Add the ControlM environment, select the ControlM environment and verify the ControlM environment. To add the environment, type the following. CTM, env add, then the name of the environment, which we will call env1, then the name of the ControlM instance, then 8443, Automation-API, Username and Password and press enter. You now see we have added the environment. Note, you can see by default that the CTM-CLI is configured to accept self-scientificates only. If you want to change this, type the command referred to here, but type false instead of true. Now select the environment as our working environment. Type the following CTM, env set env1 and press enter. You now see that we have set the environment. Now let's verify the login by typing the following CTM, session login, press enter. You can see the username, session token and version. Part two, defining a job command in the CLI. Before we begin, we must create and save the controlling reports that we want to define. In this example, we have defined two controlling reports. Alerts underscore sample underscore report and job underscore definition underscore sample. Let's start with the Alerts sample report. Open the command line and type the following CTM, reporting report, get. Then the name of the report we want to order, which is Alerts 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 will 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 will 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. Part 3, Control-M Client. The final step is to define report jobs in Control-M Client. We need to do the following. Ensure that runner's user is authorized to keep the job. Then define an OS job in Control-M Client. Part 3, Step 1, Runner's user. To ensure that jobs can be submitted by the specified user in Control-M Agents, open a command prompt and type CTM-WINCFG and press enter. You will see a table of contents. Select one, log in this user and then type Y. Then type S to save. Before entering the name in the runner's field in the CCM, you may need to type the full domain name of the user. Open a command line and type who am I and press enter. In this example, the full domain name is ADPROD-CUSER. Now open the CCM, highlight the agent and in the Security tab, select Run As and then add the run as user. You have seen that in this example, in the runner's user field, we have added ADPROD-CUSER. Enter the password, click Test and then click OK. ADPROD-CUSER is now authorized to run the job. Part 3, step 2, defining the job in Control-M Client. Firstly, let's create an OS job. Add a job name and description. We've also added an application. In the command field, type the following command, which is the same one defined in Automation API. CTM reporting reports, get job-understored definition of the course sample PDF-O CTM definition PDF. In the runner's field, you'll see that we've entered ADPROD-CUSER. Then click OK. Let's do the same for the alerts job, create an OS job. In the command line and the command that we defined in Automation API, CTM reporting reports, get alerts underscore sample underscore report PDF-O CTM alerts PDF. Again, note the runner's user field and then click OK. 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 the jobs ended OK. This now concludes the job definition video. For more information about the job definition from CTM reports, seek in CTM reports online help.