Configuring BMC-SA-Event_Orchestration_Configuration module


This topic describes the steps to configure the BMC-SA-Event_Orchestration_Configuration module and lists the configuration items included in the module. 

Use this topic to understand the module configuration items and the configuration items that you must update to use the runbook. See the Update required column to understand whether to update the values.

To configure BMC-SA-Event_Orchestration_Configuration module

This module contains data for the event management tool and the IT Service Management system. For the out-of-the-box actions, you must configure the connection details for the endpoint systems.

  1. On the Grid Manager, click Manage > Modules and click the BMC-SA-Event_Orchestration_Configuration module.
  2. Expand the configuration tree until you can navigate to the configuration item that you want to modify.
  3. Click the configuration item that you want to modify, edit the value, and click OK to save changes.
  4. After successfully configuring the module, click the Modules tab and from the Modules in Repository list, select the module and click Activate. Module with the updated changes is successfully activated on the grid. 

General configuration items

Contains configuration items for specifying the event source and the IT Service Management system. 

Configuration item

Description

Update required?

Valid values

EventSourceType

Specifies the name of the event management tool from which the event is generated.

No

BMC_TrueSight

ITSMType

Specifies the ITSM application to be used to create incidents, change, or tasks for an event.

No

BMC_AR_System

Specifics > Adapters configuration items

Specifies the adapter names for the adapters configured and enabled on the TrueSight Orchestration grid. 

Note

Ensure that the adapter name matches the name that you specify while configuring the adapter.

Configuration item

Description

Update required?

Adapter_Invocation_Mechanism_Mappings

Contains mappings to map adapter invocation mechanism (used by AD Utilities and Common Utilities workflows) to adapter names.

This enables change in adapter names but no need to change workflow logic, in dependent modules like Credentials Store.

Click here to expand...
<mappings>
 <adapter-name invocation-mechanism="rest">RESTAdapter</adapter-name>
 <adapter-name invocation-mechanism="itsm">ITSMActorAdapter</adapter-name>
 <adapter-name invocation-mechanism="windows-command">WindowsCommandAdapter</adapter-name>
 <adapter-name invocation-mechanism="windows-powershell">WindowsPowerShellAdapter</adapter-name>
 <adapter-name invocation-mechanism="ssh">SSHAdapter</adapter-name>
 <adapter-name invocation-mechanism="itsmwebservice">ITSMWebServiceAdapter</adapter-name>
 <adapter-name invocation-mechanism="command-line">CommandLineAdapter</adapter-name>
</mappings>

No

CommandLineAdapter

Specifies the name of the command line adapter that is used to invoke shell commands on the local server.

Yes

ITSMActorAdapter

Specifies the name of the BMC Remedy AR System actor adapter.

The adapter is used to invoke actions in BMC Remedy AR System.

Yes

ITSMWebServiceAdapter

Specifies the name of the web services adapter.

The adapter is used to invoke SOAP based actions to Remedy AR System for creating and updating change requests. If any action is not supported by the Web Services adapter, the BMC Remedy AR System adapter is used.

Yes

RESTAdapter

Specifies the name of the REST adapter used for invoking REST API requests to TrueSight Orchestration and TrueSight Presentation Server targets.

Yes

SSHAdapter

Specifies the name of the SSH adapter used to invoke UNIX commands, such as accessing remote UNIX machines to perform remediation actions.

Yes

WindowsCommandAdapter

Specifies the name of the Windows Command adapter used to invoke remote Windows commands from a Windows server.

Yes

WindowsPowerShellAdapter

Specifies the name of the PowerShell adapter used to invoke commands.

Yes

Specifics > BAO configuration items

Specifies the connection details to connect to the TrueSight Orchestration peer. 

Configuration item

Description

Update required?

Default values

URL

Specifies the URL to the configuration distribution peer where the modules required for the use case are enabled.

For example, specify the host name and port of the Configuration Distribution Peer (CDP), where you have activated the BMC-SA-Event_Orchestration_Service_Down module.

Example: https://hostname:port/baocdp

Yes

-

