1. Using Oracle Data Integrator on Oracle Cloud Marketplace
  2. Getting Started with Oracle Cloud Marketplace

1 Getting Started with Oracle Cloud Marketplace

Oracle Data Integrator on Oracle Cloud Marketplace is a product offering that enables customers to quickly set up and run Oracle Data Integrator (ODI) on Oracle Cloud and it provides a fully unified solution for building, deploying, and managing complex data warehouses or as part of data- centric architectures in a SOA or business intelligence environment. In addition, it combines all the elements of data integration - data movement, data synchronization, data quality, data management, and data services - to ensure that information is timely, accurate, and consistent across complex systems.

It contains the following sections:

Note:

Refer to Launching Your First Linux Instance documentation before creating the ODI instance.

Launching an Oracle Data Integrator Instance

Perform the following steps to create an instance of Oracle Data Integrator running on Oracle Cloud Infrastructure (OCI).
  1. After finding Oracle Data Integrator on Oracle Cloud Marketplace, click Get App.
  2. Select the OCI region in which you wish to install ODI, and click Launch Image.
  3. Log in to your OCI account.
  4. Click Launch Instance.
  5. Select the latest version of the image from the drop-down list.
  6. Select the compartment where you wish to install Oracle Data Integrator.
  7. Review and accept the Oracle Terms of Use.
  8. Click Launch Instance.

OCI Configuration

On the Create Compute Instance page, specify the following:
  1. In the Name Your Instance text box, enter your choice of name. For example- odi1
  2. From the Select an Availability Domain for your Instance drop-down, choose an availability domain.
  3. In the Choose an operating system or image source, you can see the name of the OCI Console Marketplace image: Oracle Data Integrator.
  4. For Choose Instance Type option, select Virtual Machine.
  5. For Choose Instance Shape option, you can see a default shape, such as VM.Standard2.1 shape.

    Note:

    To use ODI, select a shape with a minimum of 2 OCPUs.
  6. For Configure Boot Volume option, accept the default volume size.
  7. For Add SSH Key option, choose either of the following options:
    • Select Choose SSH key file option, to specify the file containing your SSH public key that was generated previously.
    • Select Paste SSH keys option and paste the SSH public key content in the text field provided, using the content of the public key that was generated previously.
  8. For Configure Networking option:
    • From the Virtual cloud network compartment drop-down list, select the compartment where your VCN has been setup.
    • From the Virtual cloud network drop-down list, choose your VCN.
    • For Subnet compartment option, specify the compartment containing the subnet that you wish to use.
    • For Subnet option, specify the subnet you wish to use (you need not change this normally from the default one, when you select the Subnet compartment ).

    Note:

    If the VM is associated with a public subnet and you wish to assign a public IP address, click the link Show Advanced Options, choose the Networking tab, and then select the Assign public IP address check box.
  9. Click Create.
When the instance gets created (provisioned), it appears in the instance list. To view full details about it, including IP addresses, click the instance name in the displayed instance list.

Configuring ODI for Autonomous Data Warehouse (Optional)

If you aim to use an Autonomous Data Warehouse (ADW) or Autonomous Transaction Processing (ATP) in this tenancy as a part of your ODI transformations, you can use the ADW/ATP Dataserver setup UI to quickly setup this connection in ODI. An ODI Oracle Dataserver is created with all the credentials necessary for the connection. If your instance is newly created, wait for few minutes for the server to start functioning.

When the created ODI instance is fully provisioned and running, you can launch the Oracle ADW/ATP Dataserver setup UI by accessing the URL http://<ipaddress>:8080/odi.

In the above URL, IP address refers to the DNS hostname or IP address, if connecting to the instance externally. If connecting to the instance within the Virtual Cloud Network (VCN), you can use the Internal FQDN (fully qualified domain name), which is displayed on the OCI Console once the instance has been provisioned. For such internal connections, you can copy and paste this to your browser window and append or setup to get to the ODI ADW/ATP Dataserver setup page.

To list ADW/ATP instances in the ADW/ATP Instance drop-down and configure ADW/ATP Dataserver in ODI repository follow the below steps:
  • Create a dynamic group to include matching rules for instances in a specified compartment. For example 
    ALL {instance.compartment.id = 'ocid1.compartment.oc1..aaaaaaaabgr34tpuanpvq6xfb667nsmy2jz45zj6dexojhxdsv4mjayem3cq'}
  • Navigate to Identity -> Policies -> Create Policy to create policy statements as specified below :

    If you set policy at:

    • ODI compartment level, then all ADW/ATP instances from the compartment where ODI instance is created are listed.

      For example - To List ADW/ATP instances only from the ODI instance compartment, you have to setup the following policy:

      Create dynamic group like: ALL {instance.compartment.id = 'ocid1.compartment.oc1..aaaaaaaabgr34tpuanpvq6xfb667nsmy2jz45zj6dexojhxdsv4mjayem3cq'}
Allow dynamic-group odi_group to inspect autonomous-database-family in compartment odi
Allow dynamic-group odi_group to read autonomous-database-family in compartment odi
Allow dynamic-group odi_group to inspect compartments in compartment odi
    • ODI tenant level, then all ADW/ATP instances from all the compartments of the tenancy are listed.

      For example - To list ADW/ATP instances from all the compartments of tenancy, you have to setup the following policy:

      Create dynamic group like: ALL {instance.compartment.id = 'ocid1.compartment.oc1..aaaaaaaabgr34tpuanpvq6xfb667nsmy2jz45zj6dexojhxdsv4mjayem3cq'}
Allow dynamic-group odi_group to inspect autonomous-database-family in tenancy
Allow dynamic-group odi_group to read autonomous-database-family in tenancy
Allow dynamic-group odi_group to inspect compartments in tenancy
  • If the policies are not created previously during ODI Instance creation, then create the policies (as mentioned above) and restart the jettyodi.service before launching the ADW/ATP Dataserver UI.

Refer to Troubleshooting ODI on OCI, to know how to restart the jettyodi.service.

To create an ODI Oracle Dataserver connecting to an ADW/ATP instance,

Provide the following details in the ADW/ATP Instance Details interface:

Description of adw_dataserver.png follows
Description of the illustration adw_dataserver.png
  1. From the ADW/ATP Instance drop-down list, select the required ADW/ATP instance.

    The ADW/ATP instances <CompartmentName-ADW/ATP InstanceName> are listed.When you select an instance, in the backend, the ADW/ATP dataserver is created in the format ADW/ATP Instance Name + "-" + RandomNuber.

  2. In the User Name and Password fields, provide the ADW/ATP user credentials.
  3. From the ADW/ATP Service drop-down list, select the connection details.
  4. Click Configure.

This creates an Oracle Dataserver for the ADW/ATP instance in the ODI repository.

You can create multiple Dataservers for the same ADW/ATP instance without considering ADW/ATP service profiles (High, Low or Medium).

Note:

Make sure you provide correct ADW user credentials while creating the ADW Dataserver. If you provide wrong user credentials you may not be able to connect to the newly created Dataserver. However, you can update the ADW/ATP user credentials, if needed, from ODI studio once you create the ADW/ATP Dataserver.