Before You Begin

This tutorial shows you how to patch Oracle Data Integrator (ODI) Studio in an Oracle Compute VM to use with repositories hosted in Data Integration Platform Cloud (DIPC).

Background

You may find the need to run ODI Studio in Oracle Public Cloud on compute instances in order to support larger, more diverse development teams. To use ODI Studio with repositories hosted in a Data Integration Platform Cloud instance, you first have to patch your ODI Studio, and then modify a few configuration files.

What Do You Need?

To perform the steps in this tutorial, you'll need:

• An Oracle Cloud subscription with instances provisioned for Data Integration Platform Cloud and Oracle Cloud Infrastructure Compute Classic (Linux with GUI desktop or Windows)
• Networking/Access rules configured that allow connectivity:
• From your Compute instance to your Oracle Database Cloud Service (DBCS) instance where the DIPC repositories are hosted
• From your Compute instance to your DIPC VM and ODI agent port
• An installation of ODI Studio 12.2.1.2.6 on your Compute instance VM. See Installing the Oracle Data Integrator Software.

NOTE: Oracle Single Sign-On from Oracle Public Cloud is disabled by default. To enable access to Oracle Technology Network (OTN) to download software from your Compute instance, you have to add the following to your hosts file:

209.17.4.8 login.oracle.com

Patch ODI Studio

ODI Studio requires a patch and post-patch configuration to connect to DIPC ODI repositories.

1. From the Compute instance where ODI Studio is installed, sign in to Oracle Support.
2. In the Search field, enter 27299170, and then click Global Search.



3. Under Recommended Links, select Oracle Data Integrator Studio for Data Integration Platform Cloud.



4. Click Download.



5. In the File Download dialog, click p27299170_122121_Generic.zip, and then save the file to your machine.

   

6. If ODI Studio is running, close it, and then delete the System 12.2.1.2.6 folder before applying the patch.
• For Windows, go to %APPDATA%\odi, and then delete the System 12.2.1.2.6 folder.
• For Linux, go to ~/.odi, and then delete the system12.2.1.2.6 folder.

cd ~/.odi
rm -R system12.2.1.2.6

7. Unzip the file, and then apply the patch:
• For Linux:
• Set the environment variable, ORACLE_HOME, to your ODI home location:

setenv ORACLE_HOME path_to_ODI_home

• Change directories to the patch location:

cd patch_location

• Run the patch

$ORACLE_HOME/OPatch/opatch apply

• For Windows:
• Right-click My Computer and select Properties.
• Click Advanced system settings and then click Environment Variables in the System Properties dialog.
• In the Environment Variables dialog, click New for System variables.
• In the New System Variable dialog, enter ORACLE_HOME for Variable Name, and the path to ODI for Variable value, then click OK.
• Open a cmd window as administrator.
• List the OPatch inventory as:

%ORACLE_HOME%/OPatch/opatch lsinventory

• Apply the patch as:

cd unzipped_patch_directory
%ORACLE_HOME%/OPatch/opatch apply

8. Start ODI Studio.
9. Open the About Oracle Data Integrator Studio 12c dialog and verify that the build number is ODI_12.2.1.2.8CLOUD_GENERIC_171029.2316.

Obtain Data Integration Platform Cloud Configuration Files

ODI Studio requires a few configuration files from your DIPC instance to enable authentication through Oracle Identity Cloud Service (IDCS).

1. SSH to your DIPC instance. See Connect to ODI Studio with VNC Server.
2. Open a terminal window and set user to Oracle:

sudo su oracle

3. Find and change directories to the location of your DIPC configuration files:

cd "$(find /u01/data/domains/*/config/fmwconfig -name jps-config-jse.xml -printf "%h")"

4. Zip the files to /tmp/odi_dipc_config.zip.

zip /tmp/odi_dipc_config.zip jps-config-jse.xml bootstrap system-jazn-data.xml audit-store.xml -r

5. (Optional) Verify the contents of the zip:

unzip -l /tmp/odi_dipc_config.zip



6. Download the /tmp/odi_dipc_config.zip file and copy it to the Compute VM running ODI Studio.

Configure ODI Studio to Connect to Data Integration Platform Cloud

You have to configure ODI Studio to use external authentication (in this case, Identity Cloud Service) to connect to your DIPC instance. After you've copied the odi_dipc_config.zip to your Compute VM, do the following:

1. Unzip the files to:
• For Linux: ~/.odi/oracledi
• For Windows: %APPDATA%/odi/oracledi

NOTE: If the location does not exist, start ODI Studio, and then close it. Starting ODI creates the locations listed above.

1. Navigate to your ODI installation directory (Install_Directory/odi/studio/bin).
2. Open odi.conf in a text editor and add the following line:

AddVMOption -Doracle.security.jps.config=[DIRECTORY_PATH_TO_JPS-CONFIG-JSE.XML]\jps-config-jse.xml

3. Save your changes.
4. Start ODI Studio.
5. Click Connect to Repository...
6. Follow the steps in Connecting to ODI Studio with VNC Server: Connecting to the ODI Repository to determine the ODI repository username for the Login screen.

NOTE: If you don't have access to the DBCS instance using it's HOSTNAME, you can add a value to your hosts file, so the hostname is resolved to the public IP address. Alternatively, you can use the public or private IP addresses depending on your Cloud network configuration. If you use the IP address, you also have to edit the jps-config-jse.xml file and replace the hostname with the IP address in any jdbc:oracle:thin entry.

7. Click OK.

You're not connected to your DIPC instance's ODI repository. The same configuration can be used to connect to any DIPC instance within the same identity domain.

NOTE: Once patched, this instance of ODI Studio can't connect to a non-DIPC ODI repository. This means you won't be able to connect to an on-premises ODI respository, for example.

If you have any issues with connectivity, see our troubleshooting guide.

Want to Learn More?

• Getting a Data Integration Platform Cloud (DIPC) Trial Instance
• Connecting to ODI Studio with VNC Server
• Using Loading Knowledge Modules on both On-Premises and Cloud Computing
• Using Check Knowledge Modules on both On-Premises and Cloud Computing