rep agent in double-star HA architecture connection?

[Anon Anon]

Hi all

 

I am referring to the document https://communities.ca.com/docs/DOC-231165900

(CA Release Automation 5.x / 6.xArchitecture and ImplementationBest Practice Guide),

regarding "Double STAR Execution Server with High Availability Architecture". This is page 18 of the document.

 

The Rep Agent is connected to both NES A and NES B, simultaneously. This is crucial so that whatever is running on the server hosting the Rep Agent is available to every agent connected to the NESes (themsleves connected to NES A and NES B). I have setup this architecture, but even though the conf/nimi_config.xml contains the following snippet,

 

 <supernodes>
  <supernode>ra-ut-nesrouter1.eng.zkb.ch:6601</supernode>
  <supernode>ra-ut-nesrouter2.eng.zkb.ch:6601</supernode>
 </supernodes>

the Rep Agent connects to only a single NES, in this case NES 2.

 

 

How to configure the Rep Agent so that it connects to both NES A and NES B simultaneously, thus matching what is described in the "Double STAR Execution Server with High Availability Architecture" section?

 

Thanks for sheding some light into this.

 

Bernard

[Saurabh Jain]

Hi Bernard,

  Yes your configuration mentioned above are correct. I review the document mentioned above and I think the diagram is actually trying to reflect the execution behavior @ run time. In reference to diagram mentioned in document what it trying to explain is that Agent remains highly available by having configuration of two NES's as supernodes. It means one either one of the NES is not available the agent will topple to other NES and will be available for job execution.

 

Currently an agent never connects to two supernode simultaneously but connects to either one actively. In case of one NES being down it just fail over to another NES to be highly available for job execution.

 

Let me know if it helps to understand.

 

Thanks,

Saurabh

[Anon Anon]

Hi Saurabh

 

thanks for your explanation. Make perfectly sense, but then the diagram is misleading. I should only have a single connection to one of the NES boxes, and perhaps a connection using another colour/filling showing the backup connection to the other NES should the first NES be in trouble. That would reflect the reality.

 

Cheers

 

Bernard

[Saurabh Jain]

Hi Bernard,

 Thanks for update and the valuable input. I agree it will make a lot sense in correcting document may be using different color lines with legend, as suggested.

 

I will pass this information to author of document to correct it.

 

Regards,

Saurabh 

[Keith Puzey]

Hi,

 

     Thanks for the feedback, i will make some changes to the drawings and republish the architecture document.

 

regards

Keith

[Keith Puzey]

Hi,

 

      Do you think is clearer?

 

[Anon Anon]

Hi Keith

yes, much better. Only missing bit is the legend for this new connection.

Cheers

Bernard

[Keith Puzey]

Hi,

 

   I have updated the drawings and republished the guide to the community.

 

Regards

Keith

[Saurabh Jain]

Hi Keith,

 Looks better to me