To enable failover in a federation deployment, a primary and a secondary CA SiteMinder® Federation Standalone system must be installed and configured.
For SSL-enabled failover environments, follow the instructions to enable SSL for a failover environment.
Important! For Solaris platforms, treat Solaris zones as phyical machines. Install and configure separate CA SiteMinder® Federation Standalone instances in each zone. CA SiteMinder® Federation Standalone does not support failover from one zone to another for a single instance because the zones have different Host IDs.
Follow these steps:
Note: The product can run in standalone or proxy mode, but the primary and secondary server must use the same mode.
If CA SiteMinder® Federation Standalone uses more than one virtual host or domain, modify the server.conf file to include all entries.
To modify the server.conf file
<VirtualHost name="default">
hostnames="defaultbaseurl.example.com:80, newbaseurl.example.com:80"
</VirtualHost>
Note: Specify multiple host_name:port entries for the hostnames setting, separating each entry with a comma.
Example:
<VirtualHost name="default"
hostnames=lb5.example.com:80
</VirtualHost>
Both CA SiteMinder® Federation Standalone systems are pointing to the same database. A proxy server or load balancer can be set up to failover from the primary system to the secondary.
|
Copyright © 2013 CA.
All rights reserved.
|
|