Username

Specifies the username required to log on to the CDP.

Yes

aoadmin

Password

Specifies the password that matches the CDP.

Yes

-

Specifics > BMC_AR_System configuration items

Contains the connection details and default values that get updated in the incident in BMC Remedy ITSM. 

Configuration item

Description

Update required?

Default values

WebServiceConnectionData

Contains connection data used to invoke SOAP requests to AR Server via the mid-tier

Change_CreateInterface

Specifies the ITSM form name used to create change and tasks in BMC Remedy ITSM.

No

CHG_ChangeServiceInterface

Change_CreateSOAPAction

Specifies the SOAP action URI used to create in Change management management application

No

urn:CHG_ChangeServiceInterface/
Change_ProcessInterfaceData

Change_GetSOAPAction

Specifies the ITSM form name used to retrieve change and task tickets information from Remedy ITSM

No

CHG_ChangeOutboundInterface

Incident_CreateInterface

Specifies the ITSM form name used to create incident tickets in Remedy ITSM

No

HPD_IncidentServiceInterface

Incident_UpdateInterface

Specifies the ITSM form name used to update incidents in Remedy ITSM

No

HPD_IncidentServiceInterface

URL

Specifies the BMC AR System or BMC Helix mid-tier URL.

Yes

-

New in 20.19.02RestURL

Specifies the URL used to access the REST API endpoint for BMC Helix Remedy ITSM.

Yes

-

Username

Specifies the username required to log on to the URL.

Yes

Orchestrator

Password

Specifies the password that matches the username, in a secure format.

Yes


Change Management Defaults

Contains default values used while interacting with BMC Remedy ITSM Change Management application

ReportedSource

Specifies the value that appears in the Reported source field for a change request in BMC Remedy ITSM.

No

EventOrchestration

IncidentManagementDefaults

Contains default values used in the incidents created in BMC Remedy Incident Management

AssignedGroup

Specifies the default value for the Assigned Group field when an incident is created.

Yes

Service Desk

AssignedSupportCompany

Specifies the default value for the Contact Company field when an incident is created.

Yes

Calbro Services

AssignedSupportOrganization

Specifies the default value for the Support Organization field when an incident is created.

Yes

IT Support

Assignee

Specifies the default value for the Contact Company field when an incident is created.

Yes

Allen Allbrook

DefaultImpact

Specifies the impact to be assigned when an incident is created.

No

3-Moderate/Limited

DefaultIncidentStatus

Specifies the status to be assigned when an incident is created.

No

Assigned

DefaultServiceType

Specifies the service type to be assigned when an incident is created.

No

Infrastructure Event

DefaultUrgency

Specifies the urgency to be assigned when an incident is created.

No

3-Medium

EventIncidentAssociationMaxPollCount

Specifies the default value for the Event Incident Association Max Poll Count field

No

3

EventIncidentAssociationPollIntervalSecs

Specifies the default value for the Event Incident Association Poll Interval Secs field

No

30

EventSourceIntegrationEnabled

Specifies the default value for the Event Source Integration Enabled field

No

true

IncidentType

Specifies the type of incident to be created in BMC Remedy ITSM for an event.

No

Infrastructure Event

ReportedSource

Specifies the reported source of the event when an incident is created.

No

Event Orchestration

StatusReason

Specifies the status reason to be assigned when an incident is created.

No

Infrastructure Change

WorkInfoLocked

Specifies the default value to be added to the workInfo source to be assigned when an incident is created.

No

No

WorkInfoSource

Specifies the default value for the WorkInfoSource to be assigned when an incident is created.

No

BMC TrueSight Event

WorkInfoType

Specifies the default value for the WorkInfoType to be assigned when an incident is created.

No

General Information

WorkInfoViewAccess

Specifies the default value to be added to the WorkInfoViewAccess field of the incidents WorkInfo record when a WorkInfo is created.

No

Public

Mappings

Contains enumerations defined in BMC Remedy ITSM server.

If your environment requires any changes, you may update the values.

ChangeClassMappings

