Creating a Batch Job for FIM compliance

BMC recommends that you run the Discover Job before each Snapshot Job. By doing so, you eliminate the need to keep track of new servers, additions and deletions of files and directories, and changes to parts and exclusion rules in the component templates. You can use a Batch Job to combine the Discover and Snapshot Jobs so that they always run together.

To combine Discover and Snapshot Jobs into a Batch Job

Use this procedure to combine a Discover Job and a Snapshot Job. The Snapshot Job executes immediately after the Discover Job ends.

1. In the Jobs folder, right-click the folder in which you want to store the Batch Job and select New > Batch Job.
   
2. On the New Batch Job window, click Add Jobs at the top of the left panel.
   
3. In the popup dialog box, expand the Jobs folder, select the jobs you want to add, and click OK.
   
4. If necessary, use the up/down arrows at the top of the left pane to put the jobs in the correct order of execution, with the Discover Job first.
5. On the Batch Job Options tab, name the Batch Job. In the Execution Options section, select Execute jobs sequentially. Then click Add Servers at the bottom right.
   
6. In the popup dialog box, select Use Servers From Individual Jobs and click OK. Alternatively, you can select a server smart group.
7. Click the Schedules tab. Then click Add Schedule .
   

8. Create a recurring schedule for the Batch Job and click OK.

   Warning

   Typically, you schedule these jobs to run within your scheduled maintenance timeframe.

   

9. Click the Properties tab. Consider whether to set values for the following properties to control job timeouts.

   • JOB_PART_TIMEOUT
   • JOB_TIMEOUT

   The default value for both of these properties is zero, which means that the jobs never time out. For some customers, it might be preferable to ensure that the Batch Job executes within a maintenance timeframe. In that case, set the properties to values other than 0.

10. To save the job, click OK in the Batch Job window.
11. Repeat this procedure for other operating systems. Create a Batch Job for each type of OS in your data center that needs FIM-PCI monitoring. The following example shows the jobs for Linux and Windows PCI FIM processing.
    
    Depending upon time requirements and available TrueSight Server Automation Application Server resources, you can schedule the OS-specific Batch Jobs to run simultaneously.