How to connect an existing Web Tier to a newly promoted Primary
2 years ago
Originally Published: 2022-09-01
Article Number
000067950
Applies To
Authentication Manager 8.x, 8.5, 8.6, 8.7 
Web Tier
Issue
Any Replica that has a Web Tier configured to be associated to it (RBA preference) will retain that Web Tier if it is promoted, just restart Web Tier Services per documentation.  But if you need the existing Web Tier to transfer its association to a new primary, because you do not want to deploy another Web Tier or change Load Balancer configure, you need to follow this KB.
In this example
Original primary: Old_primary.com.local
Web Tier Name: WT-1
Web Tier Hostname: WebTier1.com.local.
New primary: New_primary2.com.local had no Web Tiers when it was a replica.
 
Tasks
1. Deploy a replica without any Web Tier Associated to it.
2. Promote this replica to primary
3. Edit existing Web Tier and set its preferred RBA instance to the new Primary
OC-Deploy-WebTier_Preferred_RBA.png
 
Resolution
Legend
Original primary: Old_primary.com.local
Web Tier Name: WT-1
Web Tier Hostname: WebTier1.com.local.
New primary: New_primary2.com.local had a Web Tier 'WT-1' tagged to 'Old_primary.com.local' when it was a replica..

You need to edit this Web Tier and change its preferred RBA instance to, the newly promoted primary, New_primary2.com.local and restarting the webtier services.

OC-Deploy-WebTier_Primary_Edit.png

The New Primary Operations Console will show the webtier, New_primary2.com.local – however the preferred instance for webtier was yet set to the former primary, Old_primary.com.local

Web_Tier_online_KB
If webtier's preferred RBA Instance on the newly promoted server 'New_primary2.com.local', is not pointed to 'New_primary2.com.local', before 'Old_primary.com.local' is deleted from the deployment. It deletes the webtier from deployment.

Web_tiers_not_found_KB
 
Don't see what you're looking for?