Hello Shruti,
I think the final answer really should come from your actual requirements. What you've currently laid out may not make sense at all in terms of your infrastructure and business workload requirements. There are considerations across data centers such as network latency that may make this type of failover to not satisfy your company's business needs. If you can, please enumerate what requirements you are trying to address and I am sure we (myself and the community) can support a deeper discussion.
With that said, I will point out a few things to your current questions.
1. I think the 2nd image is the more accurate one. While some LBed communication will go through the "pipe", There are still some direct instructional communication from the Application Server back to RRs. In image 1, there are no communication links from the App Server directly back to RRs not going through the LB.
2. The answer is no. Again, LBing this way may not serve your real requirements but in the instance of Image 2. If Application Server A goes down and there is something instructional that needs to be send to a RR, Application Server B will still be able to see, and can directly instruct, those RRs in Site A. Obviously the communication will be affected by latency across sites but the communication should be possible.
3. I think you already have some of the right references given the images you've posted. Here are guides that should help:
- Enterprise Infrastructure Guide:
https://portal.blueprism.com/system/files/documents/v6.7%20Data%20Sheet%20-%20Infrastructure%20Overview%20Enterprise%20Edition.pdf- Securing Network Connectivity guide, provides more detail on the communication between components:
https://portal.blueprism.com/system/files/documents/v6.3%20Data%20Sheet%20-%20Securing%20Network%20Connectivity.pdf------------------------------
Wing Ling Leung
Senior Product Consultant
Blue Prism Professional Services
------------------------------