Deployments let you create and organize Oracle Cloud Infrastructure GoldenGate
resources, and enables the OCI GoldenGate deployment console, where you can add and manage data
replication processes. You can create deployments for Oracle Database, Big Data, Microsoft
SQL Server, MySQL, and PostgreSQL sources or targets.
Before you beginBefore you create a
deployment, review the following requirements:
- If you enable public deployment console access in Step 10, OCI GoldenGate creates a load balancer in your tenancy VCN on your behalf. To
ensure successful creation of the deployment and load balancer, you must have the
appropriate policies, quotas, and limits in place.
- In Oracle Cloud Infrastructure Identity and Access Management (OCI IAM)
enabled tenancies, Step 16 requires you to select the credential store you'll use to log
in to the deployment console.
- Depending on your source and target technology types, you may need more
than one deployment. If you're not sure how many deployments you need for your solution,
see Example topologies for details.
- In the Console navigation menu, click Oracle Database, and then
select GoldenGate.
- On the Deployments page, click Create deployment.
- In the Create deployment panel, enter a name and optionally, a description.
- From the Compartment dropdown, select a compartment in which to create the
deployment.
- Select one of the following options:
- Production: Sets up a deployment with
recommended defaults for a production environment. The minimum number of OCPUs is 4,
with auto-scaling enabled.
- Development or testing: Sets up a deployment
with recommended defaults for a development or testing environment. The minimum number
of OCPUs is 1.
- For OCPU count enter the number of
Oracle Compute units (OCPUs) to use.
- (Optional) Select Auto scaling.
Note
Auto scaling enables OCI GoldenGate to scale up to three times the number of OCPUs you specify for
OCPU Count, up to 24 OCPUs. For example, if you specify your OCPU Count as 2 and enable
Auto Scaling, then your deployment can scale up to 6 OCPUs. If you specify your OCPU
Count as 20 and enable Auto Scaling, OCI GoldenGate can only scale up to 24
OCPUs.
- From the Subnet in <Compartment> dropdown, select the
subnet to which a private endpoint is created from the OCI GoldenGate service
tenancy. This ensures that the deployment is always available over this subnet, as long as
the policies for this subnet allow access. The private endpoint is only used to access the
deployment console, and doesn't provide access to other resources in the subnet.
To select a subnet in a different compartment, click Change
compartment.
Note
You can only select a private subnet
when creating a deployment.
- Select a license type.
- (Optional) Click Show advanced options for network options and
to add tags.
- In the Network tab,
- Select Enable GoldenGate console public
access to include a public endpoint in addition to a private
endpoint, and allow public access to the deployment console for users. If
selected, OCI GoldenGate creates a load balancer in your tenancy to
create a public IP. Select a subnet in the same VCN as this deployment in which to
create the load balancer.
Note
The
load balancer is a resource that comes with an additional cost. You can manage
this resource, but ensure that you don't delete the load balancer while your
deployment is still in use.
Learn more about load balancer
pricing.
-
Select Customize endpoint to provide a private fully
qualified domain name (FQDN) prefix that you'll use to access the private
service console URL. You can also optionally upload an SSL/TLS certificate
(.pem) and its corresponding private key, however, password protected
certificates are not supported.
- It's your responsibility to ensure that the FQDN resolves to the
deployment's private IP address in the subnet you previously selected.
- If the deployment is public, it's your responsibility to ensure
that the FQDN publicly resolves to the deployment's public IP address.
A self-signed certificate is generated for you, if you don't
provide one.
Note
Your SSL certificate must meet the following requirements:
- It's common name should match the deployment's FQDN. If it
doesn't, you'll encounter warnings when you access the deployment
console.
- It must be signed using a strong hashing algorithm. arcfour,
arcfour128, arcfour256, none algorithm types are not permitted.
- It must not be expired.
- It's maximum validity should not exceed 13 months.
- It must not be a self-signed certificate.
If you encounter "Invalid Private Key" errors, you can
check the correctness of the key using the following OpenSSL commands. Run
this command against the
certificate:
openssl x509 --noout --modulus --in <cert>.pem |openssl md5
Then run this command on the private
key:
openssl rsa --noout --modulus --in <key>.pem |openssl md5
The output of the two commands should return the same
md5
value. If it doesn't, then the certificate and private
key don't match.
- In the Maintenance tab:
- Select Customize maintenance window to
define the start of the maintenance window to upgrade the deployment.
- (Optional) For Major release auto-upgrade period in days,
enter the number of days, between 0 and 365.
- (Optional) For Bundle release auto-upgrade period in days,
enter the number of days, between 0 and 180 days.
- (Optional) For Security patch auto-upgrade period in days,
enter the number of days, between 0 and 14 days.
- Select Enable interim release auto-upgrade, and, optionally,
enter the number of days.
- In the Tags tab, add tags to help track the resources within
your tenancy. Click + Additional tag to add more tags. Learn more about tagging.
- Click Next.
- For Deployment type, select Data replication.
- From the Select a technology dropdown, select one of the following technology
types:
- Oracle Database
- Big Data
- MySQL
- PostgreSQL
- Microsoft SQL Server
See what's supported to learn which
databases and technologies you can use as OCI GoldenGate sources and
targets.
- For Version, the latest version is automatically selected. Click
Change version to select a different version.
- For GoldenGate instance name, enter the name that the deployment
will assign to the GoldenGate deployment instance upon creation.
- For Credential store, select one of the following:
- Click Create.
After the deployment is created and becomes Active, it starts automatically.
You can then select Launch console in the deployment's Actions
(three dots) menu on the Deployments page, or click Launch console on
the deployment details page to access the OCI GoldenGate deployment console.
Ensure that you create and assign connections to use with your deployment.