This documentation supports the 21.05 version of BMC Helix ITSM: Asset Management. To view an earlier version, select the version from the product version menu.

Configuring your system to work with third-party software provider

As a user, you can access third-party-provided usage information from the SAM Console.

Perform the following steps to access third-party usage information:

  1. Create a view in the local discovery database with the appropriate columns, as described in Creating the view for software usage information.
  2. Create the federated class with the correct field ID, as described in To create the view of software usage information.
  3. Add the nameSpace _Integration_ID attribute to BMC_BaseElement and data sync it.
  4. Update pluginsvr_config.xml under the BMC Atrium CMDB path and ar.conf to include the federated plugin for the discovery source, as described in Registering the plugin in plugin_config.xml and Registering the plugin in ar.cfg.
  5. In BMC Helix ITSM: Asset Management, configure the AST:ConfigUsageProvider form properly, as described in Configuring the AST:ConfigUsageProvider form.
  6. Restart the AR System server.
Related topic

Retrieving external data by using federated plug-ins and classes Open link

After you have completed these steps, you can access the software usage feature from BMC Helix ITSM: Asset Management. The software usage feature works with any discovery source, provided all the setup is performed as described.

To create the view for software usage information

A namespace must be chosen for the discovery source to categorize and partition the data. A view in the local database must include the following columns:

  • nameSpace _Integration_ID
  • Last_Used_Date
  • Num_Times_Used_in_180_Days
  • Num_Times_Used_in_30_Days
  • Num_Times_Used_in_90_Days
  • Product_Name

To create the federated class with the correct field IDs

The discovery source, such as BMC BladeLogic Configuration Automation, must federate the software usage information into BMC Helix CMDB. Install the federated class that is federating the usage information. BMC BladeLogic Configuration Automation discovery installs the BCAC:BCAC_Software_Usage federated class as part of the CDI version 8.0 or later.

For any other third-party discovery source, you must make sure that the federated class for the discovery source exists. The federated class brings in the fields from the view described in Creating the view for software usage information. Make sure that fields IDs are specified as listed in the following table.


Field IDs for federating software usage information

Field

Field ID

nameSpace _Integration_ID

Generate a new one and register it

Last_Used_Date

400016300

Num_Times_Used_in_180_Days

303964300

Num_Times_Used_in_30_Days

303964100

Num_Times_Used_in_90_Days

303964200

Product_Name

240001002

You must register the federated class in BMC Atrium Core. You can verify the registration in the Class Manager Console.

The following figure shows a federated class in Class Manager:


To register the plugin in plugin_config.xml

You must register the plugin in plugin_config.xml, which is located under path\AtriumCore\cmdb\plugins\shared. You can see example entries in the XML file.

In the following example, BMC Atrium Core is installed in C:\Program Files\BMC Software\AtriumCore, and the plugin being registered is BCAC_DISCOVERY_PLUGIN. You might need to change the path, depending on where you installed BMC Atrium Core. You must change the plugin to the name of your plugin.

<plugin>
 <name>BCAC_DISCOVERY_PLUGIN</name>
 <type>ARDBC</type>
 <code>JAVA</code>
 <filename>C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\
 federation\federation-jdbc.jar</filename>
 <classname>com.bmc.atrium.federation.jdbc.JdbcAdapter</classname>
 <pathelement type="path">C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\db2jcc-3.3.54.jar</pathelement>

 <pathelement type="path">C:\Program Files\BMC 
Software\AtriumCore\cmdb\plugins\db2jcc_license_cu-3.3.54.jar</pathelement>
 <pathelement type="path">C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\jconn2-5.5.jar</pathelement>
 <pathelement type="path">C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\jconn3-6.0.5.ESD7.jar</pathelement>

 <pathelement type="path">C:\Program Files\BMC 
Software\AtriumCore\cmdb\plugins\ojdbc5_g-11.1.0.6.0.jar</pathelement>
 <pathelement type="path">C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\sqljdbc-1.2.jar</pathelement>
 <pathelement type="path">C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\sybase_client-5.jar</pathelement>

 <pathelement type="path">C:\Program Files\BMC 
Software\AtriumCore\cmdb\plugins\federation/federation-common.jar</pathelement>
 </plugin> 

To register the plugin in ar.cfg

You must register the plugin in ar.cfg, which is located in .\ARSystem\Conf. In the following example, the plugin is named BCAC_DISCOVERY_PLUGIN and the server is named myServer. You must change the plugin to the name of your plugin and myServer to the name of your server.

Server-Plugin-Alias: BCAC_DISCOVERY_PLUGIN BCAC_DISCOVERY_PLUGIN_myServer_:9556

To configure the AST:ConfigUsageProvider form

You must specify the discovery source for usage information in the AST:ConfigUsageProvider form. Provide the namespace and the class name of the federated class that is being used to provide the data. After you make these changes, you must restart the AR System serverfor the change to take effect.

To access the usage information

After the usage federated class and other related configuration is done, IT Asset Managers can access the usage information about the SAM Console.

The following figure shows the Software Usage console:

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

Comments