Configuring BMC Client Management

To use BMC Client Management (BCM) with FootPrints, you must install BCM separately at a location that the server can access. This installation is not part of FootPrints installation.

For more information about installing BCM, see BMC Client Management documentation.

For information about the supported versions, see Product matrix compatibility.

BCM and Java OpenJDK 11 guidelines

Because Java OpenJDK 11 is not supported on a 32-bit operating system, BCM is not supported on a 32-bit master server. Ensure that you upgrade a 32-bit BCM master to a 64-bit operating system.

BCM 12.8 and FootPrints 20.19.01 support Java OpenJDK 11. FootPrints now provides the BCM console in executable (.exe) format. If you have not upgraded to BCM 12.8, perform the following steps:

1. Stop the Tomcat service.

2. Run the following query in the FootPrints database:
   For SQL Server

   update fpscdb001_system.dflt_cfg_setting_val set boolean_val = 0 where cfg_setting_id = (select cfg_setting_id from [fpscdb001_system].[cfg_setting] where cfg_setting_const='useExecutableBcmConsole');

   For PostgreSQL

   update fpscdb001_system.dflt_cfg_setting_val set boolean_val = false where cfg_setting_id = (select cfg_setting_id from fpscdb001_system.cfg_setting where cfg_setting_const='useExecutableBcmConsole');

   fpscdb001_system is a schema name and might be different for your installation. The query will ensure that FootPrints supports the legacy JNLP console.

3. Start the Tomcat service.

Enabling BCM in FootPrints

After BCM is installed, you must enable it in FootPrints:

• At the system level
• In the workspaces that will use the integration

Enabling BCM gives FootPrints access to information about devices in your environment. When agents select a contact, FootPrints searches BCM for associated assets and then shows that information to the agent, who can act on it. Also, users can select assets when opening a ticket.

Configuring integration within BCM

In BCM, you must specify the External Integration properties for the server that FootPrints will access.

You can select the:

• language for the alert
• fields to determine where and how alerts will be created
• sub-category and severity for generating alerts
• alerts you want to receive

You can also select specific alerts in each category.

You can receive event notifications for:

• BCM Application
• Discovery and Inventory
• Applications and Application licensing
• Compliance
• Agent-based Monitoring

Each alert creates a ticket in FootPrints, so select alert settings carefully to prevent unnecessary tickets. Closing the tickets sets the alert to Resolved and closes the ticket in BCM.

Where to go from here

The required next step is to integrate BCM with FootPrints by configuring the BCM connection as explained in Integrating-BMC-Client-Management-with-FootPrints. If you skip this step, communication between the two applications will not work.