Validating integrations
BMC Service Resolution 3.0 integrates BMC TrueSight Operations Management/BMC ProactiveNet and BMC Remedy IT Service Management (ITSM) components. After you install BMC Service Resolution 3.0, you can validate that the integrations are working correctly.
The following topics are provided:
To validate the integrations
- Open the BMC TrueSight Operations Management/BMC ProactiveNet Operations console.
- Click Options > Administration.
- In the Intelligent Ticketing Configurations section, next to the Intelligent ticketing integration validation label, click Test.
- In the Validate Intelligent Ticketing Integration With Single Click window, click Test.
The results of the validation test are displayed on the screen.
Results of the single-click validation test
If the integration failed, errors are displayed on the screen. For more information, see Resolving validation test errors.
Resolving validation test errors
Use the information provided in this topic to understand the checks and the corrective actions to be taken if any of the check show an integration failure during the end-to-end integration test.
Test: Check Service Desk Accessibility
Description | Verifies that the BMC Service Desk is accessible and that you are able to ping the AR System server. Note: This test checks whether the AR System server is accessible. However, if pinging systems through a firewall is disabled in your environment, this test fails even though the AR System server is accessible through web services. As a result, the other end to end validation tests will be successful. If the Check Incident test is successful, it indicates that the end to end test was successful and the failure message associated with the Check Service Desk Accessibility test can be ignored. |
---|---|
Expected Result | BMC Service Desk is accessible. |
Corrective action | Ensure that the AR System server host is in the same network as that of the BMC TrueSight Operations Management/BMC ProactiveNet server. |
Test: Check Service Desk Availability
Description | Validates connection to the AR System server. |
---|---|
Expected Result | Connection to the AR System server is established, and the web service call to the mid tier is successful. |
Corrective action | Verify the <iBRSD_Home>/conf/ibrsd.conf file and ensure that the following entries are added and are correct.
|
Test: Send Event to cell
Description | Validates that events from BMC TrueSight Operations Management/BMC ProactiveNet are being sent to the cell host. |
---|---|
Expected Result | BMC TrueSight Operations Management/BMC ProactiveNet events are sent successfully. |
Corrective action | Verify that the cell host is up and running; go to the cell host and run the following command at the command prompt: mcstat –n <cellName> If the cell is up and running, the status is shown as Running in the command prompt. |
Test: Check event propagation to gateway
Description | Validates that events from the BMC TrueSight Operations Management/BMC ProactiveNet cell are being sent to the integration gateway. |
---|---|
Expected Result | BMC TrueSight Operations Management/BMC ProactiveNet events sent successfully. |
Corrective action | Ensure:
If the cell cannot propagate events to the gateway, go to the cell host, and run the following command at the command prompt: mcontrol prop To verify whether the propagation is successful, check the mc_propagations slot. This slot should contain ibrsd as the value. For more information, see Troubleshooting-event-propagation. |
Test: Check incident
Description | Validates that incidents are created through the integration gateway. |
---|---|
Expected Result | Incidents are successfully created. |
Corrective action | Enable and review the following logs:
For information about enabling AR System server logs, see Enabling-server-side-AR-System-logs, Enabling-logs-for-performance-issues, and Troubleshooting-incident-creation.
|
Related topics