Triggering jobs to import data into BMC Helix CMDB

• Each of these jobs can have independent schedules but, must run sequentially.
• These can be long running jobs and you may need to predict the end time of a job run in order to schedule the next one in the sequence. This creates an issue in lining up schedules for jobs because it is not possible to predict when a job earlier in the chain will finish. 
• This leads to time gaps between subsequent runs or overlapping runs, which can result in inefficient utilization of the system or undesired results. 

With the triggering mechanism, you need to schedule only the first job in the sequence and the subsequent ones are triggered upon completion of the previous one. You don't need to track the schedules for normalization engine, and reconciliation engine jobs when they are run sequentially. 

The following diagram illustrates how using the triggering mechanism you can reduce manual monitoring to sequentially run Atrium Integrator, normalization engine, and reconciliation engine jobs.

To trigger jobs to import data in BMC Helix CMDB

You need to perform the following:

• Step 1: Schedule the Atrium Integrator job
• Step 2: Set up a trigger in the Atrium Integrator job
• Step 3: Trigger the normalization engine job
• Step 4: Trigger the reconciliation engine job

You have to perform these steps once. After you configure the triggers, the normalization and reconciliation jobs will be triggered automatically every time the scheduled Atrium Integrator job runs.

Step 1: Schedule the Atrium Integrator job

You can perform one of the following steps:

• Schedule the Atrium Integrator job. See, Creating-an-Atrium-Integrator-job-to-import-data
• Create an event driven Atrium Integrator job by using the Application Pending form. To create a request on the Application Pending form, see Setting up event-driven jobs in Atrium Integrator.

Step 2: Set up a trigger in the Atrium Integrator job

Perform the following steps, to ensure that after the job is completed, an entry is created in the UDM:JobLog form with the status as END. This is required to trigger the normalization engine job.

1. Log in to Mid Tier with your credentials.
2. In the Applications pane, click Atrium Integrator > Atrium Integrator Console.
   
3. In the Atrium Integrator Console, click Launch Spoon.
4. To open a job, go to Tools > Repository > Explore to open the Repository explorer dialog box.
5. Click Edit > Settings. 
   The Job Properties dialog box is displayed. 
6. Click the Log tab. 
7. Click Job. 
8. Enter the <AR server name> in the Log Connection field. 
9. Enter UDM:JobLog form name in the Log table field.
10. Click Job Entry. 
11. Enter the <AR server name> in the Log Connection field. 
12. Enter UDM:JobEntryLog form name in the Update Log table field.
13. Click OK.

Step 3: Trigger the normalization engine job

After the job is completed an entry is created in the NE:JobRun form with job status as Complete. This is required to trigger the reconciliation job.

1. Download the runNEandREJob.def and netrigger.zip files. Click the links to download the attachments. 
2. Extract the contents of the netrigger.zip file in the BMC Helix CMDB installation directory.
3. Import the runNEandREJob.def file into Developer Studio. For information about how to import object definitions, see Importing-object-definitions.
   This creates the RunNEJob and the RunREJob filter.
4. Open the RunNEJob filter. Under IfAction>RunProcess, update the following variables in the command line as needed:
   1. batchFilePath – Enter the complete path of the batch file (after extracting)
      For example, C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\ne\netrigger\runNEJob.bat
   2. NE_JobName – Enter the name of the job that you want to execute. 
   3. NE_JobType - Enter the type of the job that you want to execute.
   4. Setup a filter qualification that runs the job only after this Atrium Integrator job is completed. 
      For example,  'Status' = "End" AND 'jobName' = "<aIJOBName>"
5. Save the filter.

Step 4: Trigger the reconciliation engine job

Open the RunREJob filter and modify the run process action using the following command:

See Run-process-workflow-action-to-perform-event-driven-reconciliation for more information about run process workflow actions.

After the normalization engine job is complete, the RunREJob filter runs automatically and triggers the reconciliation engine job.

By default, the explorer - identification and merge reconciliation job is triggered. If you want to change the reconciliation job you want to trigger, you must update the command option in the runNEandREJob.def file and perform steps mentioned in Step 3.