ChangeClassMappings
<mappings>
 <mapping name="Emergency" type="string">1000</mapping>
 <mapping name="Expedited" type="string">2000</mapping>
 <mapping name="Latent" type="string">3000</mapping>
 <mapping name="Normal" type="string">4000</mapping>
 <mapping name="No Impact" type="string">5000</mapping>
 <mapping name="Standard" type="string">6000</mapping>
</mappings>

No


ChangeTimings

ChangeTimings
<change-timings>
 <pre-approved>Emergency</pre-approved>
 <normal>Normal</normal>
</change-timings>

No


ImpactMappings

ImpactMappings
<mappings />

No


StatusMappings

StatusMappings
<status-mappings>
 <mapping name="New" type="string">0</mapping>
 <mapping name="Assigned" type="string">1</mapping>
 <mapping name="In Progress" type="string">2</mapping>
 <mapping name="Pending" type="string">3</mapping>
 <mapping name="Resolved" type="string">4</mapping>
 <mapping name="Closed" type="string">5</mapping>
 <mapping name="Cancelled" type="string">6</mapping>
</status-mappings>

No


StatusReasonMappings

StatusReasonMappings
<status-reason-mappings>
 <mapping name="Infrastructure Change Created" type="string">1000</mapping>
 <mapping name="Local Site Action Required" type="string">2000</mapping>
 <mapping name="Purchase Order Approval" type="string">3000</mapping>
 <mapping name="Registration Approval" type="string">4000</mapping>
 <mapping name="Supplier Delivery" type="string">5000</mapping>
 <mapping name="Support Contact Hold" type="string">6000</mapping>
 <mapping name="Third Party Vendor Action Reqd" type="string">7000</mapping>
 <mapping name="Client Action Required" type="string">8000</mapping>
 <mapping name="Infrastructure Change" type="string">9000</mapping>
 <mapping name="Request" type="string">10000</mapping>
 <mapping name="Future Enhancement" type="string">11000</mapping>
 <mapping name="Pending Original Incident" type="string">12000</mapping>
 <mapping name="Client Hold" type="string">13000</mapping>
 <mapping name="Monitoring Incident" type="string">14000</mapping>
 <mapping name="Customer Follow-Up Required" type="string">15000</mapping>
 <mapping name="Temporary Corrective Action" type="string">16000</mapping>
 <mapping name="No Further Action Required" type="string">17000</mapping>
 <mapping name="Resolved by Original Incident" type="string">18000</mapping>
 <mapping name="Automated Resolution Reported" type="string">19000</mapping>
 <mapping name="No longer a Causal CI" type="string">20000</mapping>
 <mapping name="Pending Causal Incident Resolution" type="string">21000</mapping>
 <mapping name="Resolved by Causal Incident" type="string">22000</mapping>
</status-reason-mappings>

No


UrgencyMappings

Urgency mappings
<mappings>
 <mapping key="Critical">1-Critical</mapping>
 <mapping key="High">2-High</mapping>
 <mapping key="Medium">3-Medium</mapping>
 <mapping key="Low">4-Low</mapping>
</mappings>

No


WorkInfoSecureLogMappings

WorkInfoSecureLogMappings
<workinfo-securelog-mappings>
 <mapping name="Yes" type="string">0</mapping>
 <mapping name="No" type="string">1</mapping>
</workinfo-securelog-mappings>

No


WorkInfoTypeMappings

WorkInfoTypeMappings
<workinfo-type-mappings>
 <mapping name="Customer Communication" type="string" version="default">2000</mapping>
 <mapping name="Customer Follow-up" type="string" version="default">3000</mapping>
 <mapping name="Customer Status Update" type="string" version="default">4000</mapping>
 <mapping name="Closure Follow Up" type="string" version="default">6000</mapping>
 <mapping name="Detail Clarification" type="string" version="default">7000</mapping>
 <mapping name="General Information" type="string" version="default">8000</mapping>
 <mapping name="Resolution Communications" type="string" version="default">9000</mapping>
 <mapping name="Satisfaction Survey" type="string" version="default">10000</mapping>
 <mapping name="Status Update" type="string" version="default">11000</mapping>
 <mapping name="Incident Task / Action" type="string" version="default">13000</mapping>
 <mapping name="Problem Script" type="string" version="default">14000</mapping>
 <mapping name="Working Log" type="string" version="default">15000</mapping>
 <mapping name="Email System" type="string" version="default">16000</mapping>
 <mapping name="Paging System" type="string" version="default">17000</mapping>
 <mapping name="BMC Impact Manager Update" type="string" version="default">18000</mapping>
 <mapping name="Chat" type="string" version="default">35000</mapping>
 <mapping name="Vendor Communication" type="string">37000</mapping>
