6.2 Managing Veridata Agent
This topic describes how to manage Veridata Agent: C-agent and Java-based components. It also includes controlling logging levels and connecting to the web user interface.
This topic includes the following sections:
- Starting and Stopping the C-Agent
- Managing Java-Based Components
- Reloading Logging Information
- Connecting to the Oracle GoldenGate Veridata Web Interface
Parent topic: Administer
6.2.1 Starting and Stopping the C-Agent
When the Oracle GoldenGate Veridata (server) initiates comparisons, the C-agent starts automatically. However, for Oracle GoldenGate Veridata Agent (agent) to function correctly, the following must be running:
- The database to which the agent is linked.
- The Manager process for the C-agent.
Although the agent process itself is automatic, you can stop the Manager process that controls the agent. Stopping Manager prevents the server from being able to start a new agent process, but it does not stop agents that are already running.
To control the C-agent Manager:
- From the agent installation location, run the Oracle GoldenGate software command-line interface.
- Stop or start the Manager.
START MANAGER STOP MANAGER
Parent topic: Managing Veridata Agent
6.2.2 Managing Java-Based Components
Parent topic: Managing Veridata Agent
6.2.2.1 Starting and Stopping the Java-Based Components
The server and web user interface components are Java programs. The agent component is also available as a Java program for all platforms except NonStop.
Note:
Before starting the server and web processes, start the repository database.To start and stop the Java agent component:
- Navigate to the
AGENT_DEPLOY_HOME
directory. - Start or stop the agent.
- In these commands:
run
starts the agent in the same command window where it is launched.start
starts the agent in a separate command window.
Note:
Therun
option is useful for diagnosing errors that happen during the startup process before the agent error logging is configured. When therun
option is used, messages written tostdout
andstderr
appear in the command window. The agent normally logs its messages to the log file, so only operating system messages and logging system errors are written tostderr
. When the start option is used, messages written tostdout
andstderr
are discarded.
Configure the host to start and stop the processes automatically. Contact your system administrator if you need assistance.
Parent topic: Managing Java-Based Components
6.2.2.2 Managing Bequeath Agent
export ORACLE_HOME=<path>
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
For the JDBC URL details, see Oracle OCI bequeath database connection URL:
$ORACLE_HOME/jdbc/lib
to the
<Agent_Home>/drivers
directory. Then, update the agent.properties
file accordingly with the following entry:
server.jdbcDriver=ojdbc11.jar
Parent topic: Managing Java-Based Components
6.2.3 Reloading Logging Information
You can reload logging information from the
<VERIDATA_AGENT_HOME>/config/odl.xml
configuration file to a running agent.
To reload logging information, start the agent and
run the UNIX/Linuz reloadLog
command as follows: agent.sh
reloadLog
Parent topic: Managing Veridata Agent
6.2.4 Connecting to the Oracle GoldenGate Veridata Web Interface
To connect to the Oracle GoldenGate Veridata Web user interface:
-
In a Web browser, enter the following address:
http://hostname:port/veridata
.In this example,
hostname
is the name of the system where the server is installed andport
is the port number where it is running (default is 8831). Uselocalhost
as the host name if you are connecting on the system that is local to the server installation. -
On the Oracle GoldenGate Veridata Web login page, enter your user name and password. For full instructions on using the Oracle GoldenGate Veridata web user interface, see the online help.
Parent topic: Managing Veridata Agent