GoldenGate Microservices Architecture (MA) allows you to configure and manage data replication over homogeneous or heterogeneous database environments using RESTful services. These microservices can be accessed using various interfaces including a web interface, command line interface, REST API, or any other service that allows accessing REST-based microservices.
Image Reference:-https://docs.oracle.com/en/middleware/goldengate/core/21.3/coredoc/overview-oracle-goldengate-microservices-architecture.html#GUID-8079B9E7-3925-46AD-9C45-172C5A248798
Now, when we install Oracle Golden Gate microservices from OCI Marketplace, it basically creates default wallet files under /u02/deployment. The two files are ewallet.p12 and cwallet.sso. When we install the GG microservices, it doesn't prompt for any wallet password and thus we can't open the wallet.
To create a secure distribution path, in order to send the redo logs from existing extract to the target(example here-Golden Gate for Big data), the wallet password is required. We can get the password from:-
For the client wallet password, you will find a file init-ogg-deployment.py under /usr/local/bin. The client wallet password is in the file if you have not changed it after the instance is created.
For V19c GG Marketplace Microservices Architecture, that information is in /usr/local/bin/common.py
For V21c GG Marketplace Microservices Architecture, that information is in /usr/local/bin/init-ogg-deployment.py. However, for v21c, you don’t need to manipulate the wallet directly under shell. You can do this from the Service Manager WebUI, which is recommended practice.
Reference:-https://docs.oracle.com/en/middleware/goldengate/core/19.1/oggmp/provisioning-oracle-goldengate-microservices-oci-marketplace.html#GUID-ED0DD115-6AB2-424F-8DE4-7DE145B5992C
