JavaScript must be enabled to correctly display this content
Create Stream Analytics resources
To use Stream Analytics in OCI GoldenGate, create a Stream
Analytics deployment and assign connections.
Tip:
Ensure that you review the OCPU management and billing
information for both OCI GoldenGate and Stream Analytics
deployments before you proceed.
Create the Stream Analytics deployment
Before you begin
Before 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.
To create a Stream Analytics deployment in the Oracle Cloud console:
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:
For GoldenGate instance name, enter a name for the
stream analytics instance.
For Credential store, select one of the following:
OCI Identity and Access Management (OCI IAM), to enable users
to log in to the the deployment console using their Oracle Cloud account (single sign
on) in IAM (Identity and Access Management) enabled tenancies.
Note:
Once you select IAM, you won't be able
to switch to GoldenGate when you edit the deployment settings at a later
time.
GoldenGate, for GoldenGate to manage users.
Enter the Administrator username
Select a password secret in your compartment or click Change
compartment to select one in a different compartment. You can also create a
new password secret.
To create a new password secret:
Click Create password secret.
In the Create secret panel, enter a name for the secret, and
optionally, a description.
Select a compartment from the Compartment
dropdown in which to save your secret.
Select a vault in the current compartment, or click Change
compartment to select a vault in a different compartment.
Select an Encryption key.
Note:
Only AES keys, Software
protected keys, and HSM keys are supported. RSA and ECDSA keys are not
supported for GoldenGate password secret keys.
Enter a password 8 to 30 characters in length, containing at least
1 uppercase, 1 lowercase, 1 numeric and 1 special character. The special
characters must not be '$', '^' or '?'.
Confirm the password.
Click Create.
Note:
You can manage GoldenGate
users in the deployment console. Learn more.
Click Create.
Your Stream analytics deployment takes a few minutes to create. Its status changes
to Active when your deployment is ready to use. Ensure that you create and assign
connections to the deployment before you use your deployment.
Supported connections
Learn about what types of connections are supported by OCI GoldenGate Stream Analytics.
OCI GoldenGate Stream Analytics supports the following
source technology types:
You can also create Amazon S3, Azure Data Lake Storage, Coherence, Hadoop File Storage
(HDFS), Ignite, JMS, and MongoDB connections directly within the Stream Analytics
console.
Assign a connection to a
deployment
When you're on the Deployment details page, you can assign connections to the
deployment.
To assign a connection to a deployment:
On the Deployment details page, under Resources, click
Assigned connections.
Click Assign connection.
In the Assign connection dialog, select a connection from the dropdown. If you
want to select a connection from a different compartment, click
Change Compartment.
Click Assign connection.
The selected connection appears in the Assigned connections list. You can also
view and manage this relationship from the Connection details page under
Assigned deployments.