Configuring BMC Client Management
To use BMC Client Management (BCM) with FootPrints, BCM must be installed separately at a location that the server can access. This operation is not part of FootPrints.
For more information setting up BCM, see BCM documentation.
To learn about the supported versions, see Product matrix compatibility.
After BCM is installed, you must enable it in FootPrints:
- At the system level
- In the workspaces that will use the integration
The information about devices in your environments is brought into FootPrints. When agents select a contact, BCM is searched for associated assets and shows that information to the agent, who can act on it. Also, customers can select assets when opening a ticket.
Configuring integration in BCM
In BCM, you must specify the External Integration properties for the server that FootPrints will access. You can select a language, which fields to match for alerts, and which alerts you want sent.
You can select a category and severity for generating alerts. You can also select specific alerts in each category. Notifications can be sent for:
- BCM issues
- Asset discovery and inventory changes
- Application changes and license warnings
- Compliance issues
Each alert creates a ticket in FootPrints, so select alert settings carefully to prevent a flood of unnecessary tickets. After the ticket is closed, the alert is set to Resolved, and it is closed in BCM.
Next step
You must also configure the BCM connection in FootPrints. If you skip this step, communication between the two applications will not work.
Related topics