Its not necessary to have two authentication profiles.. If the load on one
config server is more then it will take the other .
So the primary will hit the first and when load is more then the second
comes in picture .
On Sun, Nov 22, 2015, 10:29 AM Rajesh Kumar <firstname.lastname@example.org>
And more over there is no mechanism to route to one config server other
that roles based . it's a random one .
I think even bill has earlier mentioned on this request . #JustSaying
The product on its own does load balancing for the job servers. For configuration servers, it provides an integration with 3rd party load balancers. This way the end users use a single profile which will be configured to the load balancer and connect to different application servers.
I suggest to go through the following links
"Its not necessary to have two authentication profiles.. If the load on one config server is more then it will take the other ."
-> that's not true at all. you need a load balancer like a F5, Windows NLB, etc between the gui and appserver to balance the connections.