</workinfo-type-mappings>

No


WorkInfoViewAccessMappings

WorkInfoViewAccessMappings
<workinfo-viewaccess-mappings>
 <mapping name="Internal" type="string">0</mapping>
 <mapping name="Public" type="string">1</mapping>
</workinfo-viewaccess-mappings>

No


BMC_AR_System

ITSMLocaleLanguage

Specifies the Locale Language of the Event Source Type

No

default

ITSMLocaleCountry

Specifies the Locale Country of the Event Source Type.

No

default

ITSMTimeZone

Specifies the timezone (standard Java time zones) where ITSM application is running.

This field is used to determine the EPOCH time. EPOCH time is used queries to retrieve approved tasks by scheduled dates.

For example, Asia/Kolkata or Europe/Paris.

No

Asia/Kolkata

Specifics > BMC_TrueSight configuration items

Contains the connection details and mappings for TrueSight Presentation Server. 

Configuration item

Description

Update required?

Default values

EventSourceDefaults> IncidentIntegrationEnabled

Specifies whether BMC Service Resolution is implemented at the event source.

Valid values: true (default), false

If true, it is assumed that BMC Service Resolution integration is enabled at the event source, and TrueSight Infrastructure Management is creating incidents for events and TrueSight Orchestration does not create or update incidents.

If false, BMC Service Resolution is not integrated.

Custom; specify false if not using BMC Service Resolution to create incidents

true

EventTypes > HostDown

Contains configuration information related to all supported event types

HostDown > Configurations

Contains the configuration for the Host Down use case.

An event type can support more than one configuration based on the type of actions.

Each configuration has the following parameters:

  • <id>: Unique number for each configuration within a given event type. The ID value is concatenated with event source type (for example: BMC_TrueSight) and event type to form a unique action ID string. For example: BMC_TrueSight-HostDown-1
  • <action-name>: Specifies the action name. The action name is shown in the Launch Orchestration Actions menu in the TrueSight console.
    Default value: Check Host Connection
  • <incident-enabled>: Specifies whether to create an incident for the specified event type. By default, false.

    Note

    If true, the runbook verifies whether an incident is created for an event (by using BMC Service Resolution) and if not created, TrueSight Orchestration creates an incident for the event in BMC Remedy Incident Management system.

  • <change-enabled>: Specifies whether to create a change for the specified event type. By default, false.
  • <remediation-enabled>: Specifies whether to execute remediation action for this event type. By default, false.
  • <change-type/>: Change type determines if approval is required for task to be performed. Valid values: normal, emergency.

Custom; required if customizing for your requirements

Host Down configurations
<configurations>
 <configuration>
   <id>1</id>
   <action-name>Check Host Connection</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>false</remediation-enabled>
   <change-type />
 </configuration>
</configurations>

HostDown > ModuleName

Specifies the module name that contains the workflow processes for the Host Down event.

No

 :BMC-SA-Event_Orchestration_Host_Down

EventTypes > ServiceDownViaTSSA

Contains configuration information required if you want to restart services using TrueSight Server Automation.

Applicable only for 20-19-02-003-Patch-3-for-version-20-19-02 and later.

ServiceDownViaTSSA >Configurations

Contains the configurations for all the services supported with TrueSight Server Automation.

