Configure

• High Availability

High Availability

High Availability (HA) refers to the ability of a system, application, or services to remain operational and accessible with minimal downtime. It ensures that an application continues to function even in the event of failures, such as hardware crashes, network issues, or software bugs. You can configure High Availability for the Oracle GoldenGate Veridata Server and Agent in several ways. This article explains one such method.

Figure 1: High Availability for Veridata Server

To establish High Availability in Oracle GoldenGate Veridata:

1. Deploy Veridata Server on the nodes that share a Virtual IP between them.

2. Connect to Veridata Server using a VIP to establish an Active-Passive setup. In such a set up, even when one Server node goes down, the other node serves the purpose. Ensure that there is a shared file system for storing the logs, reports, and oosxml files from the active server, so that when the Standby server turns active it can have access to all the files.

Note:

For the MySQL repository:

• Install external MySQL, version mysql-commercial-8.0.42 and above.

• Ensure that the repository is highly available.

• Setting Up the High Availability for Oracle GoldenGate Veridata Server

• Configuring a Shared File Path

• Setting up High Availability for Oracle GoldenGate Veridata Agent

Setting Up the High Availability for Oracle GoldenGate Veridata Server

To set up HA for Veridata Server:

1. Install Veridata Server on all the nodes which share a common Virtual IP between them.

2. Ensure that all nodes use the same port for Veridata Server.

3. Edit the repository.url property in <veridata_home>/config/oggvdt_cainput.properties file, to ensure that both the servers point to the same shared repository.

4. For more information about Oracle GoldenGate Veridata installation, see Installing and Running Oracle GoldenGate Veridata.

Configuring a Shared File Path

• Reports

• Wallet

Reports

Ensure that Oracle GoldenGate Veridata reports are stored in a shared file system which can be accessed by all the nodes configured using the VIP. Shared storage path can be given in veridata.cfg as follows:

server.veridata_data property must be updated to the new shared storage path:

server.veridata_data new_path/veridata/reports

Wallet

The wallet that stores the passwords of connections or users must also be stored in the shared file path.

To configure wallet to shared path:

1. Nagivate to the config in the Veridata installation directory.

2. Open jps-config-jse.xml and update the shared path in the below xml tag in location attribute.

   <serviceInstance name="credstore" provider="credstoressp" location=". ">

   For example: <serviceInstance name="credstore" provider="credstoressp" location="/u01/config ">

In the Veridata server, the wallet path is hard-coded in the JPS configuration file.

To change it to a user-preferred directory path, follow the steps below:

1. Set the environment variable to override the wallet path to export CREDENTIAL_LOCATION=<path>

2. Restart the server after setting the environment variable.

Setting up High Availability for Oracle GoldenGate Veridata Agent

In Oracle GoldenGate Veridata, the agent is deployed as a Java Standalone application. To establish agent HA, deploy the agent on nodes sharing a Virtual IP (VIP) between them and then connect the Veridata Server to agent via VIP.

Ensure that agents running on different nodes are using the same port number. The agent.propreties from node1 must be copied to node2 as well and must be kept in sync for the changes.

Figure 2: High Availibility for Oracle GoldenGate Veridata Agent