How to configure the Enterprise Manager Failback mechanism in the Loadbalancing.xml?
search cancel

How to configure the Enterprise Manager Failback mechanism in the Loadbalancing.xml?

book

Article ID: 35827

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE

Issue/Introduction

Question:

How to configure the Enterprise Manager Failback mechanism in the Loadbalancing.xml?

For example, MQAgent is allowed to connect to 2 collectors in the loadbalancing.xml as below:

<agent-collector name="prod">
<agent-specifier>.*\|MQ.*\|.*</agent-specifier>
<include>
<collector host="coll-1" port="5001" />
<collector host="coll-2" port="5001" />
</include>
</agent-collector>

Requirements:

a) I need to configure coll-1 as a primary or preferred collector.
b) If coll-1 goes down agent should connect to coll-2.
c) As soon as coll-1 is back online, the MQ agent should reconnect to it.

 

Answer:

1. Open the EM properties file, set introscope.apm.agentcontrol.agent.emlistlookup.enable=true

2. Update the MOM_HOME\config\loadbalancing.xml as below

<agent-collector name="prod">
<agent-specifier>.*\|MQ.*\|.*</agent-specifier>
<include>
<collector host="coll-1" port="5001" latched="true" />
<collector host="coll-2" port="5001" />
</include>
</agent-collector>

3. Verfiy the results.

NOTE In the above example, MQAgent will reconnect to the primary collector during the next load rebalancing which occurs by default every 10 min (introscope.enterprisemanager.loadbalancing.interval=600)

Environment

Release: CEMUGD00200-9.7-Introscope to CA Application-Performance Management-Upgrade Main
Component: