4.1 Getting Started with Oracle GoldenGate for Distributed Applications and Analytics

You can use Oracle GoldenGate for Distributed Applications and Analytics Microservices Architecture (MA) to configure and manage your data replication using an HTML user interface. The Oracle GoldenGate for Distributed Applications and Analytics (GG for DAA) MA comprises the following components: Service Manager, Administration Service, Distribution Service, Receiver Service, Performance Metrics Service, and Admin Client.

For more information about the Oracle GoldenGate MA components, see Components of Oracle GoldenGate Microservices Architecture.

This topic lists the various tasks that you need to preform to set up GG for DAA integrations with cloud storage, message streaming, cloud warehouse, NoSQL and caching technologies.

• Working With Deployments
  Adding deployments is the first task in the process of setting up a data replication platform. Deployments are managed from the Service Manager.
• About Oracle GoldenGate Properties Files
  
• Using the Admin Client
  Admin Client is a command line utility (similar to the classic GGSCI utility). It uses the REST API published by the Microservices Servers to accomplish control and configuration tasks in an Oracle GoldenGate deployment.
• Controlling Oracle GoldenGate (Microservices Architecture) Processes
  The standard way to control Oracle GoldenGate (MA) processes is through the Admin Client.

4.1.1 Working With Deployments

Adding deployments is the first task in the process of setting up a data replication platform. Deployments are managed from the Service Manager.

For more information about installing and deploying Oracle GoldenGate for Distributed Applications and Analytics (GG for DAA), see Installing Oracle GoldenGate for Distributed Applications and Analytics and Analytics.

After you log into your Service Manager instance, you can create deployments or edit existing ones. You can work with multiple deployments from a single Service Manager instance. For more information about working with deployments, see Working with Service Manager in Oracle GoldenGate Microservices Architecture Documentation guide.

4.1.2 About Oracle GoldenGate Properties Files

There are two Oracle GoldenGate properties files required to run the Oracle GoldenGate Java Deliver user exit (alternatively called the Oracle GoldenGate Java Adapter). It is the Oracle GoldenGate Java Delivery that hosts Java integrations including the Oracle GoldenGate for Distributed Applications and Analytics (GG for DAA) integrations. A Replicat properties file is required in order to run either process. The required naming convention for the Replicat file name is the process_name.prm. The exit syntax in the Replicat properties file provides the name and location of the Java Adapter properties file. It is the Java Adapter properties file that contains the configuration properties for the Java adapter include GG for DAA integrations. The Replicat and Java Adapters properties files are required to run GG for DAA integrations.

Alternatively the Java Adapters properties can be resolved using the default syntax, process_name.properties. It you use the default naming for the Java Adapter properties file then the name of the Java Adapter properties file can be omitted from the Replicat properties file.

Samples of the properties files for Oracle GoldenGate for Distributed Applications and Analytics (GG for DAA) integrations can be found in the subdirectories of the following directory:

GoldenGate_install_dir/AdapterExamples/big-data

• Parameter Files
  Most of the Oracle GoldenGate functionality is controlled by the parameters specified in parameter files. A parameter file is a plain text file that is read by an associated Oracle GoldenGate process. Oracle GoldenGate uses two types of parameter files: a GLOBALS file and runtime parameter files.

4.1.2.1 Parameter Files

Most of the Oracle GoldenGate functionality is controlled by the parameters specified in parameter files. A parameter file is a plain text file that is read by an associated Oracle GoldenGate process. Oracle GoldenGate uses two types of parameter files: a GLOBALS file and runtime parameter files.

For more information about working with Parameter Files, see Using Oracle GoldenGate Parameter Files in the Administering Oracle GoldenGate guide.

4.1.3 Using the Admin Client

Admin Client is a command line utility (similar to the classic GGSCI utility). It uses the REST API published by the Microservices Servers to accomplish control and configuration tasks in an Oracle GoldenGate deployment.

For more information about working with the Admin Client, see Using the Admin Clientin the Administering Oracle GoldenGate guide.

4.1.4 Controlling Oracle GoldenGate (Microservices Architecture) Processes

The standard way to control Oracle GoldenGate (MA) processes is through the Admin Client.

Typically, the first time that Oracle GoldenGate processes are started in a production setting is during the initial synchronization process (also called instantiation process). However, you need to stop and start the processes at various points as needed to perform maintenance, upgrades, troubleshooting, or other tasks. For more information, see Controlling Oracle GoldenGate Processes in the Administering Oracle GoldenGate guide.