Overview of the BMC Remedyforce integration with BMC Client Management
When BMC Remedyforce and BMC Client Management are integrated, staff members can perform the following actions:
- Start the BMC Client Management console from the CMDB Manager in BMC Remedyforce.
- View the asset summary of devices imported from BMC Client Management.
- Perform actions on the BMC Client Management device imported in BMC Remedyforce.
- Create service request definitions (SRDs) and incident templates that deploy operational rules and make them available to Self Service clients.
- Attach BMC Client Management operational rules to Task templates to deploy the operational rules on BMC Client Management devices.
- Search, import, and link a device to an incident or service request.
- Deploy operational rules on a BMC Client Management device.
The first time users connect to BMC Client Management from BMC Remedyforce, the BMC Client Management Authentication dialog box is displayed. In this dialog box, users must enter their BMC Client Management credentials. If the credentials are correct, BMC Remedyforce stores the user name in the FootPrints Login ID field of the user record. Users need to enter their credentials for future connection attempts only if they change their BMC Client Management password. To display the FootPrints Login ID field in user records, system administrators must edit the layout and add the FootPrints Login ID field to the layout. To prevent users from editing the BMC Client Management user name stored in the FootPrints Login ID field, system administrators must also enable the Validate_FootPrints_Login validation rule. For more information, Configuring the integration between BMC Remedyforce and BMC Client Management.
If you are integrating with BMC FootPrints Asset Core 11.7 or later (known after version 12.0 as BMC Client Management), you have the option to enable the enhanced UI. In this case, BMC Remedyforce uses the Representational State Transfer (REST) web API in BMC Client Management to retrieve device data and perform actions on the devices from the CI Actions window. Users do not have to start the BMC Client Management console to perform these actions. For information about the REST web API in BMC Client Management, see the BMC Client Management Help.
The following table highlights how actions in the Asset Core Actions menu work differently based on availability of the enhanced UI (CI Actions window).
Action | Description |
---|---|
Version 11.7 or later (with enhanced UI enabled) | |
Selecting the following actions:
| Downloads a JNLP file. You must open the JNLP file with Java Web Start to start the BMC Client Management console and perform the selected action. |
Selecting the following actions:
| Performs the corresponding action on the BMC Client Management device without starting the BMC Client Management console |
Selecting the following actions:
| Displays the corresponding device data on a separate tab in the CI Actions window. The BMC Client Management console is not started to perform these actions. Note: You can also perform other actions on the selected device from within the CI Actions window. For more information, see Managing BMC Client Management devices from the CI Actions window. |
Version 11.7 or later (with enhanced UI not enabled) and Version 11.6 | |
Selecting any except the following actions:
| Downloads a JNLP file You must open the JNLP file with Java Web Start to start the BMC Client Management console and perform the selected action. |
Selecting the Audit Now action | Sends the audit request to the device, without starting the BMC Client Management console |
Selecting the Advanced Actions option | Opens the Select From Asset Core Operational Rules window |
Selecting the Inventory Summary action | Opens the Asset Summary page |
The following figure illustrates the architecture of the integration between BMC Remedyforce and BMC Client Management.
Integration between BMC Remedyforce and BMC Client Management
Comments
Log in or register to comment.