SM Need to specify preferredFQHN if there are multiple FQDNs

If you are using SSO at 9.34.3003 with the following pattern:
ServiceManager Server <——> Tomcat(WebTier) <—> IIS <—> Web browser(login to SSO)

If you are planning to upgrade the RTE to 9.41.2003.
Upgrade was performed at the same environment,and all the configuration was moved to 9.41 from 9.34 without change.
But they found the configuration which worked at 9.34, now didn’t work at 9.41, and the SSO login failed.

After checking with customer’s environment, we found there are two FQDNs.
Horizontal scaling is also implemented.

We suggest to perform one of the following configuration, then the login worked fine.
1. at sm.ini, specify “preferredFQHN” to one of the FQDNs.
2. at host file, specify one of the FQDNs.

Solution

There hasn’t been any change at SSO from 9.34 to 9.41.
But there was a loadbalancer issue fixed at 9.41 QCCR1E111013.

The scenarios are as follows:
1. With both preferredFQHN and groupbindaddress => Service Manager loadBalancer redirects client requests to the preferredFQHN.
2. With preferredFQHN and without groupbindaddress => Service Manager loadBalancer redirects client requests to the preferredFQHN.
3. With groupbindaddress and without preferredFQHN => Service Manager loadBalancer redirects client requests to the hostname which is matched with groupbindaddress.
4. Both preferredFQHN and groupbindaddress are not existed => Service Manager loadBalancer redirects client requests to the local hostname.

So from 9.41, if there are multiple FQDNs, it is a must to specify preferredFQHN.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s