Creating an Atrium Integrator job to import data

An Atrium Integrator (AI) Administrator creates an Atrium Integrator job and schedules it to run repeatedly.

Before you begin

Ensure that you have the following:

• Administrator user permissions to create and manage Atrium Integrator jobs.
• At least one source data store from where you can import data.
• A target data store, which is the AR System.

Process of creating an Atrium Integrator data job

To specify the job details

1. On the CMDB Dashboard, select Jobs > Manage Atrium Integrator > Create Job.
   The Create Imports Job page opens.
2. In the Job Details section, specify the job name and description, target data store details, and the target data store to which the data must be transferred. 
   Provide the following details:

After you have entered all the job details, the page looks as follows:

To select the CI types to transfer from the external data store

1. In the Mapping section, select the CI types that you want to transfer from the external data store; for example, Computer System and Monitor, and then provide the following details:

     2.  Select the source files available for the selected data store.

To map target attributes to source columns

Mapping target attributes to source columns defines the way in which data in the source column corresponds to data in the CMDB, and the actions that you must perform when transferring data between the source and target columns. A source key or primary key uniquely identifies a row of data. After a data transfer, the source key is the link that matches a record in the external data store with its counterpart in the CMDB. 

1. To map a target attribute to a source column, select the target attribute (that belongs to the selected class) and the corresponding source column (from the CSV data store), and click Map. 
   The mapping is displayed in a tabular format.
   For some attributes, you can specify a constant value. For example, you can choose the target as Availability and assign a constant value Yes to it. 
2. Select at least one row but not all rows from the table as the source key. 
   The target attribute and the corresponding source column in the external data store make up the source key, which is the primary key. 
   You must have two or more rows in the table out of which at least one row must be selected as the primary key, and at least one row should not be selected as the primary key. 

For a CSV type of data store, the Mapping section looks as shown in the following figure:

For a database (DB) type of data store, the Mapping section looks as shown in the following figure:

For an XML type of data store, the Mapping section looks as shown in the following figure:

To enable delta data import 

1. (optional) Select Enable Data Import to import only new or updated source records since the last transfer was run.
   
   
   
2. Select the column that holds the time stamp when each record was last modified. 
   During each data transfer, only new records and those records with a last modified timestamp that is later than the most recent successful transfer are retrieved from the source.

To delete orphan records

(Optional) Select Delete Orphan Records from CMDB to mark a record as deleted from BMC CMDB when that record is deleted from the source data source. 

If this option is selected, this action is not performed when the job runs for the first time, but when the job runs subsequently, the records received in current job run are compared with previous job run, and those found to be missing from the source data source are marked as deleted from BMC CMDB.

To update the source column

Update Source Data is displayed only for database type of data stores when at least one unmapped source column belongs to "integer", "int", "number", "varchar", "char", or "string" datatypes.

1. Select Update Source Data.
2. Select the column to be updated.
   
   
   

To define the relationship mapping for the CI types to be transferred

1. Click the Relationship tab.
2. Select a parent CI from the Parent Class list.
   All the mapped CI types are shown in the Parent Class list.
3. Select a child CI from the Child Class list.
   All the mapped CI types are shown in the Child Class list. 
   This list is populated based on the CIs that you have selected on the CI Types tab.

4. Select a relationship between the parent and child class from the Relationship Class list.
   Only applicable relationships are populated in the Relationship Class list.
   If the parent and child CI belong to the same class, a message is displayed as shown in the following image. 
   
   
   If you select Yes, the  CI Types tab is displayed again. 

   You cannot create a mapping between a parent and child CI belonging to the same type.

5. To add the relationship, click Add.

6. In Logical Name For Relationship Class, enter a logical name for the relationship. 

7. Map the key column of the parent class with that of the child class by selecting a CI from the Columns list.

8. (optional) To import only new or updated source records since the last transfer was run, select Enable Data Import.
   

9. (optional) Repeat steps 2 to 6 for other CIs. 

For a CSV type of data store, the Mapping section looks as shown in the following figure:

For a DB type of data store, the Mapping section looks as shown in the following figure:

For an XML type of data store, the Mapping section looks as shown in the following figure:

To create a schedule for the job

Create a schedule for the job to run at a specific time or timed interval.

1. To create a schedule, click Add Schedule.
2. Enter a schedule name. 

3. Select the Carte Server from the list to attach the schedule to the Carte Server.
   This step is useful if you have multiple Carte servers set up in your AR server group and you want to select a particular Carte server to  be used for running this job. It also helps to balance integration job load on the AR servers. 
   

   Important

   Sometimes when you create a schedule in an Atrium Integrator job, the selected carte server might not be display in the field. Even if the default carte server value does not change, save the job. When you view the job details after saving, the server that you selected is displayed in the carte server field.

   

4. Specify the time at which you want the job to start running.
5. Specify the frequency at which you want the job to run. For example, Weekly.

6. You can choose a custom interval by selecting the Interval option and then specifying the interval.

7. Click Save to save the job.

Where to go from here

Running an Atrium Integrator job