Purpose

This tutorial will show you how to update the Oracle Java Cloud Service domain for use with Oracle Data Integrator which you have installed and configured on it.

Time to Complete

The tutorial will take about 15 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.

Locating Your Database Details

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.

Before you begin updating the Java Cloud Service Domain, use the WebLogic Administration Console to shutdown all Managed Servers and the Administration Server.

1. Access the Administration Server Console by using the following link: http://admin_server_host:admin_server_port/console.

   

2. In the Domain Structure, expand [+] Environment and click Servers. Click the Control tab. Select the managed server (not the adminserver), and click Shutdown > Force Shutdown Now.

   Click Yes to continue. Wait a minute.

   

3. On the same panel, select the adminserver and shut it down in the same way. This also kills the Console.

   Click Yes.

   

   Just ignore the web browser for the moment.

4. To update your domain, use the Configuration Wizard to extend (update) the Java Cloud Service domain with ODI. Open a terminal session and enter the following commmands:
   cd /u01/app/oracle/middleware/oracle_common/common/bin
   ./config.sh

5. In the Update Domain form, select Update an existing domain. In the Domain Location, select the following WebLogic domain directory. The domain_name will automatically point to the default domain created when provisioning this JCS instance: u01/data/domains/domain_name. Click Next to continue on to the next screen.

   

6. In the Templates form, do the following:

   1. Select Update Domain Using Product Templates.
   2. Select the following items (selecting one will cause others to be selected with green checks):
      • Oracle Data Integrator - Agent
      • Oracle Data Integrator - Agent Libraries
      • Oracle Data Integrator SDK Shared Library Template
      • Oracle Data Integrator - Console
      • Oracle Data Integrator – Standalone Collocated Agent
      • Oracle Enterprise Manager Plugin for ODI
      The following products should already be selected, and greyed out and in italics. They were selected when you created the domain in your Java Cloud Service instance:
      • Basic WebLogic Server Domain
      • Oracle Enterprise Manager
      • Oracle WSM Policy Manager
      • Oracle JRF
      • WebLogic Coherence Cluster Extension

   Click Next.

   

7. The next screen is the for configuring the database type that the Repository Creation Utility requires for internal use. Again, the installer can fill in the details for you.

   Click Get RCU Configuration, then press Next

   

8. On the Datasources form, click the checkbox next to your ODI repositories configuration details. The installer will fill in the rest of the details for you. Then click Next

   

9. The JDBC Test screen is used to make sure that your database connections are working correctly. Select your database connection and then press Test Selected Connections. When the test has completed, press Next

   

10. In the Credentials form, enter the ODI Supervisor username and password for the SUPERVISOR key. (The password for the supervisor should be the variable you entered in the Repository Creation Utility section). Then add a new domain key.

    1. Click Add to add a new credential.
    2. In Key Name, enter the name of this domain as the key. This is the domain created for the JCS.
    3. In Username and Password, provide the Administrator user's Username and case-sensitive Password.
    4. In Store Name, select oracle.odi.credmap from the pull-down.

    Click Next.

    

11. In the Advanced Configuration form, select Topology, System Components and Deployments and Services. On many of the panels you will just accept the defaults.

    

12. In the Managed Servers form, update the required managed servers.

    1. To avoid targeting related libraries and applications to the default ODI server instead of the ODI cluster, delete the default ODI server from the list (you don't physically delete it) by selecting ODI_server1 and click Delete.
    2. By default, the remaining managed server will be pre-populated. You can either rename it or use it as it is. For the purpose of this documentation, the Managed Server has been left with the default entry, however select Enable SSL if it is unchecked.

    Click Next.

    

13. In the Clusters form, just note the Cluster Name. It will be the first eight letters of your domain name (which is the same as the first eight letters of your JCS instance name) and the suffix of _cluster. WARNING: If you try to change the Cluster Name, it appears to work but will generate a Coherence error later, do not change the cluster name. Click Next.

    

14. Leave the Server Templates settings as they are and click the Next.

    

15. Leave the Dynamic Servers settings as they are and click the Next.

    

16. In the Assign Servers to Clusters form, ensure that the servers are assigned to the cluster. Click Next

    

17. In the Coherence Clusters form, accept the defaults and click Next.

    

18. In the Machines form, click the Unix Machine tab to verify that it is populated. Give the machine a suitable name. Leave all other fields at their default values. Click Next.

    

19. In the Assign Servers to Machines form, ensure that the servers are assigned as shown in the image below. then click Next

    Click Next.

    

20. Leave the Virtual Targets settings as they are and click Next.

    

21. Do not change anything on the Partitions screen. Click Next

    

22. Do not change anything on the System Components page. This screen is used to configure a standalone collocated agent which can be optionally defined in the Topology. Click Next.

    

23. On the ODI Configuration page, set a SUPERVISOR password for Oracle Data Integrator standalone collocated agent. This screen is used to configure a standalone collocated agent which can be optionally defined in the Topology.

    

24. Do not change anything on the Assign System Components screen. Click Next

    

25. The ODI applications are deployed to the cluster. Check that they have been deployed correctly. On the right side under Targets, confirm that you can see odiconsole and oraclediagent under your cluster > Application

    

    By default, the ODI libraries are under the Admin Server. Move them into the cluster and out of Admin Server (these are two separate steps).

    1. In the Deployments Targeting form, on the left side under Deployments > Library, select oracle.odi-agent#2.0@12.2.1.2.6 and oracle.odi-sdk#2.0@12.2.1.2.6.
    2. On the right side under Targets, select the cluster name (your cluster name will be different).
    3. Click the middle > to move the items from the left to the right. They will go in alphabetically under Library.

    Do not click Next yet.

    Last you move the Libraries out of the Admin Server:

    1. On the right side under Targets, under Server > domain_adminserver > Library (your adminserver name will be different), select oracle.odi-agent#2.0@12.2.1.2.6 and oracle.odi-sdk#2.0@12.2.1.2.6.
    2. Click the middle < to move the items from the right. They don't actually go to the left, they just go away from the right.

    Now click Next.

26. Confirm that odiMasterRepository and odiWorkRepository are in the right side under Targets/cluster/JDBC/JDBC System Resource.

    

27. In the Configuration Summary form, leave the defaults and click Update.

    

    You can safely ignore the warning about No system component instance.

28. Click Next once the domain is configured, then click Finish.

    

    

You have successfully updated the JCS domain to support ODI JEE Agents. Now you can create agents in the master repository.

• 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.
• Using Oracle Data Integrator to Test Your Domain
• Provisioning Oracle Data Integrator on a Clustered Oracle Java Cloud Service