Modifying the IBRSD.conf file

You can configure some properties related to BMC Service Resolution that are available in the IBRSD.conf file on TrueSight Infrastructure Management, located at:

  • (Windows) <InstallationLocation>\pw\integrations\ibrsd\conf\IBRSD.conf
  • (Linux) <InstallationLocation>/pw/integrations/ibrsd/conf/IBRSD.conf

Alternatively, you can use this location path: %IBRSD_HOME%/conf

These properties can help you with incident management as a result of the integration between Infrastructure Management and BMC Remedy IT Service Management (BMC Remedy ITSM) or BMC Remedyforce.

Note

Properties other than the ones listed in the following table are internal and must not be changed.

PropertyDescription
itsmIntrConnectionTimeout

Indicates the maximum time (in milliseconds) to wait between two retries after the BMC Remedy ITSM (or BMC Remedyforce) connection drops.

Default: 300000

itsmIntrConnectionRetryCount

Indicates the maximum number of tries before declaring BMC Remedy ITSM (or BMC Remedyforce) as unreachable.

Default: 3

ThreadPool.initialSize

Governs the number of incidents that must be created simultaneously. This value can be changed to increase the incident throughput as a result of the Infrastructure Management and BMC Remedy ITSM (or BMC Remedyforce) integration.

Note: The value of this property must match the value of the ThreadPool.maxSize property.

Default: 2

ThreadPool.maxSize

Governs the number of incidents that must be created simultaneously. This value can be changed to increase the incident throughput as a result of the Infrastructure Management and BMC Remedy ITSM (or BMC Remedyforce) integration.

Note: The value of this property must match the value of the ThreadPool.initialSize property.

Default: 5

fallbackIncidentCreateSoapWSURL

Used for creating an incident on BMC Remedy ITSM.

In the URL value, the following portions are constant, the remaining portions are variable. You can change the variable portions if you have changed the URL on BMC Remedy ITSM.

  • armidtierprotocol
  • armidtierhost
  • armidtierport
  • ARSServerName

Default: armidtierprotocol://armidtierhost:armidtierport/arsys/services/ARService?server=ARSServerName&webService=HPD_IncidentServiceInterface

fallbackIncidentOutboundSoapWSURL

Used for retrieving the incident information from BMC Remedy ITSM.

In the URL value, the following portions are constant, the remaining portions are variable. You can change the variable portions if you have changed the URL on BMC Remedy ITSM.

  • armidtierprotocol
  • armidtierhost
  • armidtierport
  • ARSServerName

Default: armidtierprotocol://armidtierhost:armidtierport/arsys/services/ARService?server=ARSServerName&webService=HPD_IncidentOutboundEvent

fallbackOutageCreateSoapWSURL

Used for creating an outage in BMC Remedy ITSM.

In the URL value, the following portions are constant, the remaining portions are variable. You can change the variable portions if you have changed the URL on BMC Remedy ITSM.

  • armidtierprotocol
  • armidtierhost
  • armidtierport
  • ARSServerName

Default: armidtierprotocol://armidtierhost:armidtierport/arsys/services/ARService?server=ARSServerName&webService=AST_CIUnavailabilityInterface

remedyforce.sandbox

Useful if you want BMC Service Resolution to connect with a nonproduction BMC Remedyforce setup for testing purposes.

You need to add this parameter manually in the IBRSD.conf file.

The value must be in the format: <HTTP/HTTPS>://<RemedyforceHostName>/services/Soap/u/30.0

Example: remedyforce.sandbox=https://test.salesforce.com/services/Soap/u/30.0

delaybetweenpolling

Governs the polling interval (in seconds) between incident creation and getting incident information from BMC Remedy ITSM to Infrastructure Management. Each time an incident is created, Infrastructure Management gets the incident information (as an INFO event) from BMC Remedy ITSM. This value governs the delay between the two polls. 

Default: 10

Related topic

Extending your system capabilities

Was this page helpful? Yes No Submitting... Thank you

Comments