Purpose

This tutorial will show you how to create and configure the Oracle Data Integrator (ODI) repository with the Oracle Repository Creation Utility (RCU).

Time to Complete

The tutorial will take about fifteen minutes to complete.

Background

You should be familiar with how to install and configure ODI on premises. You can find most of that information on the web in the ODI home page, documentation, and in Oracle Learning Library (OLL) tutorials such as ODI Getting Started.

Scenario

ODI can run on Windows or Linux, can be managed with a web-based Console or standalone Studio GUI, with or without WebLogic Server (WLS). It can use agents deployed in Standalone, Collocated, and Java Enterprise Edition (JEE) mode. This tutorial will assume Linux for both the client workstation and server, managed by the Weblogic Administration Console, with WLS installed as JCS, and the agents deployed in JEE mode.

The topology of the domain you create can vary, depending upon how many virtual machines and how many Managed Servers you provision as part of your Java Cloud Service subscription.

Note — Only the Enterprise Installation is supported on ODI Cloud Service.

Context

This tutorial assumes a single node JCS deployment.

What Do You Need?

You will need to be familiar with the Oracle Java Cloud Service. If you are not then it is strongly recommended that you run through the Getting Started with Oracle Java Cloud Service tutorial before attempting this one.

Make sure you are familiar with the prerequisites required for Oracle Java Cloud Service on OCI.

The instructions in this tutorial assume that you have performed all of these tasks:

1. Ensure that you have subscriptions for Oracle Storage, Oracle Cloud Infrastructure (OCI) Database, Oracle Virtual Cloud Network, and Oracle Java Cloud Service environments.

   For more information, see Signing Up for Oracle Cloud Infrastructure.

2. Create the VM public and private keys.

   The VM public key is used by the new instance's VM for authentication when you connect to it using an SSH client. When you connect, you must provide the private key that matches the public key.

   When creating an OCI Database instance and Java Cloud Service (JCS) instance you need to specify the public key. You generate an SSH public/private key pair using a standard SSH key generation tool. For more information, see Creating SSH Keys for Use with Oracle Cloud Services in the Oracle Learning Library.

3. Configure an OCI Database instance that meets the Java Cloud Service deployment requirements, including adding a specific policy so that the database appears on the Oracle Java Cloud Service web console as an infrastructure schema database choice.

   For instructions, see:

   • Create an Oracle Cloud Infrastructure Database in the Administering Oracle Java Cloud Service guide.
   • Overview of the Database Service in the Oracle Cloud Infrastructure documentation.

Note: When creating the OCI Database instance to use with the Oracle Java Cloud Service, make sure you have created a policy to permit Oracle Platform Services to create instances in your VCN. Keep the policy current. The policy should include:

• Allow service PSM to inspect vcns in compartment
• Allow service PSM to use subnets in compartment
• Allow service PSM to use vnics in compartment
• Allow service PSM to manage security-lists in compartment
• Allow service PSM to manage all-resources in compartment
Set up the credentials to provide access to the object storage bucket, so that you can select Automatic Backup as the backup option for the database.

While performing all of these tasks, be sure to note the user name and passwords you enter; you will need them later while provisioning or performing administration tasks.

If you are doing this just as a proof-of-concept, it is easier to make all of the passwords the same. In a production environment, you should not use shared passwords.

You will need the Compartment Name, Database Instance Name, PDB Name, and the Administrator user name and password. You will need to have generated a token to use as a password for back up and recovery.

You will need to locate the user prefix of your database before moving on to the next section. Once you have located the prefix then note it down.

The database prefix is located in the JDBC setting file for your server domain. Use the more command to examine the mds-owsm-jdbc.xml file using the following form:

more /u01/data/domains/server_domain/config/jdbc/mds-owsm-jdbc.xml

where the server_domain is the name assiged to your provisioned weblogic server. In this example, our server domain is called MyJCSODI_domain, so the command would be:

more /u01/data/domains/MyJCSODI_domain/config/jdbc/mds-owsm-jdbc.xml

The terminal window will display the file, which will look similar to this:

<name>mds-owsm</name>
  <jdbc-driver-params>
    <url>jdbc:oracle:thin:@connect_string</url>
    <driver-name>oracle.jdbc.OracleDriver</driver-name>
    <properties>
      <property>
        <name>user</name>
        <value>SP435951274_MDS</value>
      </property>
      <property>
        <name>oracle.net.CONNECT_TIMEOUT</name>
        <value>120000</value>
      </property>
      <property>
        <name>SendStreamAsBlob</name>
        <value>true</value>
      </property>
    </properties>
    <password-encrypted></password-encrypted>
  </jdbc-driver-params>
  <jdbc-connection-pool-params>
    <initial-capacity>0</initial-capacity>
    <connection-creation-retry-frequency-seconds>10</connection-creation-retry-frequency-seconds>
    <test-frequency-seconds>300</test-frequency-seconds>
    <test-connections-on-reserve>true</test-connections-on-reserve>
    <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
    <seconds-to-trust-an-idle-pool-connection>0</seconds-to-trust-an-idle-pool-connection>
  </jdbc-connection-pool-params>
  <jdbc-data-source-params>
    <jndi-name>jdbc/mds/owsm</jndi-name>
    <global-transactions-protocol>None</global-transactions-protocol>
  </jdbc-data-source-params>
