High-availability configuration for Access Manager

In environments that require high availability, you can configure a cluster of two or more Access Managers that fail over during a system outage. You can also decouple the embedded database in Access Manager and configure it to use an external database.

By default, each instance of Access Manager contains an embedded database, which is used to persist data. To enable high availability for the Access Manager database, you must decouple this data source so Access Manager can communicate with an external database. After you separate the embedded database from the Access Manager, you can cluster an external database.
Enabling Access Manager to communicate with a different data source requires that you add the following properties to the context.xml file:

• JPA Hibernate dialect
• Data source driver class name
• JDBC URL
• Data source user name
• Data source password

• Configuring Access Manager for high availability