Oracle GoldenGate Monitor Agent (JAGENT) for OEM on MS Windows Configuration Steps

The Oracle GoldenGate Jagent is no longer shipped with Oracle GoldenGate 12.2 and newer.  In fact, it has been a best practice since Oracle GoldenGate 12.1 to not use the Jagent that came with GoldenGate, but to use the Jagent from the GoldenGate Monitor Agent.  The Oracle GoldenGate Monitor is available from the Oracle Website under Middleware -> GoldenGate.  Download the Oracle GoldenGate Monitor 12.2.1 zip file from the selection under Management Pack for Oracle GoldenGate.  This will download the file fmw_12.2.1.0.0_ogg_Disk1_1of1.zip file.  The contents of this zip file can be used for all platforms and databases.

Prerequisites

Before you can install the Jagent, you must install java version 1.7 or newer.  This can be downloaded from the Oracle Website.  This must be completed before installing the Oracle GoldenGate Monitor Agent.
1.    Prepare the system
a.    Validate or install java jdk 1.7 or later
b.    Copy and install the latest java JDK to server.
c.    Install the JDK.
d.    This will install both the jre and jdk.  The jre is accessed by default.
Note:  When installing the JDK specify a directory such as C:\Oracle\Java\jdk1.8.0_91.  When prompted install the JRE in a directory such as C:\Oracle\Java\jre1.8.0_91.
Warning:  Do not install the JDK and JRE into a directory that has a space in the path such as “Program Files”.  This can potentially cause some Oracle scripts to fail.

Installation

The Monitor Agent must be installed on each of the GoldenGate servers that are to be included in Monitor or OEM monitoring.  This installation and configuration process is shown below.
If OEM monitoring is used with the JAGENT, the OEM agent must be installed as well.  Installing and configuring OEM is not covered here.  These steps are to be followed in order to configure the Jagent.

Install and Configure the Monitor Agent

1.    Install GoldenGate Monitor Agent only.
a.    Change directory to the location where the GoldenGate Monitor software has been saved.
b.    Set the environment variable JAVA_HOME to the JDK directory.
C:\Temp>  set JAVA_HOME=D:\Oracle\Java\jdk1.8.0_91
c.    Run the installer from java
C:\Temp>  D:\Oracle\Java\jdk1.8.0_91\bin\java –jar fmw_12.2.1.0.0_ogg.jar
d.    Choose to install Monitor Agent.
i.    Welcome Screen.  Click Next.

ii.    Auto Updates Screen.  Click Next.

iii.    Installation Location Screen.
This is the location where the agent software will be installed.
I used C:\app\Administrator\product\oggmon but you can choose your own location.

iv.    Installation Type Screen.
Choose Oracle GoldenGate Monitor Agent

v.    Prerequisites Checks Screen.  Click Next.

vi.    Installation Summary Screen.  Click Next.

vii.    Installation Progress Screen.  Wait for it to complete.

viii.    When completed and everything has a green check, click Finish.  The installer will exit.
2.    Change directory (using cmd as Administrator) to the oggmon\ogg_agent directory under where you just installed the Monitor Agent software.  In our case, this is C:\app\Administrator\products\oggmon\oggmon\ogg_agent.

3.    Set the JAVA_HOME environment variable.
Win>  set JAVA_HOME=C:\oracle\Java\jdk1.8.0_91
4.    Run the createMonitorAgentInstance.sh script.  You will be prompted for the GoldenGate installation directory and the location where you want to install the Monitor Agent instance.
Win>  createMonitorAgentInstance.bat
Please enter absolute path of Oracle GoldenGate home directory : C:\app\Administrator\product\12.2.0.1\oggcore_1
Please enter absolute path of OGG Agent instance : C:\app\Administrator\product\oggmon\agent1
Please enter unique name to replace timestamp in startMonitorAgent script (startMonitorAgentInstance_20160523141025.sh) : abcd
Sucessfully created OGG Agent instance.
5.    Change directory to the agent installation directory; C:\app\Administrator\product\oggmon\agent1.
6.    Change directory to the agent1\bin directory.
7.    Create the Jagent wallet.
a.    pw_agent_util.sh –jagentonly
b.    Supply a password.  This is the agent password that you will use in OME or GoldenGate Monitor.

C:\app\Administrator\product\oggmon\agent1\bin>pw_agent_util.bat -jagentonly
JAVA_HOME ‘c:\oracle\java\jdk1.8.0_91’
Please create a password for Java Agent:
Please confirm password for Java Agent:
Jun 01, 2016 2:28:45 PM oracle.security.jps.JpsStartup start
INFO: Jps initializing.
Jun 01, 2016 2:28:46 PM oracle.security.jps.JpsStartup start
INFO: Jps started.
Wallet is created successfully.

8.    Change directory to the agent1\cfg directory.
9.    Edit the Configuration.properties file.
a.    Modify jagent.host=localhost to change to the actual host name.
b.    Modify jagent.username=oggmajmxusr if desired (can be jagent, root, etc).
c.    Make note of jagent.rmi.port=5559.
d.    Modify agent.type.enabled=OGGMON to agent.type.enabled=OEM if using OEM for monitoring.
10.    Add ENABLEMONITORING to GLOBALS file.
11.    Restart the manager.
a.    This should be done from Windows Services.
b.    Once it has restarted the jagent will be visible in ggsci.
12.    Start JAGENT from GGSCI.
At this point the jagent should be running properly in GGSCI.

GGSCI (gg21a) 6> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
JAGENT      RUNNING

Once the Jagent is running, OEM or GoldenGate Monitor should be able to monitor GoldenGate.
Setting up GoldenGate Monitoring in OEM 13c will be presented in a future blog entry.