Provisioning a Clustered Oracle Java Cloud Service for Oracle Data Integrator

Purpose

This tutorial provides instructions for provisioning a clustered Oracle Java Cloud Service domain prior to installing and configuring Oracle Data Integrator Cloud Service on it.

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

Time to Complete

Approximately 8 hours

Background

ODI can run on Windows or Linux, can be managed with a web-based Console or stand-alone 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. Oracle Java Cloud Service enables you to use an Oracle WebLogic Server domain and set up your ODI environment without worrying about the infrastructure or platform components. All Oracle Java Cloud Service instances are preconfigured to use your Oracle Database Cloud Service instance and an object storage container that you create in Oracle Storage Cloud Service.

Oracle Java Cloud Service provides a platform to develop and deploy business applications in the cloud. Oracle Java Cloud Service provides instant access to a cloud environment with Oracle WebLogic Server, integrated security, and database access.

It is assumed that you created a domain that contains an Administration Server and a cluster of two Managed Servers. The cluster is deployed across two Oracle Java Cloud Service virtual machines. A similar topology is shown in a diagram and described in detail in About the Deployment Topology of Virtual Machines in Using Oracle Java Cloud Service. Your actual topology may differ.

Context

This tutorial assumes a two 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.

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 Database, and Oracle Java Cloud Service environments.
   For more information, see Getting Started with Oracle Cloud.
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 a Database Cloud Service (DBaaS) 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 Oracle Cloud database instance that meets the Java Cloud Service deployment requirements.
   For instructions, see Creating a Customized Database Deployment in the Oracle Help Center.
   Note: When creating the Oracle Database Cloud Service instance to use with the Oracle Java Cloud Service, make sure you select Both Cloud Storage and Block Storage as the backup option for the database.
   Make sure the ora_p2_dblistener network access rule is enabled once the DBaaS instance is created. See Enabling Access to a Port in the Oracle Database Cloud Service documentation for additional details.

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

When you created your Java Cloud Service instance, you were provided with details about the database required for the Oracle Java Cloud Service instance. To update the Oracle Java Cloud Service domain for Oracle Data Integrator, you must connect to the same database and install the required ODI schemas.
To verify the details of the Database, see Accessing the Oracle Database Cloud Service Console in Using Oracle Database Cloud Service (Database as a Service).

Note down your Public IP and Connect String, you will need them both later. Your address and Descriptor will be different, but of the same format.

Make sure you have enabled access to port 1521 for SQL*Net. See here in the documentation for more the steps to follow.

You will create a new clustered Oracle Java Cloud instance that is linked to your database. This provision will also include the ODI installation software as part of its virtual machine setup.

1. Log on to your Oracle Cloud service and select Java from the main services menu.
2. From the Oracle Java Cloud Instances page, click the Create Instance button. From the drop down list select Java. You will now be taken to the Create Service page.

   

3. On the first page you will fill out the service details:
   • Instance Name — This is the unique name you will assign to your instance.
   • Description — This is optional text you can use to describe the service.
   • Notification Email — This is optional. You can enter an email address for alerts and notifications.
   • Tags — This is optional. Select your tags from the drop-down list.
   • Service Level — From the dropdown, select Oracle Java Cloud Service Fusion Middleware - Oracle Data Integrator.
   • Software Edition — Select Enterprise Edition
   • Metering Frequency — Select Monthly from the dropdown.
   
   Press Next when you have completed your entries.

   

4. The instance details page is where you fill in the parameters for your new instance. Click the Advanced button and then populate the form as described in the following table:

   Parameter	Description
   WebLogic Configuration
   WebLogic Clusters	Click the Edit icon. In the Manage Clusters dialog box, leave all the parameter values at the default values, except for Server Count and Compute Shape.
   Compute shape	Select OC5 - 4 OCPU, 30 GB RAM
   Server Count	Set to 2, so you can load balance
   Domain Partitions	Since we're not interested in using partitions, leave it as 0
   Enable access to Administration Consoles	Select this.
   Deploy Sample Application	This is not necessary for the OBE, but you can select it if you want.
   WebLogic Access
   SSH Public Key	You will need to supply a public SSH key for accessing the service securely. You can generate one using a third-party utility, or you can have the service create one for you. Press the Edit to create tke key or supply one of your own.
   Local Administrative Username	Assign an administrator user name for the Weblogic server
   Password	Assign a password for the Weblogic administrator
   Load Balancer
   Provision Local Load Balancer	Select Yes.
   Compute Shape	Select OC3 - 1.0 OCPU, 7.5GB RAM
   Add Another Active OTD Node	Leave it unselected
   Load Balancer Policy	Leave it as Least Connection Count
   Database Configuration
   Database Instance Name	Select in the drop down list the database you want to use to store the ODI repository.
   PDB Name	Leave as the default.
   Administrator Username	Enter the database cloud service administrator user name, usually sys.
   Password	Enter the database cloud service administrator password.
   Add Application Schema	Leave as No Application Schema added.
   Backup and Recovery Configuration
   Backup Destination	Select Both Remote and Disk Storage from the drop down list.
   Cloud Storage Container	Enter the URL for your cloud storage container.
   Username	Enter the user name for your cloud storage container.
   Password	Enter the password for the above user name.
   Create Cloud Storage Container	Leave unchecked as the cloud storage contiainer already exists.

   
   When you have entered all the details, click Next

   

   

5. On the service creation confirmation page, click Create

   

6. After the service has been provisioned, you will be returned to the Oracle Java Cloud services page. Ensure the new service has been added to the list.

Now you can connect to the Administration Server using SSH.

• Configuring the Domain for the Java EE Agent, part of Oracle Fusion Middleware Installing and Configuring Oracle Data Integrator documentation.
• Oracle Data Integrator Cloud Service: 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.