2 Get Started
To get started with Oracle Data Integration Platform Cloud, subscribe to Oracle Cloud, create a Data Integration Platform Cloud instance, add users, and then provide access to your users.
Before You Begin with Oracle Data Integration Platform Cloud
How to Begin with Oracle Data Integration Platform Cloud
Here’s how to get started with free Oracle Data Integration Platform Cloud promotions and subscriptions:
-
Sign up for a free credit promotion or purchase a subscription.
See Requesting and Managing Free Oracle Cloud Promotions or Buying an Oracle Cloud Subscription in Getting Started with Oracle Cloud
-
Access the Oracle Data Integration Platform Cloud service.
To grant access to others:
-
Learn about user accounts and roles.
See Assign Roles for Data Integration Platform Cloud Classic Instances.
-
Create accounts for your users and assign them appropriate privileges and roles.
See Managing Users, User Accounts, and Roles in Getting Started with Oracle Cloud
Access Oracle Data Integration Platform Cloud
You can access Oracle Data Integration Platform Cloud through emails that you receive after subscribing or through the service web console.
To access Oracle Data Integration Platform Cloud:
-
Sign in to your Oracle Cloud account. If this is your first time signning in, refer to the Welcome email you received when you purchased your subscription for more information.
-
Open the navigation menu in the upper left corner, select Platform Services, and then Data Integration Platform or Data Integration Platform Classic, depending on the type of service you have.
-
You can either create a new Data Integration Platform Cloud instance, or if there are instances available, select one to access.
Assign Oracle Data Integration Platform Cloud Roles
This topic only applies to Data Integration Platform Cloud Classic.
Assign Roles for the Data Integration Platform Cloud Classic Service
This topic only applies to Data Integration Platform Cloud Classic.
- DICS_ENTITLEMENT_ADMINISTRATOR: This role enables users to create and delete Data Integration Platform Cloud service instances and perform all tasks available in the Services, Activity and SSH pages of Data Integration Platform Cloud.
- Compute.Compute_Operations: For the Compute service, this role enables users to create Oracle Public Cloud service instances.
- Log in to Oracle Cloud as a user with the IDCS Administrator role.
- From the navigation menu in the upper left corner, select Identity, Federation, and then your Identity Cloud Service provider.
- Select a user, and then click Manage Service Roles.
- Click the menu for DICS, and then select Manage service access.
- Select DICS_ENTITLEMENT_ADMINISTRATOR, and then click Save Role Selections.
- Click the menu for Compute, and then select Manage service access.
- Select Compute.Compute_Operations, and then click Save Role Selections.
- Click Apply Service Role Settings.
Assign Roles for Data Integration Platform Cloud Classic Instances
This topic only applies to Data Integration Platform Cloud Classic.
You can access the following with each Data Integration Platform Cloud instance:
-
Data Integration Platform console, available through the action menu of any Data Integration Platform Cloud instance
-
Oracle Data Integrator console, available through the user menu of Data Integration Platform Cloud console
-
Enterprise Data Quality console (available with Governance edition), available through the user menu of Data Integration Platform Cloud console
-
WebLogic Server console, available through the action menu of any Data Integration Platform Cloud instance
-
Fusion Middleware console, available through the action menu of any Data Integration Platform Cloud instance
The following table lists the instance level roles that you can assign to your users.
Role in Identity Cloud Service | Equivalent ODI Profile | Description | Is Admin? |
---|---|---|---|
Administrator |
Profiles ending in ADMIN |
Service application administrator role |
Yes |
Developer |
DESIGNER (Use in ODI Studio for ELT designs) |
Service application developer role |
No |
User |
OPERATOR (Use in ODI console for job execution and status review) |
Service application user role |
No. For example, this user will not have the Management tab in the ODI console available to them. |
To assign roles to instances:
-
Log in to Oracle Cloud as a user with the IDCS Administrator role.
-
From the navigation menu in the upper left corner, select Identity, Federation, and then your Identity Cloud Service provider.
-
Select a user, and then click Manage Service Roles.
-
Click the menu for DICS, and then select Manage instance access.
-
Select the roles to assign.
-
Click Save Instance Settings, and then Apply Service Role Settings.
For more information, see Manage Security for Service Instances.
Create Instances for Data Integration Platform Cloud
There are several ways that you can create a Data Integration Platform Cloud instance, depending on your requirements and experience level.
Create Data Integration Platform Cloud Instances
This topic does not apply to Data Integration Platform Cloud Classic. It applies only to Data Integration Platform Cloud.
- Log in to Oracle Cloud.
- In the console, open the navigation menu in the upper left corner, and select Platform Services, and then Data Integration Platform.
- On the Instances page, click QuickStarts.
- Select a Data Integration Platform Cloud service edition, and then click Create.
QuickStart Data Integration Platform Cloud Classic Instances
This topic only applies to Data Integration Platform Cloud Classic.
The QuickStart option provisions a Database Cloud Service instance followed by a Data Integration Platform Cloud Classic instance with the following details:
-
Database Cloud Service: Oracle Database 12.1.0.2, Enterprise Edition. 1 PDB, 1 OCPU, 15 GB Memory
-
Data Integration Platform Cloud Classic: Enterprise Edition, 1 OCPU, 15 GB Memory
Each of these instances are configured on one virtual machine. These two instances are configured to see each other and the schemas for the Data Integration Platform Cloud Classic instance are stored in the database instance. Neither of these instances have a backup option.
These instances are typically used for creating sandbox environments or in cases that don't require backup and recovery. The QuickStart templates give you the fastest and easiest way to create a Data Integration Platform Cloud Classic instance. All you need to do is provide an instance name and then click Create.
Note:
QuickStart instances are offered through Oracle Cloud Stack, which is an Oracle Cloud service that allows several Oracle Cloud instances stacked and created together.
QuickStart a user-managed instance:
-
Log in to Oracle Cloud.
-
In the console, open the navigation menu in the upper left corner, select Platform Services, and then Data Integration Platform Classic.
-
On the Data Integration Platform Cloud Classic Instances page, click QuickStarts.
-
On the QuickStarts page, enter a name for your instance in the Instance Name field, and then click Create.
-
In the Confirmation dialog, click Download to download the credential file that you’ll need if you want to access your database and Data Integration Platform Cloud Classic VMs, and then click Create.
-
Click Navigation Menu to access the navigation pane, and then select Cloud Stack.
-
On the Stacks page, confirm that your instance appears in the list.
Allow some time to pass before using your QuickStart instance. When you refresh the page and the Status: Creating Instance no longer appears, you’ll know your instance is ready to use.
Create Data Integration Platform Cloud Classic Instances
This topic only applies to Data Integration Platform Cloud Classic.
Find Your User-Managed Services and Backup Location
This topic only applies to Data Integration Platform Cloud Classic.
- Log in to Oracle Cloud.
- From the navigation menu, select Storage Classic, and then click Account.
- Under Account Information, copy the REST Endpoint URL and paste it into a text editor to use later.
Create an Object Storage Classic Container
This topic only applies to Data Integration Platform Cloud Classic.
Any user with the Service Administrator role can create containers. You should create
at least one container for your account. Containers are similar to a directory
structure but with a key distinction, unlike directories, containers cannot be
nested. By default, all containers are of the standard
storage
class (as opposed to the archive
storage class). You can also
create containers when provisioning an Oracle Database Cloud Service deployment or Data Integration Platform Cloud instance.
Note:
Before you create your first container, make sure that the replication policy has been set for your account. See Selecting a Replication Policy for Your Service Instance
Interface | Resources |
---|---|
Web Console (Not available on Oracle Cloud at Customer) |
|
RESTful API |
|
Java Library |
See |
File Transfer Manager API |
See |
File Transfer Manager CLI |
See Create Container in Command-Line Reference for Oracle Cloud Infrastructure Object Storage Classic. |
To create an archive
container, you must set the X-Storage-Class
header to Archive. For more information, see Creating Archive Containers. (Not available on
Oracle Cloud at Customer)
Creating a Container Using the Web Console
(Not available on Oracle Cloud at Customer)
-
Log in to the Oracle Cloud Infrastructure Object Storage Classic console.
-
Click Create Container.
The Create Container dialog box is displayed.
-
Enter a name for the container.
Note:
Ensure that the container name complies with the input restrictions mentioned in Character Restrictions. -
Select Standard in the Storage Class field.
-
Click Create.
The container is created and displayed in the console.
Creating a Container Using the REST API
cURL Command Syntax
curl -v -X PUT \ -H "X-Auth-Token: token" \ accountURL/containerName
token
is the authentication token obtained earlier from Oracle Cloud Infrastructure Object Storage Classic. See Authenticating Access When Using the REST API.- For the syntax of
accountURL
, see About REST URLs for Oracle Cloud Infrastructure Object Storage Classic Resources. containerName
is the name of the container to be created.Note:
Ensure that the container name complies with the input restrictions mentioned in Character Restrictions.
Note:
When you send a REST API request to Oracle Cloud Infrastructure Object Storage Classic, all non-ASCII characters in container names, object names and metadata values must be URL-encoded. For example, my container
should be encoded as my%20container
, where %20
is the HTML encoding for the space character. Similarly, my Über Container
should be encoded as my%20%C3%9Cber%20Container
, where %20
represents the space character and %C3%9C
is the Ü
character.
HTTP Response Codes
-
Success:
201 Created
-
Failure: See Error Code Reference for Object Storage Classic
cURL Command Example
- Account name:
acme
- REST Endpoint URL:
https://acme.storage.oraclecloud.com/v1/Storage-acme
- REST Enpoint (Permanent) URL:
https://storage-7b16fede61e1417ab83eb52e06f0e365.storage.oraclecloud.com/v1/Storage-7b16fede61e1417ab83eb52e06f0e365
Note:
The REST Enpoint (Permanent) URL is displayed for accounts created after November 2017. - Using the REST Enpoint URL obtained from the REST
Endpoint
field:
curl -v -X PUT \ -H "X-Auth-Token: AUTH_tkb4fdf39c92e9f62cca9b7c196f8b6e6b" \ https://acme.storage.oraclecloud.com/v1/Storage-acme/FirstContainer
The following is an example of the output of this command:
> PUT /v1/myservice-bar/FirstContainer HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 > Host: foo.storage.oraclecloud.com > Accept: */* > X-Auth-Token: AUTH_tkb4fdf39c92e9f62cca9b7c196f8b6e6b > < HTTP/1.1 201 Created < Date: Fri, 06 Mar 2015 10:34:20 GMT < Content-Length: 0 < Content-Type: text/html; charset=UTF-8 < X-Trans-Id: tx23a1084b8c674fdeae8d4-0054f982ac < Cache-Control: no-cache < Pragma: no-cache < Content-Language: en
- Using the Service Permanent REST Endpoint URL from the REST
Endpoint (Permanent)
field:
curl -v -X PUT \ -H "X-Auth-Token: AUTH_tkb4fdf39c92e9f62cca9b7c196f8b6e6b" \ https://storage-7b16fede61e1417ab83eb52e06f0e365.storage.oraclecloud.com/v1/Storage-7b16fede61e1417ab83eb52e06f0e365/FirstContainer
The following is an example of the output of this command:
> PUT /v1/Storage-7b16fede61e1417ab83eb52e06f0e365/FirstContainer HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 > Host: storage-7b16fede61e1417ab83eb52e06f0e365.storage.oraclecloud.com > Accept: */* > X-Auth-Token: AUTH_tkb4fdf39c92e9f62cca9b7c196f8b6e6b > < HTTP/1.1 201 Created < Date: Fri, 06 Mar 2015 10:34:20 GMT < Content-Length: 0 < Content-Type: text/html; charset=UTF-8 < X-Trans-Id: tx23a1084b8c674fdeae8d4-0054f982ac < Cache-Control: no-cache < Pragma: no-cache < Content-Language: en
For informationa bout setting the replication policy in the container, see Selecting a Replication Policy Using the REST API.
For information about getting details of a container, see Getting Container Metadata.
Provision Oracle Database and Exadata Cloud Instances
This topic only applies to Data Integration Platform Cloud Classic.
Create an Oracle Database Cloud Service Instance
This topic only applies to Data Integration Platform Cloud Classic.
Before You Begin
An SSH public/private key pair (Optional)
An SSH public key is used for authentication when you use an SSH client to connect to a compute node associated with the deployment. When you connect, you must provide the private key that matches the public key.
You can have the wizard create a public/private key pair for you, or you can create one beforehand and upload or paste its private key value. If you want to create a key pair beforehand, you can use a standard SSH key generation tool. See Generating a Secure Shell (SSH) Public/Private Key Pair.
After Your Database Deployment Is Created
After your database deployment is created, you should perform the following actions:
-
Update cloud tooling
While the base images used to create Database Cloud Service database deployments are updated regularly, it is possible that even more recent updates to the cloud tooling are available. Therefore, you should check for and apply any updates to the cloud tooling. See Updating the Cloud Tooling on Database Cloud Service.
-
Apply database patches
While the base images used to create Database Cloud Service database deployments are updated regularly, it is possible that a newer patch set update (PSU) or bundle patch (BP) is available. Therefore, you should check for and apply any database patches that are available. See Applying a Patch.
Create an Oracle Database Exadata Cloud Service Instance
This topic only applies to Data Integration Platform Cloud Classic.
You must create an Exadata Cloud Service database deployment that is properly configured for use as a Data Integration Platform Cloud replication target before you create a Data Integration Platform Cloud instance.
Before you can create a database deployment, you must have an active Exadata Cloud Service instance in place.
Note:
If you do not have an active service instance in place, then the Create Service wizard will not show the options required to create a deployment on Exadata Cloud Service.
Review Creating an Exadata Cloud Service Instance
You must complete the following fields when using the wizard.
-
Service level: Oracle Database Exadata Cloud Service.
-
Database release: This selection determines the version of Oracle Grid Infrastructure that is configured.
Database releases Version of Oracle Grid Infrastructure Oracle Database 11g Release 2 or Oracle Database 12c Release 1
Oracle Grid Infrastructure 12c Release 1 is installed and can only be used to support version 11.2 or version 12.1 database deployments. In this case, you cannot later use the Create Service wizard to create a version 12.2 database deployment.
Oracle Database 12c Release 2
Oracle Grid Infrastructure 12c Release 2 is installed and used to support all of your database deployments, including subsequent deployments that use an earlier Oracle Database release version.
If you wish to deploy Oracle Database 12c Release 2 on a system that is already configured with Oracle Grid Infrastructure 12c Release 1, then you must manually upgrade to Oracle Grid Infrastructure 12c Release 2 and manually create the version 12.2 database deployment. For details see My Oracle Support note 2206224.1.
-
Database edition: The only valid option for use with Exadata Cloud Service is Enterprise Edition — Extreme Performance.
Configure the database deployment for use as a replication database by setting the Enable Oracle GoldenGate option on the Service Details page of the wizard.
The target database must be network accessible on the listener port by:
-
Specifically enabling network access to the Oracle Net Listener port. Review Enabling Access to a Compute Node Port.
Note:
If you specifically enable access to the Oracle Net Listener port, ensure that you always use an encrypted Oracle Net connection. Review Using Network Encryption and Integrity.
-
Or you can configure an IPSec VPN. This enables secure connectivity on any port between a customer network and the Oracle Public Cloud. Review Enabling IPSec VPN Access to Exadata Cloud Service.
Once you have created and properly configured an Exadata Cloud Service database deployment for use as a replication target, you can create an Oracle Data Integration Platform Cloud instance that uses it.
When provisioning your Database, you can select any Oracle Database Exadata Cloud Service you already have.
-
You first create the Oracle Database Exadata Cloud Service instance by launching the wizard. The wizard is invoked through the Open Service Console button on the Cloud My Services Dashboard related to the Exadata Cloud Service.
-
Provide all the Instance Details:
Instance Details fields Description Name
The name for your service instance is no longer than 25 characters, starts with a letter, not contains spaces or other special characters and is unique within the identity domain.
Data Center
The data center that will host your Exadata Cloud Service instance.
Plan
A plan is associated with a set of attributes that apply to a service. For Exadata Cloud Service only one plan is available.
Rack size
Select the option that describes the number of compute nodes and Exadata Storage Servers that you have.
Extra number of OCPUs (Cores)
Optionally you can enter a number of additional CPU cores that you want to enable.
Exadata System Name
The Exadata Database Machine environment. This name is also used as the cluster name for the Oracle Grid Infrastructure installation.
Database backups on Exadata Storage (Yes or No)
Check this option to configure the storage to enable local database backups on Exadata storage.
Administrator Details
Provide information about the administrator of your Exadata Database Machine environment
-
Create the Service instance by clicking in the Create Service Instance button.
-
In the Overview you can also review additional information: (like the Service Start Date and the Version).
Note:
When you run the Oracle Database Cloud Service provisioning wizard, always select an Oracle Database Exadata Cloud Service option. This action is to have the Oracle Database software pre-installed on an Oracle Exadata machine. Using this option, Database Service instances are created on available Exadata infrastructure.
-
When configuring your Oracle Database Cloud Service, you select Exadata System for your service instance.
-
Finally, when configuring your Oracle Data Integration Platform Cloud instance, you select the Database Cloud Service that has Exadata.
Follow the steps through the tutorial Get Started with Oracle GoldenGate Cloud Service
To enable Oracle Data Integration Platform Cloud replication, you need to file an SR to whitelist the GGCS IP address so that GGGCS can communicate with the Exadata DB instance with the SQL*Net connection. The SR would typically include the following information:
-
IdentityDomain ID -xxxxxx of the GGCS VM
-
Source Compute instance - GGCS VM IP address
-
Exadata CS SQL*Net Port: 1521
You can find additional Exadata Cloud Service documentation at: Enabling Access to a Compute Node Port
Note:
-
Oracle Data Integration Platform Cloud doesn't support Oracle database 12.2 capture yet.
-
With Exadata CS X6, you can complete the whitelist operation using the UI interface.
Provision and Access an Oracle Data Integration Platform Cloud Classic Service Instance
This topic only applies to Data Integration Platform Cloud Classic.
Create an Oracle Data Integration Platform Cloud Classic Service Instance
This topic only applies to Data Integration Platform Cloud Classic.
To create a Data Integration Platform Cloud Classic service instance, you can either use the Create Service wizard as described here, or you can follow the steps in the Create a Data Integration Platform Cloud Classic instance on Oracle Cloud Infrastructure Classic tutorial.
Before you Begin
When you create a Data Integration Platform Cloud Classic service instance, you provide information about the instance itself and its related resources. Therefore, make sure you have the required information about the following resources available:
-
Your Database Cloud Service instance
-
Your Oracle Cloud Storage container
Create an Oracle Data Integration Platform Cloud Classic Service Instance
To create a new Data Integration Platform Cloud Classic service instance:
- Log in to Oracle Cloud.
-
In the Oracle Cloud Infrastructure console, open the navigation menu in the upper left corner, select Platform Services, and then Data Integration Plaform Classic.
-
Click Create Instance.
-
On the Service page, enter a name and description for the Data Integration Platform Cloud Classic service instance, and provide information about its high-level characteristics.
-
Click Next.
-
On the Service Details page, complete the following sections, and then click Next.
-
Database Configuration
-
Oracle Database Cloud Service Instance Name: Select an available Database Cloud Service instance.
-
PDB Name: Specify the pluggable database name (PDB) associated with the Database Cloud Service instance chosen from the Associated DBAAS Service Name list.
-
Database Administrator Username and Password: Enter the user name and password of the administration account for this Database Cloud Service instance.
-
-
Backup and Recovery Configuration
-
Cloud Storage Container: Enter the object storage location where backups of the service instance must be stored.
Enter the URL of a container in Oracle Cloud Infrastructure Object Storage Classic using the format
rest_endpoint_url/containerName
. You can find the REST endpoint URL of the Oracle Cloud Infrastructure Object Storage Classic service instance in the Oracle Cloud My Services portal; for example,https://acme.storage.oraclecloud.com/v1/MyService-acme/MyContainer
.Note:
If the container that you specify doesn’t exist, then select the Create Cloud Storage Container check box to create the container automatically. -
Cloud Storage Username and Cloud Storage Password: Enter the user name and password of the Oracle Cloud Infrastructure Object Storage Classic service user who created the container you specified earlier. If the container doesn’t exist, then enter the user name of a service administrator.
-
Create Cloud Storage Container: Select this check box to create the container automatically if the container that you specified doesn’t exist.
-
-
Weblogic Server Configuration
-
Compute Shape: Select the compute shape for the Weblogic VMs.
-
SSH Public Key: Specify the Secure Shell (SSH) client public key that’s used for authentication when connecting to a node in your instance.
Click Edit to display the SSH Public Key for VM Access dialog, and then specify the public key using one of the following methods:
-
Select Key file name and use your web browser to select a file on your machine that contains the public key.
-
Select Key value and paste the value of the public key into the text area. Be sure the value doesn’t contain line breaks or end with a line break.
-
Select Create a New Key if you want Oracle to generate a public/private key pair for you.
-
-
Administrator Username and Password: Specify the administration user name and password for Weblogic.
The password:
-
Must start with a letter.
-
Must be between 8 to 30 characters long.
-
Must contain at least one number.
-
Can include any number of dollar signs ($), hash signs (#), or underscores (_).
-
-
-
-
Click Next.
On the Confirmation page, review the information listed. If you’re satisfied with the information, click Create.
Access a Virtual Machine Through a Secure Shell
This topic only applies to Data Integration Platform Cloud Classic.
The SSH protocol uses two keys, a public key and a private key, to provide secure communication between two computers. You can use any SSH utility to generate a public/private key pair and later, to log in to your Oracle Data Integration Platform Cloud instance. For example, you can use PuTTY or you can use OpenSSH.
For Windows you can follow the steps through the tutorial:
Configure Access Rules
This topic only applies to Data Integration Platform Cloud Classic.
To control network access to your Oracle Service instances, you can define access rules. For example, you can create rules that:
-
Enable an Oracle Database node to access multiple ports on the WebLogic Managed Server nodes
-
Enable public Internet access to a specific port on the WebLogic Administration Server node
Data Integration Platform Cloud Classic creates several default rules on a new service instance, such as public access to the WebLogic Administration Server node on port 22 for Secure Shell (SSH). Some of these are system rules, which cannot be disabled.
Make sure you consider the possible security implications before you open ports to external access.
-
Access your service console.
-
For the service that you want to modify, click Manage this Service, and then select Access Rules.
-
On the Access Rules page, click Create Rule.
-
Enter a name in the Rule Name field.
-
(Optional) Enter a description in the Description field.
-
In the Source field, select a source for the rule. The available source options depend on the topology of your service instance and may include:
- PUBLIC-INTERNET: Any host on the Internet
- OTD_ADMIN_HOST: The first Oracle Traffic Director (OTD) load balancer node
- OTD_OTD_SERVER: All OTD load balancer nodes
- WLS_ADMIN_HOST: The WebLogic Administration Server node
- WLS_ADMIN: All WebLogic Administration Server nodes
- WLS_MS: All WebLogic Server nodes
DBaaS:Name:DB
: The database service named Name- <custom>: A custom list of addresses from which traffic should be allowed. In the field that appears below this one, enter a comma-separated list of subnets (in CIDR format, such as 10.11.12.13/24) or IPv4 addresses for which you want to permit access).
-
In the Destination field, select the destination node within this service instance.
- WSL_ADMIN: The WebLogic Administration Server node
- WLS_ADMIN_HOST: The WebLogic Administration Server node
- WLS_MS: All WebLogic Server nodes
- OTD_ADMIN_HOST: The Oracle Traffic Director (OTD) Administration Server node
- OTD_OTD_SERVER: All Oracle Traffic Director (OTD) Manager Server nodes
-
In the Destination Port(s) field, enter the port or range of ports through which the source will be granted access to the destination.
-
In the Protocol field, select the TCP or UDP transport for this rule.
-
Click Create.
To return to either the Service page or the Overview page for the select service instance, click the locator links at the top of the page.
Note:
OTD has the same admin/managed server architecture as WebLogic Server. You can configure zero, one, or two load balancer nodes. The first load balancer node (OTD_ADMIN_HOST) runs the OTD admin server and managed server. The 2nd LB node (OTD_OTD_SERVER) runs an OTD managed server. OTD components can only be used as source, to allow traffic from them to other components.
To create custom access rules, refer to the Create Access Rules tutorial.
Configure VPN as a Service (VPNaaS)
This topic only applies to Data Integration Platform Cloud Classic.
Note:
When you configure VPNaaS, you must provision Data Integration Platform Cloud Classic to use IP Network instead of a Shared Network.For details on how to configure IP Networks, see Configuring IP Networks.
Before you begin, you should already have your on-premises Oracle Database installed and configured, and instances for DIPC already provisioned on the IP network. For details on provisioning Data Integration Platform Cloud Classic instances, see Create an Oracle Data Integration Platform Cloud Classic Service Instance; or you can follow the steps in this tutorial, Create a Data Integration Platform Cloud Classic instance on Oracle Cloud Infrastructure Classic.
Create Public DVLBR and Mapping IP Networks
This topic only applies to Data Integration Platform Cloud Classic.
Create a Child VLBR
-
Log in to the Oracle Cloud Instrastructure Cloud Classic console.
-
In the navigation menu, select Compute Classic.
-
Log in to the Compute Classic console, and then click the Network tab.
-
In the left navigation pane, click Load Balancers and then select Create Load Balancer.
-
Enter a Name, an IPNetwork, and a Parent Load Balancer.
-
Click Create.
After you create this child-load-balancer, you can create the JLS instances using this IPNetwork or you can use the IPNetwork (Primary) used in creating VLBR.
Finding IPNetwork used in creating the DVLBR
If you’ve already created a DVLBR ( Parent VLBR) pointing to an IPNetwork, you can find it from the Compute Classic console.
-
Click the Network tab, and from the left navigation pane, click IP Networks.
All the IP Networks are listed in the right pane.
-
Click the Load Balancer, and then select Overview to find the details.
Updating IPExchange
If a DVLBR already exists, select the IPNetwork that you pointed to, to create a parent VLBR ( INTERNET_FACING). Update the IPExchange to point to an IPExchange used in the Parent VLBR IPNetwork.
Note:
The same applies for all other IPNetworks in the same account that you want to use to create any JLS ( DIPC)-based services.- Click the Network tab, and from the left navigation pane, click IP Exchanges.
- From the right pane, click Create IPExchange.
- Enter a Name and a Description, and click Create.
- Go back to the left navigation pane, click IP Networks, and then select Create IP Network
- Select the IPExchange from the drop-down and click Create.
Set up VPNaaS
This topic only applies to Data Integration Platform Cloud Classic.
OPC – IP Network and DIPC Instance Check
This topic only applies to Data Integration Platform Cloud Classic.
OPC – Provision a VPN Connection under VPNaaS
This topic only applies to Data Integration Platform Cloud Classic.
Related Topics
Create and Configure On-Premises Third-Party VPN Device
This topic only applies to Data Integration Platform Cloud Classic.
To configure pfSense VPN appliance Phase 1 settings:
-
Click the Tunnels tab, and edit the Phase 1 General Information.
-
Enter the Authentication and Algorithms details.
-
For Advanced Options, select the Responder Only and the Dead Peer Detection options.
-
Click Save.
To configure pfSense VPN appliance phase 2 settings:
-
Click the Tunnels tab, and edit the Phase 2 General Information.
-
Enter the SA/Key Exchange details.
-
Set the Advanced Configuration details, and click Save.
Note:
Make sure that the Shared Key for the on-premises VPN device and the Oracle Public Cloud's VPNaaS match.
OPC and On-Premises – Verify Tunnel Status is Up
This topic only applies to Data Integration Platform Cloud Classic.
- Navigate to the Compute Classic console, and click the Network tab.
- From the left navigation pane, click IP Networks.
- Click VPN, then under VPNaaS, click VPN Connections.
- In the right pane, check if the Tunnel status is Up for VPNaaS on the OPC side.
- To check the on-premises side, go to the pfSense VPN Status page, and see if the status is Established.
OPC and On-Premises – Verify VPN Connection
This topic only applies to Data Integration Platform Cloud Classic.
To verify if there is a VPN connection, do one of the following:
-
From the on-premises database, log in to the DIPC Server, by using its private IP address.
-
From the DIPC server, log in to the on-premises database server. Then verify the connection from the Data Integration Platform Cloud Classic VM to the on-premises database server listener port by using the
netcat
command,nc
.
Configure DIPC Connection to On-Premises Database Server as a Data Source
This topic only applies to Data Integration Platform Cloud Classic.
The Connection that you create for an on-premises database can now be used by any job to perform data synchronization, integration, or validation.
Understand the Information on the Home page
The Home page provides you with quick access to Agents, Connections, Tasks, and Jobs, as well as a summary of active components in your Data Integration Platform Cloud instance.
At the top of the page, the menu icon displays the navigation pane. Here, you can access the Catalog, Monitor, Agents, Policies, and Admin pages. Click Home to return to the Home page at any time. When you click the Notifications icon, you’re brought to the Notifications page, where you can review a list of system messages and alerts. Click the user icon to access context-sensitive help for any page that you’re on, tutorials, videos, information about Data Integration Platform Cloud, or sign out of your session.
There are three sections to the Home page, the Welcome carousel, the Summary, and the Getting Started section.
Welcome
When you log in to Data Integration Platform Cloud, you're brought to the Home page. If it's your first time, click Watch Video to tour the interface. Afterwards, you can download an Agent, or create Connections and Tasks from the tiles in the carousel.
Summary
The Summary section displays recent and active Tasks, Jobs, Connections, and Agents in your Data Integration Platform Cloud instance. Click the title of the tile to see a filtered view of the Catalog, which displays a full list of Tasks, Jobs, or Connections, or the Agents page. Click the name of any component, Task, Jobs, Connections, or Agents, in a tile to access its page and view its metadata.
Getting Started
The Getting Started section enables you to download an Agent, or create new Tasks or other system components. Here's a list of what you can download or create:
- Add Data to Data Lake
Store and organize large volumes of data from different sources in its raw format into the Oracle Data Lake for later use.
For more information, see Add Data to Data Lake.
- Agents
Download a DIPC Agent that orchestrates data integration tasks on your data source.
For more information, see Set up an Agent.
- Connection
Create connections to define the source and target data sources.
For more information, see Create a Connection.
- Data Lake
Create a repository on the Oracle Cloud to store a vast amount of data from different sources in its raw data.
For more information, see Create a Data Lake.
- Data Preparation
Harvest data from a data source, perform a variety of transformations to organize and cleanse your data, and then write the resultant data to a new data entity.
For more information, see Prepare Data.
- Execution Environment
Use Spark Execution on Big Data Cloud or YARN to run the Add Data to Data Lake task.
For more information, see Set Up an Execution Environment.
- ODI Execution
Invoke an existing Oracle Data Integrator (ODI) Studio Scenario to perform bulk data transformations.
For more information, see ODI Execution.
- Policy
Create policies to stay informed about your job activities and to schedule jobs. Set conditions by using predefined, job-related metrics. You'll get notifications when the conditions are met.
For more information, see What is a Policy?
- Replicate Data
Capture new transactions in your source data source and replicate them to a target data source.
For more information, see Replicate Data.
- Synchronize Data
Copy data from a source data source to target data source, and then keep both data sources in sync. Use filter rules to include or exclude specific data entities in your job. The synchronize data task captures any change in the source schema and replicates it in the target and vice versa.
For more information, see Synchronize Data.