Configuring the connectors for Proactive Service Resolution
You must add connection configurations and connector accounts to the connectors required for Proactive Service Resolution (PSR).
- Configure the TrueSight Ops Mgmt for PSR and ITSM for PSR connectors to enable integration with TrueSight Operations Management on-premises.
- Configure the Helix Ops Mgmt for PSR and ITSM for PSR connectors to enable integration with BMC Helix Operations Management (TrueSight Operations Management in the cloud).
Important
If you have configured automatic routing based on Component Alias, before you activate the flow, configure a global default assignment record to manage events without a Component Alias.
Additionally, you can set permissions and add throttling controls.
For more information about the end-to-end configuration process, see Configuring connectors.
To configure the TrueSight Ops Mgmt for PSR connector
The TrueSight Ops Mgmt for PSR connector creates new events and updates existing events in BMC TrueSight Operations Management.
The following slides show how to add the TrueSight Ops Mgmt for PSRconnection configuration in BMC Helix Integration Service.
To configure the TrueSight Ops Mgmt for PSR connector, provide the following information:
| Required/Optional | Parameter | Description |
|---|---|---|
| Required | Name | Enter a unique configuration name. |
| Optional | Description | Enter a description of the configuration. |
| Required | Site | Select the site to be connected to the connector. The site specifies where the service is hosted and includes information that the connector requires to operate. |
| Optional | Number of instances | Enter the number of instances of the connector that you want to run at the selected site. This helps you to scale up when many flows are running by using the same configuration. |
| Optional | Selected by default | Select this field to make the connector configuration the default configuration, especially if you have multiple connector configurations. |
| Required | Enable usage | Select this check box to enable the connector. |
| Required | TSPS Server URL | Enter the URL of TrueSight Presentation Server. |
| Required | TrueSight Data Providers | Enter a comma-separated list of TSIM (TrueSight Infrastructure Management) server names that must belong to the tenant specified in TrueSight Tenant, where PSR integration must be enabled. |
| Optional | TrueSight User Realm | Enter a tenant or a realm of a user who authenticates to TrueSight Presentation Server. |
| Required | TrueSight Tenant | Enter a tenant for which PSR integration is enabled. |
| Optional | TrueSight Retry Count | Enter the count of retries to be made in case of any temporary timeout or failure. The default value is 5. |
| Optional | TrueSight Retry Interval | Enter the value that indicates a delay between the retry attempts in case of any temporary timeout or failure. The default value is 60000. |
| Optional | TrueSight Retry Concurrent Request | Enter the count of the parallel requests that a single data provider can make to create an incident. The default value is 10. |
To configure the ITSM for PSR connector
The ITSM for PSR connector creates and updates incidents in BMC Helix ITSM based on events from BMC TrueSight Operations Management.
The following slides show how to add the ITSM for PSRconnection configuration in BMC Helix Integration Service.
To configure the ITSM for PSR connector, provide the following information:
| Required/Optional | Parameter | Description |
|---|---|---|
| Required | Name | Enter a unique configuration name. |
| Optional | Description | Enter a description of the configuration. |
| Required | Site | Select the site to be connected to the connector. The site specifies where the service is hosted and includes information that the connector requires to operate. |
| Optional | Number of instances | Enter the number of instances of the connector that you want to run at the selected site. This helps you to scale up when many flows are running by using the same configuration. |
| Optional | Selected by default | Select this field to make the connector configuration the default configuration, especially if you have multiple connector configurations. |
| Required | Enable usage | Select this check box to enable the connector. |
| Required | ITSM URL | Enter the URL of the ITSM server that accepts REST calls. |
To configure the Helix Ops Mgmt for PSR connector
The Helix Ops Mgmt for PSR connector creates new events and updates existing events in BMC Helix Operations Management.
The following slides show how to add the Helix Ops Mgmt for PSRconnection configuration in BMC Helix Integration Service.
To configure the Helix Ops Mgmt for PSR connector, provide the following information:
| Required/Optional | Parameter | Description |
|---|---|---|
| Required | Name | Enter a unique configuration name. |
| Optional | Description | Enter a description of the configuration. |
| Required | Site | Select the site to be connected to the connector. The site specifies where the service is hosted and includes information that the connector requires to operate. |
| Optional | Number of instances | Enter the number of instances of the connector that you want to run at the selected site. This helps you to scale up when many flows are running by using the same configuration. |
| Optional | Selected by default | Select this field to make the connector configuration the default configuration, especially if you have multiple connector configurations. |
| Required | Enable usage | Select this check box to enable the connector. |
| Required | Helix Operations Management Server URL | Enter the URL of the Helix Monitor server for the given tenant. |
| Required | Helix Operations Management API Key | Enter the API key from the Helix Monitor server for the given tenant. Important: BMC Helix Operations Management enables you to use rotating API keys to keep systems secure if your organization foresees a security threat should the API key get compromised. If you have enabled API key rotation in BMC Helix Portal, make sure that you update the latest API key when the key is rotated. For more information about rotating API keys, see
Using rotating API keys for secure data streaming
|
| Optional | Helix Operations Management Retry Count | Enter the count of the retries to be made in case of any temporary timeout or failure. The default value is 5. |
| Optional | Helix Operations Management Retry Interval | Enter the value that indicates a delay between the retry attempts in case of any temporary timeout or failure. The default value is 60000. |
| Optional | Helix Operations Management Retry Concurrent Request | Enter the count of the parallel requests that a single data provider should make to create an incident. The default value is 10. |
Where to go from here
After you add connector configurations for the TrueSight Ops Mgmt for PSR and ITSM for PSR connectors, add connector accounts. For more information, see Adding accounts.
Important
Do not add an account for the Helix Ops Mgmt for PSR connector. The authentication is automatically done after you create and enable a flow.
Comments
We need to add an additional prerequisite. If you are using automatic routing based on Component Alias, you need to have a global default assignment record to catch any events that don't have a Component Alias before you activate the flow or the flow activation will fail.
Jon Brent Fournet , I have added a note to the topic to include this information.
None of the slides are visibile on this page?
Thank you for brining this to our notice, Kevin Simpson . I have updated the presentation links.
Please note updated page title Configuring the connectors for Proactive Service Resolution.
Log in or register to comment.