Скачать или смотреть Installation and Configuring Servce Manager in Oracle Goldengate Microservices

This session is Day 2 of ongoing Microservices training batch:

For Training and consulting requirement for Oracle Goldengate, Pls do fill out contact information form using below link:
https://lnkd.in/gC7pfn2
Also u can directly reach out to me via below methods:
1. Email @[email protected]
2. Call/whatsapp@+14168715708
3. DM@   / ashishagarwalag  

In the session 2 of our Oracle Goldengate Microservices training, We discussed about below:

1. Download of MSA binaries can be done thru OTN.
2. We have a source DB and a target DB. One service manager will be running on each database. Service manager is a watchdog for all the services. Admin server, Matric server and distribution server will be running on source while admin server, matric server and receiver server will be running on target.
3. Under admin server we have extract process which is writing the data to trail files and distribution server sends the data over TCP/IP to receiver server and receiver server writes it to the trail files. Replicat process reads the data from trail files and writes it to the target database.
4. Before proceeding with installation u need to define location where to install. You may install GG in:
a. Separate mount point:
b. Existing mount point
5. Which user to choose to install: Oracle or other user(ggadmin) -oinstall
6. To consider how much space u need for installation, Understand the requirement. Do Research and design
7. Below are the options available to Install GG 21c:
GUI Installation
Silent Installation –

8. Prior to installation of MSA, u need to create 3 directories:

a. Goldengate Home (ogg123_ma)
b. Service Manager home(ogg123_sm)
c. Deployment Home(ogg123_deploy)

9. We have a source DB and a target DB. One service manager will be running on each database. Service manager is a watchdog for all the services. Admin server, Matric server and distribution server will be running on source while admin server, matric server and receiver server will be running on target.

10. Under admin server we have extract process which is writing the data to trail files and distribution server sends the data over TCP/IP to receiver server and receiver server writes it to the trail files. Replicat process reads the data from trail files and writes it to the target database.
11. How to create a service manager?
a. oggca.sh script present under ogg123_ma/bin. Create a new service manager with the option of register service manager as system service daemon. Here you have to provide the hostname and port number.
b. Admin server, Metric server, distribution service and service manager are all the part of deployment. Service manager can be only one however we can have multiple deployments.
c. While creating the the service manager we have to provide deployment name like DEP1 and here you can customize the related directories or you can choose the default ones.
d. It is also important to provide TNS admin to set the environment variables and also provide administrator username and password.
e. After this step we will choose security options. Now we will create administration server, distribution server ,receiver server and performance server. For all these services will provide an open port for each service to run on.
f. Now in next page provide default schema and this schema will become the part of our GLOBALS parameter file.
g. At this stage you can save the response file. Response files are platform independent and can be used for silent installation in any other environment. The next step is to run register service manager as deamon.
h. Registerservicemanager.sh file as a root user because earlier we opted to create service manager as system service daemon.
i. Installation is complete here.
9. To access to service manager you can access local machine or you can reach from remote machine http://111.222.33.444 :7820 (for example)
10. Service manager password informations are stored in /OGG_sm/var/lib/credentials and information regarding administration server and distribution server are stored under /OGG_deploy/var/lib/credentials.
12. Service manager related directories will be under OGG123_SM
13. Deployment related directories will be under OGG123_DEPLOY