New in 20.19.02.003Each configuration has the following parameters:

  • <id>: Unique number for each configuration within a given event type. The ID value is concatenated with event source type (for example: BMC_TrueSight) and event type to form a unique action ID string. For example: Start service Via TSSA.
  • <action-name>: Specifies the action name. The action name is shown in the Launch Orchestration Actions menu in the TrueSight console.
  • <incident-enabled>: Specifies whether to create an incident for the specified event type. By default, false.
  • <change-enabled>: Specifies whether to create a change for the specified event type. By default, false.
  • <remediation-enabled>: Specifies whether to execute remediation for this action. By default, false.
  • <change-type/>: Change type determines if approval is required for task to be performed. Valid values: normal, emergency.

Conditional; required if using TrueSight Server Automation to restart services.

ServiceDownViaTSSA configuration
<configurations>
 <configuration>
   <id>1</id>
   <action-name>Start service Via TSSA</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>2</id>
   <action-name>Start SNMP service Via TSSA</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>3</id>
   <action-name>Start Print Spooler Via TSSA</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>4</id>
   <action-name>Start Apache Web Server Via TSSA</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>5</id>
   <action-name>Start Microsoft Skype service Via TSSA</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
</configurations>

ServiceDownViaTSSA >ModuleName

Specifies the module name that contains the workflow processes for the Service Down event to be remediated using TrueSight Server Automation.

Conditional; required if using TrueSight Server Automation to restart services.

:BMC-SA-Event_Orchestration_Service_Down_Via_TSSA

EventTypes > ServiceDown

Contains configuration information related to all supported event types

ServiceDown > Configurations

Contains the configurations for the out-of-the-box service down use case.

New in 20.19.02The following services are included:

  • RSCD agent
  • SNMP service
  • Print Spooler
  • Apache Web Server
  • TrueSight Server Automation service
  • Microsoft Skype service

Each configuration has the following parameters:

  • <id>: Unique number for each configuration within a given event type. The ID value is concatenated with event source type (for example: BMC_TrueSight) and event type to form a unique action ID string. For example: BMC_TrueSight-ServiceDown-1
  • <action-name>: Specifies the action name. The action name is shown in the Launch Orchestration Actions menu in the TrueSight console.
    Default value: Start Service
  • <incident-enabled>: Specifies whether to create an incident for the specified event type. By default, false.

    Note

    If true, the runbook verifies whether an incident is created for an event (by using BMC Service Resolution) and if not created, TrueSight Orchestration creates an incident for the event in BMC Remedy Incident Management system.

  • <change-enabled>: Specifies whether to create a change for the specified event type. By default, false.
  • <remediation-enabled>: Specifies whether to execute remediation for this action. By default, false.

    Note

    If true, the BMC-SA-Event_Orchestration_Service_Down module must contain the Perform Triage, Perform Remediation, and Perform Validation workflows.

  • <change-type/>: Change type determines if approval is required for task to be performed. Valid values: normal, emergency.

Custom; required if customizing for your requirements

ServiceDown configurations
<configurations>
 <configuration>
   <id>1</id>
   <action-name>Start service</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>2</id>
   <action-name>Start RSCD agent</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>3</id>
   <action-name>Start SNMP service</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>4</id>
   <action-name>Start Print Spooler</action-name>
   <incident-enabled>true</incident-enabled>
   <change-enabled>true</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>5</id>
   <action-name>Start Apache Web Server</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>6</id>
   <action-name>Start TrueSight Server Automation service</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>true</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
 <configuration>
   <id>7</id>
   <action-name>Start Microsoft Skype service</action-name>
   <incident-enabled>false</incident-enabled>
   <change-enabled>false</change-enabled>
   <change-template-name />
   <remediation-enabled>true</remediation-enabled>
   <change-type>normal</change-type>
 </configuration>
</configurations>

ServiceDown > ModuleName

Specifies the module name that contains the workflow processes for the Service Down event.

Custom; required if customizing for your requirements

:BMC-SA-Event_Orchestration_Service_Down

Mappings

Used to convert input event data into common event model

EventMappings

Contains the mappings used to convert the event data into a common event model.

