This documentation supports the 20.08 version of BMC CMDB, which is available only to BMC Helix subscribers (SaaS).

To view an earlier version, select the version from the Product version menu.

Retrieving federated data stored externally by creating federated classes


You can federate data stored externally, such as a in a table in a database, by creating BMC CMDB classes and mapping them to the external data. This method of federation is also called the retrieval method. When you define federated data classes mapped to represent external data, you must make sure that they are subclasses of the BMC_FederatedBaseElement class.

The federated data class represents a portion of the information about the external source of data so that data can be viewed within the context of the data model.

After you complete the following procedure, in the Explorer, you can directly view the federated data that is related to specific CIs.

Before you begin

To retrieve federated data stored externally by creating federated classes

As an administrator, you want to create a new federated data class for information stored on an external database. It is assumed that you have already created a plug-in and data store for this database. 

  1. Open Class Manager.
    Select Class Management > Classes.
  2. Click Federated, and then click Create.

    The Create Federation page opens.
  3. Enter the details of the class you want to create:

     Steps (4)
    1. In the Namespace list, select the namespace to which you want the new class to belong.

    2. In the Name field, enter the name of the new class.
      If your organization follows any naming conventions when extending the data model, apply those conventions to this class. You can optionally enter the author name and description in the respective fields.

    3. From the Select Plug-in list, select the plug-in that you want to use to connect to the federated data.
      For example, the Calbro Services administrator would select the banking server plug-in. 
      For more information about federated data plug-ins, see Creating AR or JDBC federated data plug-ins to access data external to the CMDB.

    4. You must specify the data that you want to retrieve through the federated class:

      • (For AR plug-ins) From the Select Form list, select the AR form that you want to access.

      • (For JDBC plug-ins) From the Select Table list, select the table that you want to access.

    5. From the Form Fields list, add the fields that you want available in the new class.

    6. From the Key Attribute list, select a field as the key identifier for the new class.
      You can only select fields that have the Data Type as CHAR in the Key Attribute list. You cannot add fields of non-character data types such as ENUM as a key attribute for a federated class. For example, the Status attribute is of ENUM data type and you cannot add it as a key attribute.

  4. In the Relationship section, select the relationship class.
    The source class of the relationship must be in the BMC_BaseElement hierarchy of classes, and the destination class of the relationship must be a federated data class. You can define multiple relationships to a single class.

     Steps (6)
    1. In the Namespace list, select the namespace to which you want the new relationship class to belong.
    2. In the Class Name field, enter the name of the new class.
      If your organization follows any naming conventions when extending the data model, apply those conventions to this class. You can optionally enter the author name and description in the respective fields.
    3. (Optional) In the Author field, enter a name according to the convention in your organization.
    4. (Optional) In the Description field, enter a description that would help understand the purpose of the class.
    5. In the Qualification field, click the Launch Expression Builder button and define a qualification.
      The qualification must help you associate a CI with the federated data related to that CI. For example, a qualification $PRINTERID$ = 'AccountID' relates a specific printer CI to a federated data from the database with a matching attribute.
    6. Click Add/Edit Class Permissions, to provide permissions to various groups and roles.

Best Practice

Create a federated relationship that links the CI class to your federated data class. Define a qualification that specifies which instances from the source class are related to data in the destination class. This qualification requires matching an attribute in the federated data class to an attribute in the CI class (for example, matching IDs between two sets of CIs). 

For best performance from the BMC Remedy AR System server, the qualification should return only a limited result set from the federated repository. If your qualification returns a large amount of federated data, the BMC Remedy AR System server may experience poor performance. 

Example of a federated data class definition

The following example values are for a Calbro Services administrator who wants to create a new federated data class for computer system information stored on a Microsoft SQL Server database.

OptionExample Value
NamespaceBMC.FED
NameCAL_BankingServers
Select Plug-inThe banking server plug-in.
Select TableBankingServers
Form FieldsPrimaryKeyNamePriorityLastDataTransfer, and Workgroup
Key AttributePrimaryKey

Where to go from here


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

Comments