This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

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

Creating a CMDBf plugin

The following procedure includes an example for a Calbro Services administrator who wants to create a custom plugin for a CMDBf-compliant CMDB. You have already located the Access Point URL and the WSDL URL to the CMDB.

Use the CMDBf plugin only for federated repositories that are other third-party CMDBs. The combination of the master BMC Atrium Configuration Management Database (BMC Atrium CMDB) instance with the secondary CMDB instances constitutes a logical CMDB known as the Configuration Management System (CMS) in IT Infrastructure Library (ITIL) V3.


Do not use the CMDBf plugin to connect one BMC Atrium CMDB storing one type of data (for example, Asset Management data) to another BMC Atrium CMDB storing another type of data (for example, Change Management data). Only one BMC Atrium CMDB should function as the single source of reference for all Configuration Items (CIs) in your IT environment.

To create a CMDBf plugin

  1. Open Federation Manager.
  2. In the toolbar, click Configure Repository Plugins and Adapters.
  3. In the Configure Repository Plugins and Adapters dialog box, click New.
  4. In the General tab of the Details section, enter the following information for the CMDBf plugin:

    Parameters for creating CMDBf plugin




    Select CMDBf from the list of available adapters.

    Plugin Name

    Unique name for the plugin. This name cannot change after you save the plugin. To make the name descriptive in a meaningful, consistent way, consider using the following naming convention: <databaseType><databaseName>_PLUGIN<hostName>

    User Name

    User name to access the external source of data.


    Password to access the external source of data.

    Access Point URL

    URL of the service access endpoint, formatted as follows: * http://<hostName>:<port>/<servicePortName>*


    URL of the service WSDL, formatted as follows: * http://<hostName>: <port>/<servicePortName>?wsdls*

    For example, Allen, the Calbro Services administrator, would select the CMDBf adapter, name the new plugin CMDB_PLUGIN_CalbrSJ, and enter the user name and password to the CMDB. He would then enter an Access Point URL of *http://goldserver:9090/axis2/services/ThirdPartyCMDB_porttype*, and a WSDL URL of *http://goldserver:9090/axis2/services/ThirdPartyCMDB_porttype?wsdl*.

    Creating a CMDBf plugin
  5. Click Add.
    The Loaded column in the Configure Repository Plugins and Adapters dialog box reads No for the new plugin.
  6. In the list of repository plugins, select the new plugin.
  7. Click Show XML.
  8. In the Plugin XML dialog box, copy all of the text from <plugin> to <\plugin>, including those tags.
  9. On the plugin server computer, open the pluginsvr_config.xml file for editing.
    By default, the pluginsvr_config.xml file is in the <installDir>\BMC Software\AtriumCore\cmdb\plugins\shared directory.
  10. In the <pluginsvr_config> section of the pluginsvr_config.xml file, paste the <plugin> text that you copied from the Plugin XML dialog box in step 8 as a new <plugin> entry.
  11. Save and close the pluginsvr_config.xml file.
    The Loaded column in the Configure Repository Plugins and Adapters dialog box displays No when you first create the new plugin.
  12. Click Refresh.
    The Loaded column in the Configure Repository Plugins and Adapters dialog box now should display Yes for the new plugin.
    If the Loaded column continues to display No, one of the following conditions exists:
    • An error occurred in connecting to the external data source. Examine the AtriumPluginSvr.log file for errors. By default, the AtriumPluginSvr.log file is in the <installDir>\BMC Software\AtriumCore\Logs directory.
    • The external data source returns no external tables. No errors are logged in this case.
  13. If your BMC Atrium CMDB environment uses a server group, make sure the same plugin is configured on all servers in the server group. Repeat the following steps for each server:
    1. Copy the same plugin configuration information in the pluginsvr_config.xml file for each server. Make the appropriate changes in the <filename> and <pathelement> tags to correct the jar paths for the local server if required.
    2. Copy and paste the Server Plugin Alias entry in the ar.cfg file. Change the server name to the local server.
    3. Restart the server.
  14. Close the Configure Repository Plugins and Adapters dialog box.
    You now must create a data store to represent the external data in your CMDBf-compliant CMDB. For more information, see Managing federated data stores.
Was this page helpful? Yes No Submitting... Thank you