6.1 Managing C-Agent and Java Components

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

This topic includes the following sections:

6.1.1 Starting and Stopping the Veridata Server and the Repository

To start the Oracle GoldenGate Veridata server:

  1. Go to <VERIDATA_HOME>/bin.
  2. Run the following command ./run.sh (starts the repository also in case it is down).

    Or

    ./run.sh skipRepoStart (if you want to ignore the repository status and just start the server)

To stop the Oracle GoldenGate Veridata server:

  1. Go to <VERIDATA_HOME>/bin.
  2. Run the following command ./run.sh stop.

To start and stop the repository:

  1. Go to <VERIDATA_HOME>/bin.
  2. Run the following commands:
    • To start the repository: ./run.sh repoStart.
    • To stop the repository: ./run.sh repoStop.
    • To know the repository status: ./run.sh repoStatus.

6.1.2 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:

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

6.1.3 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:

  1. Navigate to the AGENT_DEPLOY_HOME directory.
  2. Start or stop the agent.
    Operating System
    UNIX or LINUX
    agent.sh {start | run} OR agent.sh 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.

6.1.4 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

6.1.5 Connecting to the Oracle GoldenGate Veridata Web Interface

To connect to the Oracle GoldenGate Veridata Web user interface:

  1. 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 8831). Use localhost as the host name if you are connecting on the system that is local to the server installation.

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