Configuring the BMC Remedy AR System monitor adapter
You configure an adapter in Grid Manager. The configuration provides information about how the adapter interacts with the BMC Remedy Action Request System application (BMC Remedy AR System). While each adapter must have a unique name, you can create multiple adapters with the same adapter type to allow for different configuration properties.
The form view provides an easy-to-use interface for configuring adapters. The form view prevents human errors that might occur as a result of copying the configuration XML from the XML sample into the UI when configuring an adapter. You can switch to the XML view to configure those elements and attributes that are not available as fields on the form view or to configure all the elements and attributes using XML only. However, after you switch to the XML view and save the configuration in the XML from that view, you cannot thereafter use the form view for modifying that configuration.
To configure the monitor adapter
- Log on to the TrueSight Orchestration Grid Manager.
- Access the adapters page by clicking the Manage tab; then click the Adapters tab.
- In the Adapters in Repository list, select the ro-adapter-remedy-monitor check box to configure an monitor adapter.
- Click Add to Grid to include the adapter in the Adapters on Grid list.
- Click Configure corresponding to the newly added adapter.
- On the Add an Adapter Configuration page, perform the following substeps to configure the adapter using the form view or jump to step 7 to configure the adapter using the XML view:
- Enter a name for the adapter.
- Enter a description for the adapter.
- Under Properties, enter or select values for the configuration elements.
Include all required elements indicated with an asterisk (*).
- (Optional) Configure the adapter in the XML view using the following substeps:
- Enter a name and a description for the adapter.
- Click Switch to XML View to specify elements and attributes that are not in the form view, starting with step.
- On the Warning message that appears, click Switch View.
Copy the configuration elements and attributes into the Properties text box, and then click OK.
- On the Warning message that appears, click Save.
This action saves the adapter configuration with settings in the XML view permanently. The newly configured adapter is now listed in the Adapters on Grid list.
To configure the load balancer with the BMC Remedy AR system monitor adapter
If your Remedy AR System server group contains a load balancer, you must configure the load balancer with the monitor adapter. You use a hardware load balancer to improve the scalability and availability of BMC Remedy AR System servers. The load balancer distributes the traffic from multiple clients to several servers, preventing BMC Remedy AR System servers from becoming overloaded. A load balancer provides solutions to issues relating to performance, hardware capacity, system downtime, and so on in high-load environments.
To configure the load balancer, you have to add a mapping for the IP addresses of the load balancer and other servers in the BMC Remedy AR System servers' group in the ar.cfg file of each server in the group.
For example, consider AR Server 1 and AR Server 2 in the BMC Remedy AR System servers' group. The IP address of AR Server 1 is IP1, AR Server 2 is IP2, and the load balancer is L-IP. These IP addresses are mapped as follows to the local BMC Remedy AR System server's IP address:
For AR Server 1, add the following entries to the corresponding ar.cfg file:
Map-IP-Address: L-IP IP1
{{code language="none" source="string:{{code language=~"none~"~}~}
Map-IP-Address: IP2 IP1
{{/code~}~}"/}}{{/code}}
(% class="code" %)
(((
Alert-Ignore-Actual-Client-IP: T
Alert-Send-Timeout: 30
)))
{{code language="none" source="string:{{code language=~"none~"~}~}
{{/code~}~}"/}}
)))
* (((
For AR Server 2, add the following entries to the corresponding **ar.cfg** file:
{{code language="none"}}Map-IP-Address: L-IP IP2{{/code}}
{{code language="none"}}Map-IP-Address: IP1 IP2
{{/code}}
(% class="code" %)
(((
Alert-Ignore-Actual-Client-IP: T
Alert-Send-Timeout: 30
)))
{{code language="none"}} {{/code}}
{{confluence_note title="Note"}}
Even if there is no load balancer, the IP address mappings are required for the BMC Remedy AR System servers' group.
{{/confluence_note}}
To configure the load balancer with the monitor adapter, see the {{code language="none"}}<target>{{/code}} element description in [[Configuration node elements for monitor adapter>>doc:Automation-DevSecOps.Orchestrator.TrueSight-Orchestration-Content.tsoc2102.Application-adapters.BMC-Remedy-AR-System-adapter.Configuring-the-BMC-Remedy-AR-System-actor-adapter.WebHome||anchor="ConfiguringtheBMCRemedyARSystemactoradapter-49976"]].
\\The following table shows the configuration node elements for BMC AR Remedy monitor adapter that you can specify using the form view, XML view, or both. You cannot use the form view to configure elements and attributes that do not have an entry in the UI label column. To configure such elements and attributes, you have to switch to XML view.
{{confluence_table-plus enableSorting="false" atlassian-macro-output-type="BLOCK"}}{{id name="ConfiguringtheBMCRemedyARSystemmonitoradapter-49976"/}}
**Configuration node elements for the monitor adapter**
|=(((
**UI label**
)))|=(((
**Element**
)))|=(((
**Description**
)))|=(((
**Required**
)))
|(((
None
)))|(((
{{code language="none"}}
<config>
{{/code}}
)))|(((
Contains the configuration elements to connect to a specific server, along with login credentials
)))|(((
Yes
)))
|(((
**Target**
)))|(((
{{code language="none"}}
<target>
{{/code}}
)))|(((
Specifies the host name or IP address of the BMC Remedy AR system server
{{confluence_note title="Note"}}
If the Remedy AR Server group uses a load balancer, you must set the {{code language="none"}}<target>{{/code}} element of the monitor adapter to the IP address of the load balancer.
{{/confluence_note}}
)))|(((
Yes
)))
|(((
**Schemas**
)))|(((
{{code language="none"}}
<schemas>
{{/code}}
)))|(((
Contains the {{code language="none"}}<schema>{{/code}} elements
)))|(((
No
)))
|(((
**Schema**
)))|(((
{{code language="none"}}
<schema>
{{/code}}
)))|(((
Specifies the BMC Remedy AR System schema to be cached upon adapter attachment to a peer, restart of a peer, or immediately following a reset-cache action
\\In the absence of this element, the schema will be cached the first time it is called by an adapter request.
)))|(((
No
)))
|(((
**Port**
)))|(((
{{code language="none"}}
<port>
{{/code}}
)))|(((
Specifies the remote connection port number
\\In the absence of this element, a default value of '0' will be assigned. This default will cause the BMC Remedy AR System to use its default TCP/IP port number.
)))|(((
No
)))
|(((
**User Name**
)))|(((
{{code language="none"}}
<user-name>
{{/code}}
)))|(((
Specifies the user name to connect to the BMC Remedy AR System server
)))|(((
Yes
)))
|(((
**Password**
)))|(((
{{code language="none"}}
<password>
{{/code}}
)))|(((
Specifies the password that corresponds to the specified {{code language="none"}}<user-name>{{/code}}
)))|(((
No
)))
|(((
**Rpc Number**
)))|(((
{{code language="none"}}
<rpc-number>
{{/code}}
)))|(((
Specifies the RPC port number
\\In the absence of this element, a default value of '0' will be assigned. The default will cause the BMC Remedy AR System to use its default RPC port number.
)))|(((
No
)))
|(((
**Poll Interval**
)))|(((
{{code language="none"}}
<poll-interval>
{{/code}}
)))|(((
Specifies the frequency, in seconds, to re-register with the BMC Remedy AR System host
\\This will re-establish any dropped connections with the BMC Remedy AR System host. In the absence of a specified poll-interval, a default value of '900' will be assigned. This default will prompt for re-registration with the BMC Remedy AR System host every 15 minutes.
)))|(((
No
)))
|(((
**Alert Listener Port**
)))|(((
{{code language="none"}}
<alert-listener-port>
{{/code}}
)))|(((
Specifies the port on which the adapter will listen for BMC Remedy AR System notifications
\\In the absence of this element, a default value of 0 will be assigned. The default will cause the protocol to provide the first available port on which to listen.
)))|(((
)))
|(((
**Delete Alerts**
)))|(((
{{code language="none"}}
<delete-alerts>
{{/code}}
)))|(((
Deletes alerts from schema after being marked as read
\\Valid values: true, false
{{confluence_note title="Note"}}
If this element is set to {{code language="none"}}true{{/code}} and the {{code language="none"}}<username>{{/code}} provided is for a user with insufficient privileges to delete a record, the alert will remain in the schema, marked as read, and a warning level message will be logged. In the absence of this element, a default value of false will be assigned.
{{/confluence_note}}
)))|(((
No
)))
|(((
**Maximum Registration Retries**
)))|(((
{{code language="none"}}
<maximum-registration-retries>
{{/code}}
)))|(((
Specifies the number of retries the adapter makes to connect to the Remedy AR System application
\\The registration retry frequency is determined by the {{code language="none"}}<polling-interval>{{/code}} element. If the registration fails due to authentication errors, there are no retries.
\\Default value: 3
)))|(((
No
)))
|(((
**Maximum Alerts Per Second**
)))|(((
{{code language="none"}}
<maximum-alerts-per-second>
{{/code}}
)))|(((
Specifies the count of unread alerts to be processed per second
\\It limits the rate at which the monitor adapter retrieves unread alerts from the BMC Remedy AR System server. If the monitor adapter goes down for a long period and this element is enabled, no Out-of-Memory errors occur.
)))|(((
No
)))
|(((
**Query**
)))|(((
{{code language="none"}}
<query>
{{/code}}
)))|(((
Used to provide additional querying capability to add more filtering criteria to the default query
)))|(((
No
))){{/confluence_table-plus}}
)))
The following figure shows the XML template for monitor adapter configuration.
\\{{id name="ConfiguringtheBMCRemedyARSystemmonitoradapter-83528"/}}**XML template for monitor adapter configuration**
{{code}}
<config>
<target></target>
<schemas>
<schema></schema>
<schema></schema>
</schemas>
<port></port>
<user-name></user-name>
<password></password>
<rpc-number></rpc-number>
<poll-interval></poll-interval>
<alert-listener-port></alert-listener-port>
<delete-alerts></delete-alerts>
</config>
{{/code}}
{{excerpt-include 0="confluencePage:page:tsop81.Configuring adapters" name="CustomLogging" nopanel="true"/}}
{{excerpt-include 0="confluencePage:page:tsop81.Configuring adapters" name="EncrpytElementContent" nopanel="true"/}}