Installing the BMC CMDB Extensions to enable integration with Atrium CMDB

The BMC CMDB Extensions enable the integration between TrueSight Infrastructure Management and the Atrium CMDB. With the integration, you can utilize configuration items (CIs) in the Atrium CMDB for service modeling. The BMC CMDB Extensions facilitates the process of updating the TrueSight Infrastructure Management Server with changes made to CIs in the Atrium CMDB.

Related topics

Installing BMC Impact Model Designer

Uninstalling BMC CMDB Extensions

BMC Service Resolution Open link

When integrating TrueSight Infrastructure Management with Atrium CMDB, you must install the BMC CMDB Extensions and components before configuring the TrueSight Infrastructure Management Server to integrate with the Atrium CMDB.

When you install the BMC CMDB Extensions, the following BMC software is installed:

Install BMC CMDB Extensions on the same computer where Atrium CMDB is installed.

  • In a server group environment, install BMC CMDB Extensions on all the servers in the server group. For more information about the server group environment, see the online documentation of BMC Service Resolution.
  • In the primary node, install the binaries and the workflow; in all other nodes, install only the binaries. Ensure that all servers are added to the group list.

See System requirements and product compatibility for Infrastructure Management for the minimum supported configuration requirements, and supported versions.

This topic provides the following information about installing BMC CMDB Extensions:

Before you begin

  • Before you begin with the installation, ensure that you have administrator privileges on Remedy Action Request System.
  • As an administrator, ensure that you have the following permissions:
    • Administrator
    • Incident Config
    • Incident Master
    • Incident Viewer
    • Incident Submitter
    • Contact Organization Admin
    • Contact Location Admin
    • Contact People Admin
    • Contact Support Admin
    • Config Group Mapping Admin
    • Config Categorization Admin
    For information about adding permissions, see  Role-based access Open link .
  • BMC recommends that you run the Remedy AR System and Atrium Core Heath check before proceeding with the installation.
  • AR user must have a fixed license.

  • If you moved the BMC Remedy Action Request database from one server to another, you should ensure that the filesystem dependencies have also been migrated before installing or upgrading the BMC Remedy Action Request database.
  • Ensure that you enable Administrative Operations on the AR Server. For information about enabling Administrative Operations, see the online documentation of BMC Remedy Action Request System.

  • Ensure that the Enable Multiple Assign Groups setting is enabled for all AR Servers. To do this, in AR Server, in the Server Information page, on the Configuration tab, select the Enable Multiple Assign Groups check box.

  • Ensure that you increase the Server-Plugin-Default-Timeout to 600 seconds and enable unqualified search in the Server Information page of AR Server.

  • Ensure that you have installed the following applications on the Remedy Action Request System server:


    Installation instruction

    Atrium Core

    To install Atrium CMDB, see the online documentation for BMC Atrium Core.

    Remedy Incident Management

    To install Remedy Incident Management, see the online documentation for BMC Remedy IT Service Management.

  • For a successful installation, ensure that your system has a minimum of 3 GB of free memory. If this requirement is not met, importing workflows to Atrium CMDB may fail.
  • On Linux or Solaris operating system, ensure that the following libraries are present in the /usr/lib folder:

To install BMC CMDB Extensions on Microsoft Windows

  1. Navigate to the BMC_TrueSight_Infra_Mgmt_11.0_ExtensionsForAtriumCMDB_Windows\Disk1 directory in the installation package.
    • If you have an installation DVD, copy the contents to a directory with write permission, and navigate to the directory.
    • If you have downloaded the installation files, navigate to the directory.
  2. Run setup.exe as an administrator.
  3. On the Welcome page, click Next.
  4. On the license agreement page, click Next.
  5. On the Directory Selection page, retain the default directory, or click Browse to select a different directory, and click Next.
  6. On the Remedy AR System Server/Atrium CMDB User Inputs page, provide the following details, and click Next.



    AR System Server Administrator Name

    AR System Server Administrator Password

    Administrator credentials to access Remedy Action Request System

    AR System Server TCP Port

    Port number of the server on which Remedy Action Request System is running. If the server is using a portmapper, then the default port number is 0.

    AR System Server Name Alias

    Host name of Remedy Action Request System or Atrium CMDB

  7. On the CMDB User permissions information page, make sure that you do not select the Deploy SDIG Workflow check box, and then click Next.
  8. Verify that the information on the TrueSight Infrastructure Management CMDB Extensions initialization page reflects your installation correctly. Click Previous to make changes, or click Next.
  9. On the Notification Service Plugin User Inputs page, enter the port number on which the Notification Service is listening for incoming connections of clients (for example, Publishing Server) that subscribe for notifications. The default port number is 1840.


    This port is different from the AR Server port. Configure your firewall to allow this port so that Publishing Server can connect to it.


  10. On the TrueSight Infrastructure Management CMDB Extensions information page, click Next.
  11. On the Installation Preview page, click Install.
    The installer displays the progress of the installation.
  12. On the Installation Result Summary page, click Next.
  13. On the Installation Summary page, click View Log to view the installation logs or click Finish to complete the installation.
  14. Restart Apache Tomcat as described in To restart Apache Tomcat on Microsoft Windows.

