Federation Manager Installation and Upgrade Guide › Migrate to Federation Manager r12.5 › How to Migrate to r12.5

How to Migrate to r12.5

Your pre-r12.5 deployments can be running on operating platforms or use databases that r12.5 does not support. Therefore, migrate from your pre-r12.5 environment to r12.5.

Migrate a Federation Manager configuration to a new system to replicate the configuration. Copying an existing configuration avoids repeating the entire configuration process on the new system.

Complete the following tasks to migrate to a r12.5 system:

Important! Follow the import steps exactly as outlined. Do not access the Certs & Keys tab in the Federation Manager UI until the copying procedure is complete.

1. Synchronize multiple key databases (for migrating a cluster)
2. Export the existing configuration to an XML file.
3. Return the existing system to its original state.
4. Run the installation program on the new system.
5. Import the existing configuration to the new system.
6. Migrate the key database to the certificate data store.
7. Migrate SSL key and certificate data.

After all the data is migrated, reactivate partnerships.

Note: The XPSExport and XPSImport tools are shipped with the product.

Important! We recommend that you perform the migration in a test environment not in a production environment.

The following figure shows the migration path from a single system.

The following figure shows the migration path for a cluster environment.

You can set up a Federation Manager cluster to support failover. You can migrate from an existing r12.x cluster to a new cluster, using a procedure similar to a non-cluster migration. To migrate a cluster, you set up a new r12.5 system for each system in your existing cluster. The systems in a cluster share one data store. You migrate all data to the new r12.5 data store.

Follow these steps:

1. Export the configuration to an XML file and copy the key database. The exported file can act as a backup configuration.
2. Return the existing system to its original state. You deactivate partnerships to export the configuration, so you must reactivate the partnerships to use the original system and its configuration.
3. Synchronize key database instances.
4. Install and configure Federation Manager on each new system.
5. Configure each new system. Use the same settings for the new system that are used for the original system. The following settings for the new system must match:
   • Deployment mode

     Use the same deployment mode (proxy or standalone) for the new system.

   • SiteMinder Connector

     If SiteMinder is enabled on the original system, it must be enabled for the new system.

   • Port numbers

     When running the Configuration wizard, specify the same ports for the new system that the original system used.

   • Virtual Host Name

     If the original system used a virtual host, use the same virtual host name on the new system. Additionally, make the appropriate entries in the host file for the new system.

6. Import the exported configuration from the original system to the new system.

This process is detailed in the following sections.