Datasource Failover and Load Balancing Configuration for Identity Suite Virtual Appliance
search cancel

Datasource Failover and Load Balancing Configuration for Identity Suite Virtual Appliance

book

Article ID: 223604

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Suite

Issue/Introduction

When configuring an external database for the Identity Suite Virtual Appliance (vApp), administrators may need to implement failover and load balancing to ensure high availability. This is achieved by defining multiple database hosts within the JDBC connection string (DB_URL) during datasource creation.

Symptoms

  • Requirement to connect to an Oracle Real Application Cluster (RAC).
  • Need to ensure system availability during Oracle infrastructure changes or database instance failures.
  • Requirement to implement LOAD_BALANCE and FAILOVER parameters at the JDBC level.

Environment

Identity Suite 14.x

Cause

Standard single-host connection strings do not provide automatic redirection if a database node becomes unavailable.

Resolution

JDBC Connection String Syntax

The DB_URL entry in the Virtual Appliance allows for multiple hosts. Use the following syntax for a resilient connection string:

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=ON)(FAILOVER=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=host1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=host2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=your_service_name)(FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC))))

Implementation Guidelines

  1. VApp Interface: Always enter the complex connection string in the DB_URL field during the datasource creation process in the VApp dashboard.
  2. Testing Requirement: While the Virtual Appliance accepts multiple hosts in the JDBC string, this configuration must be thoroughly validated in a non-production environment to ensure the application behaves correctly during a database node switch.
  3. Proxy/Scan Alternative: For optimal stability, it is recommended to use a SCAN (Single Client Access Name) address or a proxy host. This allows the database backend to manage load balancing and failover, which provides better control than relying solely on the application server's JDBC driver.