This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Using Atrium Integrator sample jobs

You can use a sample job as a staring point while creating a complex job. Sample jobs and transformations can be accessed from the BMC SAMPLES folder in BMC Atrium Integrator Spoon or from the jobs list in the left panel in Atrium Integrator console.

Sample jobs are published only after BMC Atrium Core is installed. Sample jobs won't be published if Atrium Integrator is installed without BMC Atrium Core.

The following table, lists the available sample jobs and their usage.

Sample job usage

Sample job

Usage

AISAMPLE_MachineOS _DELTA

Job: Use this job to capture data from CSV and populate it into CMDB. When you run this job, for the first time, entire data from the CSV is populated in CMDB. Next time when you run the job, only the delta is captured wherein, the data is populated incrementally. This job also establishes parent-child relationships between the classes. This sample is designed to capture data of Computersystem and Operatingsystem classes and populate it into CMDB. A relationship is created between both the classes and they are associated to the MachineOS class in parent-child relationship.

AISAMPLE_Computersystem _DELTA

Transformation: These transformations capture data from CSV file and populate the data into CMDB. When the transformations are executed, for the first time, entire data from the CSV is populated in CMDB wherein, for the subsequent execution it is incremental where only the delta is captured. These transformations function using the NGIE: Delta form which, initially stores the record pertaining to the transformation name and default time stamp i.e. 01/01/1970. When the transformations are executed, they capture the max date from the source file and replace the existing timestamp in the NGIE:Delta form. Next time when the transformations are executed, the ARInput step reads the record and AROutput step fetches the time stamp from the NGIE: Delta form. Only records created after the timestamp recorded in the NGIE: Delta form are populated into CMDB.

AISAMPLE_Operatingsystem _DELTA (non-delta transformation)

Transformation: These transformations capture data from CSV file and populate the data into CMDB. When the transformations are executed, for the first time, entire data from the CSV is populated in CMDB wherein, for the subsequent execution it is incremental where only the delta is captured. These transformations function using the NGIE: Delta form which, initially stores the record pertaining to the transformation name and default time stamp i.e. 01/01/1970. When the transformations are executed, they capture the max date from the source file and replace the existing timestamp in the NGIE:Delta form. Next time when the transformations are executed, the ARInput step reads the record and AROutput step fetches the time stamp from the NGIE: Delta form. Only records created after the timestamp recorded in the NGIE: Delta form are populated into CMDB.

AISAMPLE_CompOS _DELTA

Transformation: This transformation creates relationship between both the child classes and associate them to a parent class. This transformation associates child -Computersystem and Operatingsystem class to parent MachineOS class. The relationship source for this association is .csv file that stores the relationship information available at:
diserver
data-integration
NGIESample
bmc_<classname>.csv

Job_Comp_Proc_RELATIONSHIPS

Job: Use this job to capture data from CSV and populate it into CMDB. When you run this job, for the first time, entire data from the CSV is populated in CMDB. Next time when you run the job, only the delta is captured wherein, the data is populated incrementally. This job also establishes parent-child relationships between the classes. This sample is designed to capture data of ComputerSystem CI then Processor CI. And then a relationship is created between both the CIs under the HostedSystemComponents class.

BMC_Computer_System_CSV

Transformation: These transformations capture data from CSV file and populate the data into CMDB. When the transformations are executed, for the first time, entire data from the CSV is populated in CMDB wherein, for the subsequent execution it is incremental where only the delta is captured.

BMC_Processor_CSV

Transformation: These transformations capture data from CSV file and populate the data into CMDB. When the transformations are executed, for the first time, entire data from the CSV is populated in CMDB wherein, for the subsequent execution it is incremental where only the delta is captured.

BMC_Comp_Rel_Processor

Transformation: This transformation captures the relationship between two or more classes defined in a flat file source. This transformation uses CMDB lookup to lookup the data in class tables. After getting a match, Instance ID from the tables are captured. The parent Instance ID is loaded as SourceInstanceID and child's Instance ID is loaded as DestInstanceID with other values.

Job_CSV_CMDB_COMPUTERSYSTEM

Job: Use this job to capture data from CSV and populate it into CMDB.

BMC_Computer_System_CSV

Transformation: This transformations capture data from CSV file and populate the data into CMDB. When the transformations are executed, for the first time, entire data from the CSV is populated in CMDB wherein, for the subsequent execution it is incremental where only the delta is captured.

Job_XML_CMDB_MONITOR

Job: Use this job to capture data from XML and populate it into CMDB. This sample job runs an XML transformation and populates BMC_Monitor Class.

BMC_Monitor_XML

Transformation: This transformation captures data from XML file and populates into CMDB. This transformation takes care of the entire initial load of data.


 Job_FileMetaLoader

Job: This job is run when you create a CSV or XML data store connection with a remote Atrium Integrator Carte server. This job runs on the remote Atrium Integrator Carte server. The job checks if the folder of files exists on the specified server. Based on the file type identified, the job populates that information in ngie: file metadata. You can use the logging information of this job to identify and troubleshoot issues related to CSV and XML datastore connections to remote Atrium Integrator Carte server.
Do not delete this job or you will not be able to create CSV or XML datastore connection with remote Atrium Integrator Carte server.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments