This chapter describes the tasks required once you have updated your version of Oracle GoldenGate Monitor to the current version.
This chapter contains the following sections:
Note:
After upgrading to Oracle GoldenGate Monitor 12c (12.1.3), Oracle GoldenGate Monitor 11g users cannot immediately log in to it. You must create users and assign privileges by using the Oracle WebLogic Administration Console. For more information, see "Managing Users from the WebLogic Administration Console" in Installing and Configuring Oracle GoldenGate Monitor Server.
With the existing Oracle GoldenGate Monitor Server database successfully upgraded from 11.x to 12c (12.1.3), you need to create a Weblogic domain for the server implementation that runs with the upgraded schema. You must use the upgraded Monitor schema during this process. For Oracle databases, you need to create an expanded domain; however, you can only create compact domains for non-Oracle databases because they do not support the Oracle Platform Security Service (OPSS). Follow the procedure for the specific database, described in Installing and Configuring Oracle GoldenGate Monitor Server:
To create an expanded domain for Oracle databases, see "Configuring the Server for Oracle Databases"
To create a compact domain for non-Oracle databases (that is, MySQL and Microsoft SQL Server), see "Configuring the Server for Non-Oracle Databases".
Note:
The procedure in this section is required only if an existing customer is upgrading the Oracle GoldenGate Monitor from 11g version to 12.1.3 software.
Once the Oracle GoldenGate Monitor Server domains are created successfully, set your JAVA_HOME and then run the upgrade configuration scripts (monitor_server_cfg_update.sh and monitor_server_cfg_update.bat) to upgrade the server configuration and properties that are installed during domain creation.
The monitor_server_cfg_update.sh (Linux) and monitor_server_cfg_update.bat (Windows) scripts update the configuration properties files—which are under the newly-created domain's DOMAIN_NAME/config/monitorserver/cfg/ folder—with the Monitor server configuration and properties details from old Monitor 11g installation cfg/ directory.
To run the scripts, do the following:
Navigate to the DOMAIN_HOME/oggmon/plugins/upgrade/script folder and enter:
On Linux:
$ ./monitor_server_cfg_update.sh
On Windows:
monitor_server_cfg_update.bat
The system responds:
Enter absolute path to cfg directory of Monitor 11g installation
Enter (for example):
On Linux:
/apps/monitor/cfg : /scratch/username/Monitor-11.2.1.7/oggmon_ms/cfg
On Windows:
C\apps\monitor\cfg : C:\username\Monitor-11.2.1.7\oggmon_ms/cfg
The system responds:
Enter absolute path to cfg directory of current Monitor installation
Enter (for example):
On Linux:
/weblogic/user_projects/domains/YOUR_DOMAIN_NAME/config/monitorserver/cfg) : /scratch/username/Oracle/DOMAIN_HOME/user_projects/domains/one_domain/config/monitorserver/cfg
On Windows:
C:\weblogic\user_projects\domains\YOUR_DOMAIN_NAME\config/monitorserver\cfg) : C:\username\Oracle/DOMAIN_HOME\user_projects\domains\one_domain\config/monitorserver\cfg
After running the upgrade configuration scripts described in Section 3.2, "Run the Post-Upgrade Configuration Scripts", use the following procedure to create an Oracle GoldenGate agent instance:
Stop the Oracle GoldenGate agent instance that is pointing to the Oracle GoldenGate Monitor 11g server.
Create an Oracle GoldenGate agent instance by following the instance set up instructions in Installing and Configuring Oracle GoldenGate Monitor Agent.
Once you have the Oracle GoldenGate agent (12c) instance, update the jagent.jmx.port property in OGG_AGENT_INST_HOME/cfg/Config.properties in the 12c instance by adding the port number value from the Oracle GoldenGate Agent 11g OGG_HOME/cfg/Config.properties. Also, ensure that all Oracle GoldenGate agent configuration property values are set correctly.
Note:
Ensure that all Oracle GoldenGate agent configuration property (MonitorServer JMX properties) values are set correctly with the newly created 12c Monitor server setup.
Remove existing Oracle GoldenGate JAgent (JAGENT) software that was bundled with Oracle GoldenGate Software by doing the following:
Delete OGG_HOME/cfg folder
Delete OGG_HOME/dirjar folder
Delete OGG_HOME/pw_agent_util.* files
Delete OGG_HOME/jagent.* files
Start the Oracle GoldenGate agent from Oracle GoldenGate Core GGSCI console by entering start jagent.
Finally, start the Oracle GoldenGate Monitor Server by running the scripts described below from your domain directory:
Compact domains are used for MySQL and SQL Server databases. To start an Oracle GoldenGate Monitor Server that is running a MySQL database, navigate to MONITORSERVER_MYSQL_DOMAIN and the following command:
On Linux:
$ ./startWebLogic.sh
On Windows:
C:\MONITORSERVER_MYSQL_DOMAIN> startWebLogic.cmd
To start the Monitor server that is running a SQLServer database, navigate to MONITORSERVER_SQLSERVER_DOMAIN and the following command:
On Linux:
$ ./startWebLogic.sh
On Windows:
C:\MONITORSERVER_SQLSERVER_DOMAIN> startWebLogic.cmd
Expanded domains are used for Oracle databases. To start Oracle GoldenGate Monitor Server running with this type of database, do the following:
Navigate to MONITORSERVER_GOLDENGATE_DOMAIN and run the following scripts to start the Weblogic Administration Server as described in "Start the WebLogic Administration Server" in Installing and Configuring Oracle GoldenGate Monitor Server.
Navigate to MONITORSERVER_GOLDENGATE_DOMAIN/bin, and start the Weblogic 12c (12.1.3) Managed Server, as described in "Start the WebLogic Managed Server" in Installing and Configuring Oracle GoldenGate Monitor Server.
Run this script with the arguments noted:
$ ./startManagedWebLogic.sh MONITOR_server1 http://<hostname>:7001
Open the WebLogic Administration Console and, following the instructions in "Managing Monitor Server Users from the WebLogic Administration Console" in Installing and Configuring Oracle GoldenGate Monitor Server, create a Oracle GoldenGate Monitor user.
Once you have completed the preceding steps, log in to Oracle GoldenGate Monitor with the username and password created in the Weblogic Server and verify system functionality.