Previous Topic: How to Migrate a Failover Deployment

Next Topic: Set up Failover at the Proxy Server or Load Balancer

Migrating an r12 Failover Deployment to r12.1 SP3

You can migrate an existing r12x failover deployment to an r12.1 SP3 Federation Manager deployment.

To migrate a failover configuration

  1. Install Federation Manager 12.1 onto each machine in your deployment.
  2. Run the Federation Manager Configuration wizard on the first r12.1 machine and enter the same information that was used when you ran the r12x Configuration wizard.

    To determine the Federation Manager r12x configuration settings, go to the following file on the r12x system: federation_mgr_home\install_config_info\ca-Federation-Config.properties.

  3. Run the Federation Manager Configuration wizard on the second machine. Enter the following information:
    1. Database information from the first machine.
    2. All other entries from the ca-Federation-Config.properties file.
  4. Log in to the Federation Manager UI.
  5. From the Infrastructure tab, select System Settings.

    The Configure System Settings dialog displays.

  6. Change the Global Base URL to include the host and port of the Proxy Server or load balancer in your federated network. Setting this URL properly ensures that the default URL for all metadata used to create partnerships is correct.

    To modify the server.conf file

    1. Navigate to federation_mgr_home/secure-proxy/proxy-engine/conf.
    2. Open the server.conf file in an editor.
    3. Go to the # Default Virtual Host section.
    4. Add the base URL to the hostnames setting using fully qualified host names, as follows:

      <VirtualHost name="default">

      hostnames="defaultbaseurl.ca.com:80, newbaseurl.ca.com:80"

      </VirtualHost>

      Note: Specify multiple host_name:port entries for the hostnames setting, separating each entry with a comma.

  7. If you have enabled SSL for failover on an r12x system, you have to migrate the SSL configuration to the r12.1 SP3 primary and secondary system, as instructed in the SSL migration steps.

Both Federation Manager systems are now pointing to the same database server and can be configured for failover from a proxy server or load balancer.