Federation Manager Guide › User Directory Connections for Authentication › ODBC Directory Connection › ODBC Directory Failover Configuration

ODBC Directory Failover Configuration

Federation Manager can distribute ODBC user directory requests over multiple data source servers for failover.

Note: Federation Manager does not support load balancing for ODBC user directories.

For failover, Federation Manager uses one ODBC directory to fulfill requests until that server where that store resides fails to respond. When the default directory does not respond, Federation Manager routes the request to the next store configured for failover. This process can be repeated over multiple servers. After the default server is able to fulfill requests again, Federation Manager routes requests back to the original server.

To configure ODBC failover

1. Select the User Directory tab in the UI.
2. Do one of the following:
   • Select Connect to ODBC to create an ODBC user directory connection.
   • Select Action, Edit next to an existing ODBC entry you want to edit.

   The User Directory dialog opens.

3. Click Configure Failover in the Configure ODBC User Directory section of the dialog.

   The ODBC Data Source Failover table displays.

4. Enter the data source name, in the first Failover Node field. Add the names of other data sources in the remaining fields for failover.

   Note: If you are adding a server for failover, the failover directory must use the same type of communication (SSL or non-SSL) as the primary directory because both directories share the same port number.

   If you only have one entry in the table, then Federation Manager only supports failover.

Example: ODBC Failover

In this example, a SiteMinder environment contains two user directories, A and B, which must meet the following requirements:

• User directory A must failover to user directory B
• User directory B must failover to user directory A

This configuration requires two failover nodes, one that specifies the data source name for user directory A and one that requires a data source name for user directory B.