Federation Manager Guide › Configuration Backup and Restoration › How To Restore a Single System to a Previous Configuration › Revert to a Backed-up Configuration

Revert to a Backed-up Configuration

If you experience any problems with your existing Federation Manager configuration, you can revert to a previously backed up Federation Manager configuration on the same system.

Restoring a configuration requires the use of the XPSImport tool that is shipped with Federation Manager.

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

To revert to a backed-up Federation Manager configuration

1. Run the Federation Manager Configuration wizard, using a new database instance.

   Use the same settings for this new configuration that were used when Federation Manager was originally configured on the system. These settings include:

   • Port numbers
   • Virtual Host Name

   Important! Do not use an existing database for this step. The import will fail if you do.

2. Stop Federation Manager services, as follows:

   Windows

   Select Start, All Programs, CA, FederationManager, Stop services.

   Solaris

   1. Open a command window.
   2. Run the following script:

      federation_mgr_home/fedmanager.sh stop

      When you run the fedmanager.sh script, it sources the Federation Manager environment script, ca_federation_env.ksh.

      Note: Do not stop and start the services as the root user. You must be a non-root user.

3. Restore the key database by doing the following:
   1. Rename or delete the directory federation_manager_home/siteminder/smkeydatabase
   2. Copy the previously backed-up database to federation_manager_home/siteminder directory.
4. Restore all other configuration data using the XPSImport command, as follows:

   XPSImport export_file_name -passphrase passphrase

   • export_file_name

     Names the XML file that resulted from the export of the original configuration. The filename should end with the extension .xml.

   • passphrase

     Specifies the passphrase required to decrypt sensitive data. It must be at least eight characters and must contain at least one digit, one upper case and one lower case letter. If the passphrase contains a space, then it must be enclosed in quotes.

5. Re-run the Federation Manager Configuration wizard.

   Use the same settings for this new configuration that were used when Federation Manager was originally configured on the system. These settings include:

   • Port numbers
   • Virtual Host Name
6. Log back in to the Federation Manager UI.
7. Select the Federation tab and click Partnerships.

   The View Federation Partnerships window opens.

8. Select Activate from the Action menu next to each deactivated partnership in the Federation Partnership list. This re-activates all the partnerships.
9. (Optional) If the SiteMinder Connector was enabled in the original configuration, reestablish the Connector by doing the following:
   1. Click the Infrastructure tab and select Deployment Settings.
   2. Reconfigure the SiteMinder Connector settings using the same values that were used by the original configuration.
   3. Click Register Host to reregister Federation Manager with the SiteMinder Policy Server.

The Federation Manager configuration is restored to the state it was when the configuration was backed up.