Can you check the profiles (when you run autoconfig on the secondary node ; it gets set to secondary node) whether they are pointing to the URL that you wanted.
Can you load balance a VIP in front so the URL for both nodes is the same?
Thanks for taking the time to respond. I am busy recloning and retrying the entire process again, so I will only be able to test your suggestion in a day or two.
I am trying to take it one step at a time, and first getting the system running without a load balancer. Once I have 2 applications tiers working then I plan to add the load balancer.
I assume that it is possible to run a dual applications tier system with both application tiers operating with their own URL? (i.e. a user can connect to either tier, using different URLs and see the same data).
1 person found this helpful
You might be able to... but then you might have some Site Level profile options that don't represent both nodes....some of which might get set when you run your last autoconfig... and that last autoconfig might set values to that node you ran if from...
If you go with a VIP...it will take care of a lot of the headaches...
I suspect that you are right, and the lack of a load balancer is the cause of my current issues.
We are going to put this project on hold for now, but when it resumes I will ensure that I implement the load balancer.
Thanks for the assistance.
Whichever node has the last run of autoconfig .. that node login URL will be redirected .. thats an expected behavior.
As when you run autoconfig all _agent profile gets updated with that node and login page gets set to that node.
I hope this helps you.