6 Deploying and Configuring Oracle GoldenGate Veridata Agent

Learn how to deploy and configure the Oracle GoldenGate Veridata agent of the Oracle WebLogic Server domain. Find out how to start and stop the agent, reload the logging properties, and how to use the agent in debugging mode.

6.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 6-1 Directories in an Oracle GoldenGate Veridata Installation

Directory Variable Directory Path

ORACLE_HOME

/install_location/Oracle_Home. This is the home directory for the Oracle Fusion Middleware products.

VERIDATA_PRODUCT_HOME

/ORACLE_HOME/veridata

AGENT_ORACLE_HOME

/VERIDATA_PRODUCT_HOME/agent

AGENT_DEPLOY_LOCATION

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

Note that this location should be outside the ORACLE_HOME.

The agent_config.sh|.bat script located in the AGENT_ORACLE_HOME directory is used for deploying the Veridata Agent.

Syntax:

agent_config.sh|.bat AGENT_DEPLOY_LOCATION

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 ORACLE_HOME.

6.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=server.port
      

      For example, server.port=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=<server.jdbcDriver>

      For example, server.jdbcDriver=ojdbc8.jar.

  4. Copy the drivers to the driver location which is available at: AGENT_DEPLOY_LOCATION/drivers.

6.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.

6.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:

agent_config.sh|.bat AGENT_DEPLOY_LOCATION true

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

6.5 Reload the Logging Properties of the Veridata Agent

You can reload logging information from the AGENT_ORACLE_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. Run the following command to load the AGENT_ORACLE_HOME/config/odl.xml configuration file:
    agent.sh|bat reloadLog