In a few weeks I’ll be talking about monitoring Oracle GoldenGolden using Oracle Enterprise Manager 12c at IOUG Collaborate in Las Vegas. This is one of the few presentations I will be giving that week (going to be a busy week). Although this posting, kinda mirrors a previous post on how to configure the Oracle GoldenGate JAgent, it is relevant because:
1. Oracle changed the name of the JAgent to Oracle Monitor Agent
2. Steps are a bit different with this configuration
Most people running Oracle GoldenGate and want to monitor the processes with EM12c, will try to use the embedded JAgent. This JAgent will work with the OGG Plug-in 220.127.116.11. To get many of the new features and use the new plug-in (18.104.22.168), the new Oracle Monitor Agent (22.214.171.124) needs to be downloaded and installed. Finding the binaries for this is not that easy though. In order to get the binaires, download Oracle GoldenGate Monitor v126.96.36.199.0 from OTN.oracle.com.
Once downloaded, unzip the file to a directory to a temp location
$ unzip ./fmw_188.8.131.52.0_ogg_Disk1_1of1.zip -d ./oggmonitor Archive: ./fmw_184.108.40.206.0_ogg_Disk1_1of1.zip inflating: ./oggmonitor/fmw_220.127.116.11.0_ogg.jar
In order to install the agent, you need to have java 1.8 installed somewhere that can be used. The 18.104.22.168.0 software is built using JDK 1.8.
$ ./java -jar ../../ggmonitor/fmw_22.214.171.124.0_ogg.jar
After executing the command, the OUI installer will start. As you walk through the OUI, when the select page comes up; select the option to only install the Oracle GoldenGate Monitor Agent.
After the installation is complete, then the JAgent needs to be configured. In order to do this, navigate to the directory where the binaries were installed.
$ cd /u01/app/oracle/product/jagent/oggmon/ogg_agent
In this directory, look for a file called create_ogg_agent_instance.sh. This files has to be ran first to create the JAgent that will be associated with Oracle GoldenGate. In order to run this script, the $JAVA_HOME variable needs to be pointed to the JDK 1.8 location as well. Inputs that will need to be provided are the Oracle GoldenGate Home and where to install the JAgent (this is different from where the OUI installed).
$ ./create_ogg_agent_instance.sh Please enter absolute path of Oracle GoldenGate home directory : /u01/app/oracle/product/126.96.36.199/12c/oggcore_1 Please enter absolute path of OGG Agent instance : /u01/app/oracle/product/188.8.131.52/jagent Sucessfully created OGG Agent instance.
Next, go to the directory for the OGG Agent Instance (JAgent), then to the configuration (cfg) directory. In this directory, the Config.properities file needs to be edited. Just like with the old embedded JAgent, the same variables have to be changed.
$ cd /u01/app/oracle/product/184.108.40.206/jagent $ cd ./cfg $ vi ./Config.properties
Change the following or keep the defaults, then save the file:
jagent.host=fred.acme.com (default is localhost) jagent.jmx.port=5555 (default is 5555) jagent.username=root (default oggmajmxuser) jagent.rmi.port=5559 (default is 5559) agent.type.enabled=OEM (default is OGGMON)
Then create the password that will be stored in the wallet directory under $OGG_HOME.
cd /u01/app/oracle/product/220.127.116.11/jagent $ cd ./bin $ ./pw_agent_util.sh -jagentonly Please create a password for Java Agent: Please confirm password for Java Agent: Mar 26, 2015 3:18:46 PM oracle.security.jps.JpsStartup start INFO: Jps initializing. Mar 26, 2015 3:18:47 PM oracle.security.jps.JpsStartup start INFO: Jps started. Wallet is created successfully.
Now, enable monitoring in the GLOBALS file in $OGG_HOME.
$ cd /u01/app/oracle/product/18.104.22.168/12c/oggcore_1 $ vi ./GLOBALS
$ ./ggsci Oracle GoldenGate Command Interpreter for Oracle<br>Version 22.214.171.124.0 OGGCORE_126.96.36.199.0_PLATFORMS_140727.2135.1_FBO Linux, x64, 64bit (optimized), Oracle 12c on Aug 7 2014 10:21:34 Operating system character set identified as UTF-8. Copyright (C) 1995, 2014, Oracle and/or its affiliates. All rights reserved. GGSCI (fred.acme.com)> info all Program Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING JAGENT STOPPED GGSCI (fred.acme.com)>; stop mgr! Sending STOP request to MANAGER ... Request processed. Manager stopped. GGSCI (fred.acme.com)>; delete datastore Are you sure you want to delete the datastore? yes Datastore deleted. GGSCI (fred.acme.com)>; exit $ ./ggsci Oracle GoldenGate Command Interpreter for Oracle Version 188.8.131.52.0 OGGCORE_184.108.40.206.0_PLATFORMS_140727.2135.1_FBO Linux, x64, 64bit (optimized), Oracle 12c on Aug 7 2014 10:21:34 Operating system character set identified as UTF-8. Copyright (C) 1995, 2014, Oracle and/or its affiliates. All rights reserved. GGSCI (fred.acme.com)>; create datastore Datastore created. GGSCI (fred.acme.com)>; start mgr Manager started. GGSCI (fred.acme.com)>; start jagent Sending START request to MANAGER ... JAGENT starting GGSCI (fred.acme.com)>; info all Program Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING JAGENT RUNNING
With the JAgent running, now configure Oracle Enterprise Manager 12c to use the JAgent.
Note: In order to monitor Oracle GoldenGate with Oracle Enterprise Manager 12c, you need to deploy the Oracle GoldenGate Plug-in (220.127.116.11).
To configure discovery of the Oracle GoldenGate process, go to Setup -> Add Target -> Configure Auto Discovery
Select the Host where the JAgent is running.
Ensure the the Discovery Module for GoldenGate Discovery is enabled and then click the Edit Parameters to provided the username and rmx port specified in the Config.properties file. And provide the password was setup in the wallet. Then click OK.
If the discovery was successful, the Oracle GoldenGate Manager process should be able to be seen and promoted for monitoring.
After promoting the Oracle GoldenGate processes, they can then be seen in the Oracle GoldenGate Interface within Oracle Enterprise Manager 12c (Target -> GoldenGate).
At this point, Oracle GoldenGate is being monitored by Oracle Enterprise Manager 12c. The new plug-in for Oracle GoldenGate is way better than the previous one; however, there still are a few thing that could be better. More on that later.