</jdbc-data-source>
							

Where connect_string in the URL line represents the database connect string.

You will find the prefix under the user property. (All the characters before the underscore). Also make a note of the URL to connect to the database.

This section describes how to use the Repository Creation Utility (RCU) to create the required Oracle Data Integrator schemas.

1. Run the following commands to start the Repository Creation Utility (RCU) and create the ODI schema:

   cd /u01/app/oracle/middleware/oracle_common/bin
   ./rcu

   Click Next when the opening screen is displayed.

   

2. On the Create Repository panel, accept the defaults and click Next.

   

3. You must use the Database you seleted when creating you ODI Cloud Service instance. Remember, it cannot be ATP or ADW. The database details you define here will be designated as the supervisor database:

   Field	Description
   Database Type	At the time of writing, only Oracle is supported for the repository.
   Connection String Format	Select the appropriate radio button if you want to supply the connection parameters individually or as a connection string.
   Connect String	Populate with the connection string for your database. This field is active if you selected the Connection String radio button.
   Host Name	This is the instance name of main Oracle database you attached to your Java Cloud instance. This field is active if you selected the Connection Parameters radio button.
   Port	The designated port the database instance communicates through. For Oracle databases this is usually port 1521. This field is active if you selected the Connection Parameters radio button.
   Service Name	The external name of the service can be found in the service details page of your Oracle Java Cloud instance. This field is active if you selected the Connection Parameters radio button. For more information, click here.
   Username	The system administrator user name of the database.
   Password	The database administrator password.
   Role	This will be SYSDBA and will be selected automatically when you set the Username to SYS.

   To get the dbhost:dbport/dbservice details, review the DBaaS properties. When you have filled in the details click Next

   

4. The Repository Creation Utility will check the entries by connecting to the specified database. When the checks have been completed click OK

   

5. Click the Select existing prefix. Select the correct user prefix from the drop down list. It should match the prefix you found in the previous section from the datasource in the Weblogic Administrator Console. Select Oracle Data Integrator component. Click Next.

   

6. The Repository Creation Utility will display a message window while it is checking prerequisites for creating the database. Press OK when it has finished.

   

7. Enter a new password for schema users.For a proof-of-concept, you can use the same passwords for all schemas. In a production environment, you might not want to do that. Note that RCU has different password complexity rules than the VM images, in particular about special characters. Click Next when you have entered and confirmed the password

   

8. On this page you will enter details for the ODI master and work repositories in the database you attached to your Oracle Java Cloud instance.

   Custom Variable	Value
   Supervisor password	The password of the SUPERVISOR user.
   Work Repository Name	Use the default name WORKREP.
   Work Repository Password	The password for the work repository.

   NOTE: Make a note of the Supervisor password. It will be required for step 23 of the next section, “Updating the Java Cloud Service Domain”

   

9. The default tablespaces are fine, just click Next.

   

10. You will now receive a warning stating that the RCU is about to create any missing table spaces. Press Ok to continue.

    

11. The Repository Creation Utility will now proceed to create the tablespaces. Press OK when it's finished.

    

12. Make a note of the Service Name and the Schema Owner; you will need them when are running the ODI Studio later on in this tutorial. When you have noted them down, click Create to continue.

    

    

13. On the Summary screen, click Close.

    

You now have the tablespaces and schemas needed to support ODI Repositories in the DCS.

• Configuring the Domain for the Java EE Agent, part of Oracle Fusion Middleware Installing and Configuring Oracle Data Integrator documentation.
• Oracle Data Integrator 12c: Getting Started Series on Oracle Learning Library (OLL).
• Oracle WebLogic Server 12c: Administration I, the root of all WLS (and therefore JCS) training. Includes Training on Demand (ToD), Instructor-Led Training (ILT), and Live Virtual Class (LVC) formats.
• Leveraging On-Premises Licenses in the Oracle Public Cloud. This document will tell you which middleware products can be used in conjunction with the Oracle Java Cloud Service.
• Oracle® Fusion Middleware Developer's Guide for the Oracle Data Integrator. This document will tell you how to get started with the Oracle Data Integrator.
• Installing Oracle Data Integrator on the Java Cloud Service
• Updating the Java Cloud Service Domain
• Using Oracle Data Integrator to Test Your Domain
• Provisioning Oracle Data Integrator on a Clustered Oracle Java Cloud Service