1. Oracle GoldenGate System Monitoring Plug-In User Guide
  2. Enabling Hybrid Cloud Monitoring on Oracle GoldenGate Cloud Service

5 Enabling Hybrid Cloud Monitoring on Oracle GoldenGate Cloud Service

This section discusses using the Enterprise manager Cloud Control console to administer both your Oracle cloud and on-premises deployments.

Topics

5.1 About Hybrid Cloud Monitoring

You can use the Enterprise Manager Cloud Control console to administer both your on-premises and Oracle Cloud deployments.

Oracle Hybrid Cloud lets you as an on-premises Enterprise Manager administrator, monitor and manage cloud services using the same Oracle Enterprise Manager tools to monitor, provision, and maintain Oracle Databases, Engineered Systems, Oracle Applications, Oracle Middleware, and a variety of third-party systems. See Enabling Hybrid Cloud Managementin Enterprise Manager Cloud Control Administrator's Guide.

5.2 Installing the Monitor Agent on Cloud Device to Configure the JAgent

You must install the monitor agent on your cloud device to configure the JAgent:

  1. Provide the latest release file, which is fmw_12.2.1.2.0_ogg_generic.jar.
  2. Copy the file into the cloud device.
  3. Select Monitor agent only and provide the location for installation.

    Note:

    You must have permission to install in the mentioned location.
  4. Once the installation is complete, go to MON_AGENT_INST_LOC/oggmon/ogg_agent directory.
  5. Run the createMonitorAgentInstance.sh. Provide the Oracle GoldenGate core location, for example /u01/app/oracle/gghome when asked.
    Provide a new location /u02/data/Agent_Inst to create an agent instance for the monitor.
  6. Go to the AGENT_INST_LOC/bin directory.
  7. Run pw_agent_util.sh -jagentonly.
    • Create a password for Java Agent:
    • Confirm password for Java Agent:
  8. Go to the AGENT_INST_LOC/cfg directory.
  9. Modify the Config.properties file and change agent.type = OEM and save the file.

5.3 Creating an Inventory Location for Non Oracle Users

You must create a new inventory location for non Oracke users as they do not have direct access to Oracle GoldenGate Cloud Service POD machines through Oracle user. Without this access they’re unable to push the Hybrid cloud agent from the Enterprise Cloud interface.

To create a new inventory location for the opc user:

  1. Copy the createCentralInventory.sh script to the GGCS POD machine.
  2. Login as an opc user then use the sudo su # command.
  3. Create the inventory directory.

    Example: /u02/data/opcuser/oraInventory directory.

  4. Run the create inventory script ./createCentralInventory1479193434142.sh inventory_location group_name.

    Example: ./createCentralInventory1479193434142.sh /u02/data/opcuser/oraInventory opc.

  5. Change the permission of inventory folder from root to opc using the chown command.

    Example: chown opc /u02/data/opcuser/oraInventory.

  6. Use Ctrl+D to come out from root user and change to opc user.
  7. Create an emagent folder as opc user to push the Hybrid cloud agent.
  8. Push the Hybrid cloud agent from Enterprise Manager interface.
The location of createCentralInventory.sh will be provided separately.

5.4 Configuring JAgent in the Provisioning Environment

You must configure the JAgent to work in the provisioning environment.

  1. Go to GGHOME location and start the GGSCI console using the ./ggsci command.
  2. Use the info-all command to verify that only the manager process has stopped.
  3. Use the view param mgr command to check the parameters in MGR.prm file and modify the port as needed
  4. Exit the GGSCI console.
  5. Create the GLOBALS file and provide the value as ENABLEMONITORING and save it in the GGHOME location.
  6. Start the GGSCI console and use the create datastore command to create the datastore.
The GGSCI should show both the manager and JAgent processes.

5.5 Installing the Hybrid Cloud Gateway Agent

Install the EM Agent on the machine A, which is marked as a Hybrid Cloud Gateway Agent.

  1. From the Setup menu, select Add Target, then Add Target Manually, and then select Install Agent on Host.
  2. Add the Host Target. Enter the host name, for example A, and platform, for example platform = Linux x86-64. Click Next.
  3. Add Installation base directory to a location on machine A.
  4. Add Named Credential to Host credential of Machine A.
  5. Don’t add a value in the Port field. The system uses an available free port. Click Next.
  6. Click Deploy Agent.

    Ignore any warning that is displayed.

  7. Click Continue On All Host.
  8. Run the /usr/local/packages/aime/em/run_as_root /scratch/userID/emagentm/agent_13.1.0.0.0/root.sh command to complete the installation.

5.6 Configuring the EM Hybrid Cloud

You must configure the Hybrid Cloud agent.

  1. In the Enterprise Manager Plug-in for Oracle GoldenGate UI, select Setup, Add Target, Add Target Manually, Install Agent on Host.
  2. Add the Host Target. Enter the host name and platform. Click Next.
  3. Add the Installation base directory. It is the same location as in host provided in step 2.

    It’s the same location as you provided in the previous step for the host .

  4. Add the Named Credential to the host as provided in step 2.

    You must have privilege to the location provided in the previous step.

  5. Don’t provide the port value. The system allocates a free port. Click Next.
  6. Click Deploy Agent.
  7. Provide the details about the known error, which appears.

5.7 Configuring the SOCKS Proxy Setup

To configure the SOCKS proxy to work with the cloud device:

  1. Login to the cloud or POD box using the credentials provided during the Hybrid agent installation.
  2. Use this command to start the proxy server on the cloud device.

    ssh -i private_key file -v -N -f -D listening IP Address:listening IP port GGCS Oracle User@GGCS IP Address

    ssh -i opc_rsa -v -f -N -D 1080 USER@$_IP

    ssh -i private_key file -v -N -f -D listening IP Address:listening IP port

    • -i: Private Key File

    • -v: Verbose Mode

    • -N: No execution command on remote system

    • -f: Run the proxy process in the background

    • -D: Dynamic Port Forwarding

    • -C: Compression