3.3 Installing and Configuring Source and Target Agents

From the agent directory, install and configure source and target agents.

3.3.1 About Oracle GoldenGate Veridata Agent Deployment Scripts

After installing Oracle GoldenGate Veridata Agent using Oracle Universal Installer, you must deploy the agent to a non Oracle Home location and configure the agent before running comparison jobs using a deployment script provided in the installation.

The following table describes the directories and the variables that are used when referring to those directories in this section.

Table 3-1 Directories in an Oracle GoldenGate Veridata Installation

Directory Variable Directory Path

VERIDATA_HOME

This is the home directory where Oracle GoldenGate Veridata is installed. For example, VERIDATA_HOME in this documentation is /scratch/vdt23c.

VERIDATA_AGENT_HOME

VERIDATA_HOME/agent. This is the location where Oracle GoldenGate Veridata agent is installed.

AGENT_DEPLOY_LOCATION

This is the location where the Oracle GoldenGate Veridata Agent is deployed.

Note that this location should be outside the VERIDATA_HOME.

The agent_config.sh script located in the VERIDATA_AGENT_HOME directory is used for deploying the Oracle GoldenGate Veridata Agent.

Syntax:

export JAVA_HOME=/usr/java/jdk17
cd /scratch/vdt23c/agent
./agent_config.sh /scratch/agent1
./agent_config.sh /scratch/agent2
cd /scratch/agent1
cp sample_properties/agent.properties.oracle agent.properties
(EDIT agent.properties per documentation)
./agent.sh start agent.properties

The AGENT_DEPLOY_LOCATION can be an absolute path or a path relative to the location from where the script is running.

Note:

You must deploy the Oracle GoldenGate Veridata Agent to a directory outside VERIDATA_HOME.

3.3.2 Configuring Oracle GoldenGate Veridata Agent

You must configure the Oracle GoldenGate Veridata Agent to use your database.

  1. Go to the agent deployed location AGENT_DEPLOY_LOCATION.

    There is an agent.properties.sample file in this directory that contains database related properties like JDBC URL and driver.

  2. Copy the agent.properties.sample file and rename to agent.properties.
  3. Most of the properties defined in the file have default values. However, you must update the following properties:
    1. The server.port property is the port where the Oracle GoldenGate Veridata Agent listens for connection requests.
      server.port= <Port Number>

      For example, <Port Number> = 7862

    2. The database.url specifies the JDBC connection URL for the database. Samples for all supported databases are provided in the file.
      database.url=<Database URL>

      For example, <Database URL>=jdbc:oracle:thin:@localhost:1521:orcl.

    3. The server.jdbcDriver property specifies the list of JDBC driver JAR files. Sample lists for the supported databases are provided in the file.

      Use the driver corresponding to the database.url in the preceding step.

      server.jdbcDriver=<JDBC Driver>

      For example, <JDBC Driver>= ojdbc11-23.2.0.0.jar.

  4. Oracle, MySQL, PostgreSQL, SQL Server, DB2 and Sybase drivers are available in VERIDATA_HOME/agent/drivers. For any other drivers you want to use, copy the driver to VERIDATA_HOME/agent/drivers. For more information, see Agent Parameters - Connections.

After the Oracle GoldenGate Veridata agent is installed, you need to configure 2-way SSL. See Configuring Workflow for Two-Way SSL in Oracle GoldenGate Veridata 23c.

3.3.3 Starting the Oracle GoldenGate Veridata Agent

Go to the agent deployment location AGENT_DEPLOY_LOCATION and run following command.

$ ./agent.sh start agent.properties

Where agent.properties is the properties file that contains your database properties.

3.3.4 Using the Oracle GoldenGate Veridata Agent Deployment Script in Debug Mode

For debugging issues with the Veridata Agent deployment, run the agent_config script with an additional command line argument as follows:

Syntax:

<VERIDATA_AGENT_HOME>/agent_config.sh AGENT_DEPLOY_LOCATION true

When this option is true, the debug logs are printed on the screen.

3.3.5 Reloading the Logging Properties of the Veridata Agent

You can reload logging information from the VERIDATA_AGENT_HOME/config/odl.xml configuration file to a running agent by using the reloadLog option. The changes in the odl.xml file are put into effect on the agent. The agent must be running for this command to work.

  1. Open the command prompt and navigate to the directory where the agent is installed.
  2. Go to <AGENT_DEPLOY_LOCATION> and run the following command:
    ./agent.sh reloadLog
    If agent properties are stored in a custom file other than agent.properties, then run the following command:
    ./agent.sh reloadLog <AGENT_PROPERTIES_FILENAME>