EventMappings
<mappings>
 <!-- metadata -->
 <mapping>
   <source>mc-event-model-version</source>
   <destination class="metaData">eventModelVersion</destination>
 </mapping>
 <mapping>
   <source>class-name</source>
   <destination class="metaData">eventClass</destination>
 </mapping>
 <mapping>
   <source>mc-ueid</source>
   <destination class="metaData">eventId</destination>
 </mapping>
 <mapping>
   <source>status</source>
   <destination class="metaData">status</destination>
 </mapping>
 <mapping>
   <source>mc-incident-report-time</source>
   <destination class="metaData">reportTime</destination>
 </mapping>
 <mapping>
   <source>mc-smc-impact</source>
   <destination class="metaData">eventToCIAssociationType</destination>
 </mapping>
 <mapping>
   <source>mc-timeout</source>
   <destination class="metaData">timeout</destination>
 </mapping>
 <mapping>
   <source>mc-notes</source>
   <destination class="metaData">notes</destination>
 </mapping>
 <mapping>
   <source>mc-history</source>
   <destination class="metaData">propagationHistory</destination>
 </mapping>
 <mapping>
   <source>mc-relation-source</source>
   <destination class="metaData">relationSource</destination>
 </mapping>
 <mapping>
   <source>mc-owner</source>
   <destination class="metaData">owner</destination>
 </mapping>
 <mapping>
   <source>mc-account</source>
   <destination class="metaData">account</destination>
 </mapping>
 <!-- source / reporter data -->
 <mapping>
   <source>mc-tool-id</source>
   <destination class="sourceData">resourceId</destination>
   <destination class="reporterData">resourceId</destination>
 </mapping>
 <mapping>
   <source>mc-smc-id</source>
   <destination class="sourceData">reconciliationId</destination>
 </mapping>
 <mapping>
   <source>mc-smc-alias</source>
   <destination class="sourceData">alias</destination>
 </mapping>
 <mapping>
   <source>mc-host</source>
   <destination class="sourceData">componentHost</destination>
 </mapping>
 <mapping>
   <source>mc-host-address</source>
   <destination class="sourceData">componentHostAddress</destination>
 </mapping>
 <mapping>
   <source>mc-location</source>
   <destination class="sourceData">location</destination>
 </mapping>
 <mapping>
   <source>mc-object-uri</source>
   <destination class="sourceData">componentURI</destination>
 </mapping>
 <mapping>
   <source>mc-object</source>
   <destination class="sourceData">componentCaption</destination>
 </mapping>
 <mapping>
   <source>mc-object-class</source>
   <destination class="sourceData">componentType</destination>
 </mapping>
 <mapping>
   <source>mc-object-owner</source>
   <destination class="sourceData">componentOwner</destination>
 </mapping>
 <!-- reporter data -->
 <mapping>
   <source>mc-tool-address</source>
   <destination class="reporterData">componentHostAddress</destination>
 </mapping>
 <mapping>
   <source>mc-tool-uri</source>
   <destination class="reporterData">componentURI</destination>
 </mapping>
 <mapping>
   <source>mc-tool</source>
   <destination class="reporterData">componentCaption</destination>
 </mapping>
 <mapping>
   <source>mc-tool-class</source>
   <destination class="reporterData">componentType</destination>
 </mapping>
 <mapping>
   <source>mc-tool-time</source>
   <destination class="reporterData">eventTime</destination>
 </mapping>
 <mapping>
   <source>mc-tool-rule</source>
   <destination class="reporterData">eventType</destination>
 </mapping>
 <mapping>
   <source>mc-tool-source</source>
   <destination class="reporterData">reporterEventId</destination>
 </mapping>
 <mapping>
   <source>mc-tool-sev</source>
   <destination class="reporterData">eventSeverity</destination>
 </mapping>
 <mapping>
   <source>mc-tool-suggestion</source>
   <destination class="reporterData">eventSuggestion</destination>
 </mapping>
 <!-- situation data -->
 <mapping>
   <source>mc-event-category</source>
   <destination class="situationData">situationCategory</destination>
 </mapping>
 <mapping>
   <source>mc-event-subcategory</source>
   <destination class="situationData">situationSubCategory</destination>
 </mapping>
 <mapping>
   <source>mc-incident-time</source>
   <destination class="situationData">situationTime</destination>
 </mapping>
 <mapping>
   <source>mc-priority</source>
   <destination class="situationData">priority</destination>
 </mapping>
 <mapping>
   <source>severity</source>
   <destination class="situationData">severity</destination>
 </mapping>
 <mapping>
   <source>msg</source>
   <destination class="situationData">messageSummary</destination>
 </mapping>
 <mapping>
   <source>mc-service</source>
   <destination class="situationData">service</destination>
 </mapping>
 <mapping>
   <source>mc-long-msg</source>
   <destination class="situationData">messageDetail</destination>
 </mapping>
 <mapping>
   <source>repeat-count</source>
   <destination class="situationData">repeatCount</destination>
 </mapping>
 <!-- metrics data -->
 <mapping>
   <source>mc-parameter</source>
   <destination class="metricsData">metricName</destination>
 </mapping>
 <mapping>
   <source>mc-parameter-value</source>
   <destination class="metricsData">metricValue</destination>
 </mapping>
 <mapping>
   <source>mc-parameter-unit</source>
   <destination class="metricsData">metricValueUnit</destination>
 </mapping>
 <mapping>
   <source>mc-parameter-threshold</source>
   <destination class="metricsData">metricThreshold</destination>
 </mapping>
 <!--  extended data is a generic place holder for all unidentified/custom fields -->
 <mapping>
   <source>extendedData</source>
   <destination class="extendedData">nameValueList</destination>
 </mapping>
