Classic VS Microservices (MA)
In Oracle GoldenGate 12.3, we have two architectures available for deploying GoldenGate
- Classic Architecture
- Microservices Architecture
- Below Classic Architecture
In this architecture, the primary access into the Oracle GoldenGate enviornmentis is through the GoldenGate Service Command Interface (GGSCI). After logging into GGSCI, you can interact and administrate the associated processes, i.e. Manager, Extract (Capture), Data Pump, and Replicat (Apply). The Collectors are pretty much hidden on the target systems, but they are there; just not seen through GGSCI. In this architecture, you data is replicated over TCP/IP between the Data Pump process and Collectors using local and remote trail files.
The downside to this architecture is that, in order to administer the environment, you have to physically login to the server where Oracle GoldenGate is running. With this requirement, many organizations were restrictive on who had access to the server and often caused a debate over who were truely the owners of Oracle GoldenGate.
Althought the Classic Architecture of Oracle GoldenGate has been a bedrock of replication for nearly 20 years, we (Oracle) wanted to leverage that bedrock to transform the way we (industries) replicate data today. This lead to the more flexible and super scalable Microservices Architecture. As you may have guessed, “Microservices” is the mechanism that we are suing to provide access to the “RESTful API” end points. By using RESTful APIs, we (Oracle) have taken a huge leap forward in the replication space. We have broken down the limitations we had around administration and access, while at the same time remaining true to the bedrock that is the foundation of Oracle GoldenGate.
Microservices Architecture:
The Microservices Architecture in Oracle GoldenGate is comprised of five main components:
As you will notice there are some traditional components of Oracle GoldenGate missing, while there are still extracts (capture), trail files, and replicats (apply). This is due to being a completely new replication architecture which had many benefits. A few of these benefits are:
- Remote Administration
- SSL Support
- HTML 5 webpages for each service/server
- Additional replication protocols (WSS, WS, UDT, OGG)
- Real-time Performance Metrics
In order to understand the Microservices Architecture, you have to understand what each of the servers (or services) provide within the architecture. So, let’s take a moment and talk about these items starting with the ServiceManager.
- 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.
Install Oracle GoldenGate 12.3.0.1.0 Microservices
The Microservices Architecture for Oracle GoldenGate 12c (12.3.0.1) 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 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
$ ./oggca.sh
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.
Oracle GoldenGate Classic Architecture is deprecated in 21.3
Oracle GoldenGate Classic Architecture for Oracle database and heterogeneous databases DB2 z/OS, MySQL, SQL Server, and PostgreSQL is deprecated and may be desupported and unavailable in a future release. Oracle recommends using the Oracle GoldenGate Microservices Architecture.
Also,
Classic Extract has been desuported. We no longer can create Classic Extract in OGG 21c. Customers extracting from a ADG instance with classic extract will have to change to downstream capture.
CUSEREXIT for Extract is deprecated and will be desupported in future releases.
The RMTTASK parameter is desupported for Oracle GoldenGate Microservices Architecture. The parameter has been deprecated for Classic Architecture and will be desupported for Classsic Architecture in future releases.
No comments:
Post a Comment