We have released GoldenGate OEM Plug-in 220.127.116.11.0. The release's primary focus was to support the monitoring of Oracle GoldenGate 18.1, 19.1 Microservices (MA) Instances. In the earlier GoldenGate OEM Plug-in 18.104.22.168.0 release, we started supporting our first GoldenGate 12.3 Microservices Instance. In the new release, we have certified the latest of GoldenGate releases 18.1 and 19.1 Microservices and Classic. Along with the certification, we are supporting the new metrics for coordinated and parallel replicats. We have provided more services(Administration Service and Service Manager) and Deployments support in the plug-in. You may discover the new targets in the discovery module and promote the targets of your choice. Finally, we have certified the OEM 13.3 in the release.
Once you discover targets, you can select the processes(Extract, Replicat, etc) while promoting the targets. The selected processes(aka targets) and its parent process would get promoted automatically. For example, if you select the Extract process under Admin Server, the OEM PlugIn will promote the selected Extract process, Admin Server (which is Extract’s Parent), and Service Manager (which is Admin Server’s Parent). On a similar line, if you select the parent process, all the children will be selected by default and then you may choose to de-select the particular child.
Once you promote the processes or targets, you may notice the changes in Dashboard User Interface for Microservices processes. All the processes are shown in the tree structure. The Service Manager is the parent process, which shows one or many GoldenGate Deployments, all the extracts and Replicats are part of Admin Server. You may see all the services status on the screen. Along with the Microservices Instance, you may monitor the Classic Instance on the same dashboard. We have given each process(Target) a specific type name as per GoldenGate terminologies. It will be helpful when you want to know about what type of Extract or Replicats you are monitoring (Classic or Integrated Extract, Coordinated or Parallel Replicat).
When you click on the Service Manager on the dashboard, it will direct you to the below-mentioned page. The page shows all the Deployments and the details of its services, such as Port and Status. In the future, you should be able to search across a particular Deployment. The admin Server page will show all the extract and Replicats processes and its detailed metrics. When you click on individual Extract, Replicat you will be able to see the Metrics, Logs, and Configuration of the process.
For the Parallel and Coordinated replicat(PR/CR), you can see the accumulated metrics in the Parent process. The children process of the PR/CR is not visible on the screen. In the future, we will provide options to select the child process and then you would be able to monitor those children as well.
The GoldenGate OEM Plug-in has upgraded infrastructure to be compatible with the newer version of Enterprise Manager (EM) to 22.214.171.124.0. As mentioned earlier, we have certified the GoldenGate 18.1, 19.1 Classic and Microservices and added few metrics related to Parallel Replicat and Coordinated replicat.
Just to recap the communication between EM Agent and GoldenGate MA, and Classic Instances. You would not require to setup GoldenGate jAgent(Monitor Agent) to communicate with GoldenGate OEM Plug-in for GoldenGate Microservices Instances. The GoldenGate MA architecture provides the RESTful APIs to monitor and manage the GoldenGate MA Instances. The GoldenGate OEM Plug-in uses these RESTful APIs to communicate with GoldenGate MA Instances. For your GoldenGate Classic Instances, you would still need to setup GoldenGate jAgent 126.96.36.199.0+ for the communication purposes. The latest Monitor Agent was released on May, 19 (188.8.131.52.190530).
We are working to get more features around monitoring the GoldenGate Microservices and Classic architecture in future releases. Please stay tuned for further updates.