</mappings>

No


WebServiceConnectionData

Contains the connections details to connect to TrueSight Presentation Server

BASE_URL

Specifies the URL to the TrueSight Presentation Server or a load balancer server, if used.

Yes

EVENT_URI

This will be appended to BASE_URL to create a related event in the TrueSight Presentation Server.

Do not update the values in this field.

No

/CI/-1/event

LOGIN_URI

This will be appended to BASE_URL to invoke login request with the TrueSight Presentation Server.

Do not update the values in this field.

No

/authenticate/login

Tenant

Specifies the realm in Remedy SSO used by the TrueSight Presentation Server.

Yes

*

Username

Specifies the username in the TrueSight Presentation Server with super admin privileges and application administration roles.

Yes


Password

Specifies the password, in an encrypted format, to log on to TrueSight Presentation Server.

Yes

-

Specifics > Defaults configuration items

Configuration item

Description

Update required?

Default values

BypassEventNotes

Used to bypass updating event source update.

No

false

NotfoundWorkflowName

Specifies the default value returned by the logic when required workflow is not found

No

NOT_FOUND

RunSchedules

Used to turn of polling for task tickets. Used for debug purposes only.

No

true

SupportedActionsDelimiter

Used to form action ID string used by TrueSight Presentation Server

No

-

RESTRequestTimeout

Default timeout, in seconds, for REST adapter connection timeout and socket connection timeout.

Custom; update if the request takes longer to complete

900

New in 20.19.02CloseIncident

If you specify None, incident status is not updated after the remediation is successful.

If you specify Close, incident status is set to Closed after the remediation is successful. If you specify Resolve, incident status is set to Resolved.

No

Resolve

New in 20.19.02ComponentType

Sets the operating system type if the event data does not provide the information about the target operating system.

No

unix

New in 20.19.02UseRemedyJavaAPI

By default, the value is false. Uses the REST API exposed by the Jetty server.

Specify true if you want to use the BMC Remedy Java API, using BMC Remedy AR System adapter.

No

false

Specifics > Workflow Definitions configuration items

Configuration item

Description

Update required?

Default values

CommonWorkflows

Contains the names of the workflows invoked when using the REST API requests

No

<workflows>
 <workflow action="PerformRemediationOnTaskApproval">:BMC-SA-Event_Orchestration:Remediate:Perform Remediation on Task Approval</workflow>
</workflows>

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*