Docs.bmc.com will undergo a brief maintenance outage 27 March 2025. The site will be unavailable for ten minutes starting at 6:30 AM CDT/5 PM IST.

Configuring an Atrium Integrator job for a Load step


To import data from various sources, you must create an Atrium Integrator job for each Load step. These jobs provide the details that are required to find the source data store, transform the data using the specified rules, and store the data in the required target data store.

Important

To configure an Atrium Integrator job for a Load step

  1. In the Load Parameters panel in the Step (New) window, select the required Atrium Integrator job name from the following choices:

    Job name

    Description

    Activity_Process_Setup

    Imports activity template, activity configuration rules, and activity configuration notification rule records

    CI-CMDB

    Imports computer system, processor, product, and operating system CIs

    Company

    Imports company and company alias records

    Change_Process_Setup

    Imports the following records: approver lookup, change template, change template support group association, change template associations, and task template association

    Financials

    Imports configuration cost center repository and cost center user-defined association records

    Foundation_Process_Setup

    Imports assignment and alternate records

    Generic_Catalog

    Imports generic catalog, generic product service associations, and generic company module association records

    Geography

    Imports postal code records

    Incident_Process_Setup

    Imports the following records: incident template, incident template support group association, incident template associations, scripts, group event mapping, decision tree, decision tree main branch, decision tree branch, and decision tree branch item

    Load Service Agreement

    Imports service agreement and its associated milestone, action, and penalty rewards records

    Load Service Target

    Imports service target and its associated milestone, action, and goal schedule records

    Load SLM Contract

    Imports BMC Service Level Management contract

    LDAP_People

    Imports people from an LDAP server to the CTM:LoadPeople form

    Location

    Imports site, site alias, region, site group, and site company association records

    OperationalCatalog

    Imports operational catalog and operational catalog association records

    People

    Imports people records

    PeopleOrg

    Imports people organization records

    Product_Catalog

    Imports the following records: product catalog, product alias, product company association, product model version, product model version patch, and product catalog alias mapping

    Release_Process_Setup

    Imports the following records: release milestone exit criteria, release approver lookup, release template, release template associations, release template support group associations, release configuration rules, release configuration prioritization, release configuration notification rules, release milestone phases

    Support_Group

    Imports the following records: support group, support group assignment, support group alias, support group on call, business work days, and business holiday

    System_Setup

    Imports pager service configuration records

    Task_Process_Setup

    Imports the following records: task group template, task template, task association template, task flow template, task assignment configuration, task variable template, and task variable mapping

    Transactional_Activity

    Imports activity and activity work information records

    Transactional_Asset

    Imports asset work log, asset to asset relationship, asset people, and CI records

    Transactional_Change

    Imports infrastructure change, change work log, change impacted areas, and signature records

    Transactional_Contract

    Imports contract records

    Transactional_Incident

    Imports incident, incident association, incident work log, and incident impacted area records

    Transactional_Problem

    Imports the following records: problem investigation, problem investigation work log, problem impacted areas, problem known error, problem known error work log, problem solution database, problem solution alias, problem solution work log, and problem solution database additional mapping

    Transactional_Release

    Imports release worklog, release signature, and release records

    Transactional_Shared_Components

    Imports support group associations for broadcasts, and financial data (including costs and payments) for applications.

    Transactional_Task

    Imports tasks, task group, and task work information records

    The Variables panel displays the following information which is used by Atrium Integrator to connect the BMC Remedy AR System server with the import process.

    Variable

    Value

    AR_USER

    BMC Remedy AR System server user name

    You only need to make this change once. If you modify AR_USER, the new value propagates to all the Load steps.

    Best practice
    If you have selected either the Transactional_Asset or CI-CMDB Atrium Integrator job, we recommend that you keep BMC.ITSM.CI.DATA, which is the default, as the DATASETID variable to ensure that the data is reconciled correctly with the production dataset. You will need to highlight the DATASETID variable in the Variables table to display the DATASETID entry field.

    Do not load data directly to the BMC.ASSET production dataset.

  2. Select either the name of the User's data spreadsheet (created using Spreadsheet Management) that will be attached to the Atrium Integrator job from the Spreadsheet drop-down list or click Add to browse locally and manually add the spreadsheet as an attachment.
    This process will also pull in the attachments .zip file if one exists for the spreadsheet.

    If you have attachment fields with data in your ARX files or Excel spreadsheets, you must add an attachment .zip file. To load spreadsheets with attachments:

    1. In the attachment columns in your spreadsheet, enter the following path for your files and save your changes: optionalSubFolderName\fileName
    2. Create a folder on your local hard drive.
      If you are attaching files that have a shared file name you must put these in separate local sub-folders before zipping them. Your spreadsheets will need to reference these sub-folders.
    3. Put all of the files that you want to attach to the staging form record, and have identified in the attachment columns of your spreadsheet, in this folder. You can create subfolders if required.
    4. Zip up your files and name the .zip file folderName.zip.

      Warning

      The file must be a .zip file. No other compression formats are supported.

      When you export an ARX file, the attachment directory is automatically created and you can make a zip file by zipping up the directory.

      Important

      If you remove a spreadsheet, by clicking Remove, you will also remove the attachments .zip file.

  3. To save the step, click Save.
     After your Data Management job has a status of Built, and you choose to run the job, the Atrium Integrator job runs. When the job finishes running, the Load step is set to Completed.