Important: For installing CMDB on a second server in a group

 If you are installing CMDB Extensions on the second server in a server group, ensure that the administration ranking of the second server is set to 1. With this, the installer identifies that CMDB Extensions are already installed on the earlier server, and the workflow is not installed on the second server.

To install BMC CMDB Extensions on Linux/Solaris


  • Install the TrueSight Infrastructure Management Extensions by the user using which you installed AR Server, it may be either root or non-root user.
  • Ensure that you have write permission to the ar.conf file.
  1. Navigate to the BMC_TrueSight_Infra_Mgmt_11.0_ExtensionsForAtriumCMDB_<operating system>/Disk1 directory in the installation package.
  2. Apply executable rights to all the installation files by running the following command: 

    chmod -R 755 installationDirectoryFolderName 

    installationDirectoryFolderName is the name of the folder that contains all the installation files.

    For example, chmod -R 755 Disk1

  3. Run setup.bin.
  4. Follow step 3 through step 13 as described in To install BMC CMDB Extensionson Microsoft Windows.
  5. Restart Apache Tomcat as described in To restart Apache Tomcat on Linux/Solaris.

Integrating with Atrium CMDB in an Action Request Server group

When integrating with an Action Request Server Group, you must install the BMC CMDB Extensionson:

  • The primary administrative server - Installing on the primary administrative server creates the necessary forms, workflow, and data. It also deploys the Impact Model Designer on the primary server.
  • Each server that has the reconciliation function enabled - Installing on each server is necessary to install the Notify ARDBC plugin. For more information, see  Configuring the Notify ARDBC plug-in Open link .

Configuring after installation

After installing the BMC CMDB Extensions, a BMC.ARF.BiARS_SIMINIT error might be displayed in the TrueSight Infrastructure Management operator console, while creating incidents.

From the Remedy Developer Studio, disable the BiiARS_HPD:OutBoundStagingForm_INCIDENTINFO'! filter.

Was this page helpful? Yes No Submitting... Thank you


  1. Mandar Katdare

    Steps to install CMDB Extensions silently, including a possible sample options.txt file need to be documented here.

    Jan 03, 2018 10:00
    1. Mukta Kirloskar


      We currently do not have an option to install CMDB Extensions silently.

      Thanks and regards,


      Feb 26, 2019 01:53
  2. Fotis Koutsoukos

    Hello, The link in the following text regarding BMC Remedy Action Request System documentaion is redirecting to unsupported content

    "In a server group environment, install BMC CMDB Extensions on all the servers in the server group. For more information about the server group environment, see the online documentation of BMC Remedy Action Request System." --> redirection to -->


    " in the primary node, install the binaries and the workflow; in all other nodes, install only the binaries. Ensure that all servers are added to the group list."

    Where are the binaries located? the steps on how to install the binaries on a CMDB node are missing

    Sep 10, 2018 11:57
    1. Mukta Kirloskar


      Thank you for your comment. I have fixed the link. I will also update the document for installing binaries after talking to the R & D team.

      Thank you!

      Feb 26, 2019 02:05
  3. Tord Nilsson

    Hi Can you clarify that installing CMDB Extensions on the second server (In a server group) you need to set the second server to have administration ranking as 1. The installer will then by it self identify that the CMDB Extensions is alredy installed on the first server earlier (And will not install any workflow)

    The above is not clear in the documentation Thanks! /Tord

    Jun 12, 2019 05:03
    1. Mukta Kirloskar

      Thank you, Tord. I will update this information.

      Jun 26, 2020 02:08
      1. Mukta Kirloskar

        We have added it in the documentation, and it will be soon available when we next publish the documents.

        Thank you for your inputs.

        Jul 14, 2020 10:40
  4. Roland Pocek

    please refer to the kb article and correct the needed permissions when installing the extensions

    Jul 13, 2021 04:56