This post covers Microservices Architecture (MA) introduced in Oracle GoldenGate 12CR3 and five components that are part of this Architecture i.e. Administration, Distribution, Receiver, Service and Performance Metrics Server. Oracle GoldenGate Microservices Architecture (MA) enables you to configure, monitor, and manage Oracle GoldenGate services using REST API with JSON and also using web-based user interface.
I recently did a webinar on Oracle GoldenGate 12c for Replication & Cloud Migration including the new Architecture i.e. Microservices where GoldenGate Expert Ashish and I discussed this new MicroServices Architecture, you can watch the complete webinar HERE (Need Name and Email to watch Replay).
Classic VS Microservices (MA)
In Oracle GoldenGate 12.3, we have two architectures available for deploying GoldenGate
- Classic Architecture
- Microservices Architecture
The Microservices Architecture in Oracle GoldenGate is comprised of five main components:
- Service Manager
- Administration Server
- Receiver Server
- Distribution Server
- Performance Metrics Server
1. Service Manager: Enables to administer, monitor and manage other services available in Microservices Architecture.
2. Administration Server: An Administration Server supervises, administers, manages, and monitors processes operating within an Oracle GoldenGate deployment for both active and inactive processes. It is the central and main entity for managing the various components of a GoldenGate deployment. Administration Server can create and manage local Extract and Replicat processes even without access to the server where Oracle GoldenGate is installed.
3. Receiver Server: It provides the central services to handle all incoming trail files and communicates with the Distribution Server over the network.
4. Distribution Server: A Distribution Server is an application which functions as a networked data distribution agent in support of conveying and processing data and commands in a distributed networked deployment. The Distribution Server distributes one or more trails to one or more destinations and also performs some filtering operations if configured to do so. The Distribution Server is used to set up a relay Path between the source and target deployments.
5. Performance Metrics Server: It collects and stores performance data related to a GoldenGate deployment. Enables us to monitor performance metrics using a web application and use the data to tune deployments for maximizing performance.
Admin Client: The Admin Client is a command line utility (similar to the classic GGSCI utility). It uses the REST API published by the Microservices Architecture(MA) Servers to accomplish control and configuration tasks in an Oracle GoldenGate deployment.
Download Oracle GoldenGate 220.127.116.11.0 Microservices from OTN.
Install Oracle GoldenGate 18.104.22.168.0 Microservices
The Microservices Architecture for Oracle GoldenGate 12c (22.214.171.124) installation with an Oracle Database is done as below:
- Install the Oracle GoldenGate MA.
- Set the necessary environment variables.
- Deploy an Oracle GoldenGate instance using the Configuration Assistant.
The Microservices Architecture is installed using the Oracle Universal Installer (OUI). OUI is a graphic installation program that prompts you for the input required to install the Oracle GoldenGate binaries and working files, and set the database environment in which Oracle GoldenGate will operate. Alternatively, use a command line silent installation using OUI.
The installer registers the Oracle GoldenGate home directory with the central inventory that is associated with the selected database. The inventory stores information about all Oracle software products installed on a host if the product was installed using OUI.
Click on next to move to next screen and provide the necessary location to install Goldengate.Once all information is provided Goldengate installation will be completed.
Click Close to complete the installation.
Deploy Oracle GoldenGate: Configuration Assistant (OGGCA)
Launch the Configuration Assistant via the oggca.sh script located in the $OGG_HOME/bin directory. Through the Configuration Assistant, we can create the Service Manager as well as configure the deployment.
A single Service Manager can support a number of deployments.
$ export TNS_ADMIN=/u01/app/oracle/product/12.2.0/dbhome_1/network/admin
$ export OGG_HOME=/u01/app/oracle/ogg_ma
$ cd $OGG_HOME/bin
A window will pop up for creating a service manager and register it as a service.
Log in to Service Manager
To start using Oracle GoldenGateMA, we have to connect to Service Manager:
1. Open a web browser and connect to the Service Manager that we created with the Configuration Assistant. The URL is similar to http://localhost:9001, where 9001 is the port where we have deployed our Service Manager instance.
2. Enter the username and password we created during deployment and click Sign In.
Connect to Oracle GoldenGate Service Manager
Upon login, you will find the deployments done for each server as a service.
Use Administration Server to configure and create the Extract and Replicat processes. Also, create the parameter files using Administration Server.
With the help of Distribution, Server define the PUMP process and also define the trail files between sources and targets. Distribution server defines the trail files.
- [Video] Oracle GoldenGate: What Why And How To Learn
- Oracle GoldenGate: Supplemental Logging & Its Importance
- Oracle GoldenGate 12c Webinar: Q/A
- Oracle GoldenGate Training: Lessons Learned & Key Takeaway: Day1 Review
- Oracle GoldenGate Training Day2 Review: Processes & DML Replication: Lessons Learned & Key Takeaway
- Oracle GoldenGate 12c: Troubleshooting using LogDump Utility
- Getting Started with Oracle GoldenGate Microservices Architecture