Oracle GoldenGate Microservices Architecture has been introduced in Oracle GoldenGate version 12.3. A kind of architecture mainly designed on the perspective of Cloud operations. So, the older one is now called as Classic Architecture.
As we all aware that, Oracle GoldenGate Classic Extract for Oracle Database is already de-supported from OGG version 18c and now from OGG 21c, Oracle GoldenGate Classic Architecture itself got deprecated and may be de-supported and unavailable in future releases.
So, Oracle recommends the customers to move to Microservices architecture.
To know more about OGG Microservices Architecture, please check the below link,
On each new release, Oracle has enhanced the Microservices architecture and there are bunch of enhancements in OGG 21c.
In this article, I would be explaining about the Installation and Configuration of Oracle GoldenGate 21c Microservices Architecture.
I have downloaded the binary and unzipped in the below location.
Before installing OGG 21c MA, you need to create three directories which are below,
Why you need the above three directories? What is the need of it?
/u04/app/ogg/ogg21c_ma is OGG_HOME
/u04/app/ogg/ogg21c_sm is Service Manager Home
/u04/app/ogg/ogg21c_deploy is Deployment Home
Now, navigate to the directory where binary is stored and run the runInstaller file to start the installation of OGG.
One of the new enhancement or feature of Oracle GoldenGate 21c is, you don’t need to specify or select Database version for which the OGG is going to get installed. There would be no option at all. Oracle GoldenGate uses a single or unified build. The OGG build itself has the latest Oracle Database client libraries in it.
Choose software location. This is OGG HOME /u04/app/ogg/ogg21c_ma
Save a response file if required and then click Install
When it is successfully Installed, you will see the following
Oracle GoldenGate for Microservices is installed now. If you want to see the logs for the installation, you can get it from below location,
Understanding the installed binaries
Files under the bin directory,
Deploying OGG Microservices
Setting the Environment Variables
Under the bin directory, we need to run the oggca.sh which takes us to the Deployment screen.
Configure Service Manager. The location of Service Manager is /u04/app/ogg/ogg21c_sm
If you want to register as a service check the box Register Service Manager as a system service/daemon
Click on Add new deployment
Give a name to deployment and software home will be OGG HOME.
In this screen, by default the “Customize directories” is checked. You can provide your own location for configuration files, parameter files etc., If you want GG to take care of it, then just uncheck it.
Provide the Deployment Home. In our case it is /u04/app/ogg/ogg21c_deploy
Set the environment variables if not already set.
Set the username and password for Service Manager and Services.
By default, SSL is enabled. This is to create a secured deployment. Uncheck the boxes to create unsecured deployment. But, if you are going to replicat data from this unsecured deployment to a secured deployment, then you need to check the second check box. All three cases are shown below, you can select it accordingly.
As we are going with Unsecured deployment, we have unchecked all.
If you are going to send or replicat data to a secured deployment, then check the below,
Choose the administration server port. If you click on Distribution port, the rest will be automatically set.
Provide Schema name to add it in the GLOBALS file.
Save the response file, if required. Review the summary once before clicking the finish button.
Once you click on the finish button, the deployment creation starts and at the end, it will ask us to run the servicemanager.sh script as root.
The configuration of Deployment is completed.
As we have registered the Service Manager as daemon, it will be started automatically. Check if it is running,
Check if other services are running.
Login to the Service Manager GUI. Provide the username and password.
Once you login to the Service Manager, you can see the other services running. Here Service Manager is just a watch dog.
Administration Service is where we can create Extract and Replicat processes. Login to the Administration server.
Distribution Service is where we configure the data push. Where the data needs to be replicated? To which Target.
Receiver Service – Configuration for receiving the data from Distribution Service.
Performance Metric Service is a real time monitoring of all OGG processes configured.
Hope the article was helpful. Cheers 🙂