Managing C-Agent, Manager, and Java Components

3 Managing C-Agent, Manager, and Java Components

This chapter describes how to manage C-agent, manager, and Java-based components, including controlling logging levels and connecting to the web user interface.

This chapter includes the following sections:

3.1 Starting and Stopping the C-Agent and the Oracle GoldenGate Veridata Manager

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 on all platforms

From the agent installation location, run the Oracle GoldenGate software command-line interface.
Stop or start the Manager.
```
START MANAGER
```
```
STOP MANAGER
```

3.2 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 agent component:

Switch to its installation directory.
Start or stop the agent.

Operating System

UNIX or LINUX

agent.sh {start | run} OR agent.sh stop

Windows

agent.bat {start | run} OR agent.bat stop
- 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:
The run option is useful for diagnosing errors that happen during the startup process before the agent error logging is configured. When the run option is used, messages written to stdout and stderr 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 to stderr. When the start option is used, messages written to stdout and stderr are discarded.

Configure the host to start and stop the processes automatically. Contact your system administrator if you need assistance.

3.3 Reloading Logging Information

You can reload logging information from the AGENT_ORACLE_HOME/config/odl.xml configuration file to a running agent.

To reload logging information, start the agent and run the reloadLog commands shown in the following table:

UNIX and Linux	Windows
agent.sh reloadLog	agent.bat reloadLog

3.4 Controlling Logging Levels for Oracle GoldenGate Veridata Agent

To control the agent logging levels so that they log more information for debugging purposes, update the AGENT_ORACLE_HOME/config/odl.xmlconfiguration file. Relevant comments are provided in the odl.xml file.

3.5 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 and port is the port number where it is running (default is 8830). Use localhost as the host name if you are connecting on the system that is local to the server installation.
Examples:
```
http://localhost:8830/veridata
http://sysa:8830/veridata
```
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.