Provisioning Oracle Data Integrator Cloud Service


Options



Before You Begin

Purpose

This tutorial will show you how to install and configure Oracle Data Integrator (ODI) by provisioning an Oracle Java Cloud instance with the ODI option.

Time to Complete

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

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 Using Oracle Database Cloud Service 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.

Pre-Installation Steps

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.

  1. 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).

    DCS IP info
    Description of this image

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.

Provisioning the Oracle Java Cloud Instance

To start with you will create a new 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. Select Java from the drop-down list.

    Description of this image

  3. On the first page you will fill out the service details:

    • Instance Name — This is the unique name you will assign to your service.

    • 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 when you have completed your entries.

    Description of this image

  4. The instance details page is where you fill in the parameters for your new instance. Click the 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 Compute Shape. Set this to OC5 - 4 OCPU, 30 GB RAM
    Compute shape Shows as OC5 - 4 OCPU, 30 GB RAM
    Server Count Since this is a single server installation, leave it as 1
    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 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 Leave as No.
    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

    Description of this image

    Description of this image

  5. On the instance creation confirmation page, click

    Description of this image

  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.

    Description of this image

    To be able to access WLS console, you need to follow the steps here in the documentation to enable control access in an Oracle Java Cloud Service.

Installing ODI on the Oracle Java Cloud Service

Connecting to the Oracle Java Cloud Service Environment Using SSH

When you create an instance of the Oracle Java Cloud Service, all the Oracle Compute Cloud Service VMs required to support the service are provisioned and configured for you. You can access the services and resources provided by the VMs by logging in to the machine through an SSH tunnel. You'll access the VMs from your local machine by using the ssh command in a UNIX command shell.

  1. To connect to the Oracle Java Cloud Service instance through SSH, you must find the IP address of the Administration Server VM hosting the instance.
    1. Sign in to the My Services application at http://cloud.oracle.com.
    2. In the Oracle Java Cloud Service section, click Java.
    3. On the Oracle Java Cloud Service page, click Open Service Console
    4. On the Oracle Java Cloud Service Console, click the instance.
    5. The public IP address of the Administration Server is available under the Virtual Machines section. Make a note of the IP address.

      Note: You must wait for the instance creation to complete before you can see the IP address.

      Description of this image
  2. Start a Linux terminal shell and run the SSH utility.
    ssh -i path_to_private_key opc@IP_of_JCS_Instance_Admin_Server

    In the preceding command:

    Parameter Description
    path_to_private_key is the path to the SSH private key file that matches the public key used when your instance was created
    IP_of_JCS Instance_Admin_Server is the public IP address of the Admin Server VM in n.n.n.n format.
    opc is the user account.

    For example:

    ssh -i keys/id_rsa opc@10.10.10.10

    You are now logged in as user opc.

  3. Switch to user oracle on the JCS Admin Server VM.
    sudo su oracle
  4. Turn off the lock screen on the JCS Admin server.
    gconftool-2 -s -t bool /apps/gnome-screensaver/lock_enabled false
  5. Start the VNC Server. If prompted for a password, enter one. Make a note of it.
    vncserver -nolisten local -geometry 1680x1050
  6. Open a new local terminal to create an SSH tunnel the VNC server port on the Administration Server VM.
    ssh -i path_to_private_key -L 5901:IP_of_Tunnel_Server:5901 opc@IP_of_Admin_Server -N 

    In the preceding command:

    Parameter Description
    path_to_private_key Path to your private key file.
    IP_of_Tunnel_Server The address of the server through which the tunnel is run.
    IP_of_Admin_Server The destination server (the address of the administration server for your Oracle Java Cloud instance).

    For example:

    ssh -i keys/id_rsa -L  5901:127.0.0.1:5901 opc@10.10.10.10 -N 
  7. To get desktop access for the Oracle Java Cloud Server instance,use the VNC Viewer on your local machine to connect to localhost:5901. You will be prompted for the password you entered in step 4.
  8. vncviewer
    In the Window that opens, enter localhost:5901 and click OK.
    Window for VNC Viewer. Enter the localhost and port
    Description of this image

    Once VNC connects you to the remote machine, you want to turn off the screen saver, otherwise you could find yourself locked out of the remote machine.
    Select System/Preferences/Screensaver menu item. In the resulting Screensaver Preferences dialog box, make sure Activate screensaver when computer is idle is not selected.

    Turn off screen saver
    Description of this image

  9. If you don't manage to turn off the screen saver in time, you will be locked out and the system will prompt you for the (unknown) oracle user password. If this happens, you need to reset the server and log back in.

    If you're not locked out, you can ignore this step.

    1. Using the same terminal session as in step 4, enter the following command to make sure you are the oracle user:
      sudo su oracle
    2. Find the number of the session which is now locked. You can use this number to kill the session. For example:
      ps –ef | grep vnc
      
      oracle 		28596     1  0 16:07 pts/0    00:00:01 /usr/bin/Xvnc :1 -desktop test-w                                  
      ls-1:1 (oracle) -auth /u01/app/oracle/tools/paas/state/homes/oracle/.Xauthority                                   
      -geometry 1680x1050 -rfbwait 30000 -rfbauth /u01/app/oracle/tools/paas/state/homes/oracle/.vnc/passwd -rfbport 5901 
      -fp catalogue:/etc/X11/fontpath.d -pn -nolisten local
      oracle   28601 28600  0 16:07 pts/0    00:00:00 vncconfig -iconic
      In this example, the number we want is 28596. The session number returned when you run the command most likely will be different.
    3. Kill the session.
      kill -9 28596
    4. Delete the server temp files and folders relating to this session. Answer yes when prompted.
      rm –R /tmp/.X*
    5. Start the vncserver again.
      vncserver -nolisten local -geometry 1680x1050
    6. Repeat steps 5 and 6, but with a different port number. The simplest thing to do, is increase the port number by one. Previously the port number was given as 5901, so this time use 5902. Make sure the port is free, before you use it. Open a new local terminal to create an SSH tunnel the VNC server port on the Administration Server VM.
      ssh -i path_to_private_key -L 5902:IP_of_Tunnel_Server:5902 opc@IP_of_Admin_Server -N 
      To get desktop access for the Oracle Java Cloud Server instance, use the VNC Viewer on your local machine to connect to localhost:5902. You will be prompted for the password you entered in step 4.

Installing Oracle Data Integrator

As with all things Linux, directories are case sensitive.

Note: Since Oracle WebLogic Server is already installed in your Java Cloud Service instance, there is no need to install the Fusion Middleware Infrastructure. It is already there.

  1. From the vncviewer, open a terminal session and navigate to the /tmp directory. Check there are no temporary files present. If there are any, delete them using the rm command, so removing any possiblity of running out of disk space whilst installing ODI.

    Then navigate to the /u01/zips/upperstack directory

    cd /u01/zips/upperstack

    Inside the folder you will find the odi installer archive file. You can check by executing the ls command.

  2. Unpack the archive file using the unzipcommand.

    unzip ODI.zip
  3. This will unpack two jar files into the current directory. These files make up the ODI installer. To run the installer. Use the Java command:

    java -jar fmw_12.2.1.2.6_odi_generic.jar

    to initiate the installation.

  4. When prompted, set the Inventory Directory to /u01/app/oraInventory, then click to create the Central Inventory Directory.

    Inventory Directory
    Description of this image

  5. When the Welcome screen opens, click .

    ODI Install welcome screen
    Description of this image

  6. Select Skip Auto Updates and then click

    Auto Updates screen
    Description of this image

  7. For the installation location enter /u01/app/oracle/middleware, then click to check the features that will be installed at this location. Click to move to the next step.

    Set install location screen
    Description of this image

  8. In the Installation Type form, select Enterprise Installation. Click .

    Note – The Standalone Installation is not supported in this configuration. Do not select it.

    Setting the installation type
    Description of this image

  9. Click on the Prerequisite Check screen

    Note – Depending on the configuration of instance, the ODI installer may display a warning stating that the JDK version is not certified. You can ignore the message.

    Prerequisite check
    Description of this image

  10. On the Installation Summary form, click .

    ODI Installation summary
    Description of this image

  11. The Installation Progress screen will show the name and status of each component as it copied and configured. When the operation has completed, click

    Installation progress
    Description of this image

  12. Click on the Installation Complete screen.

    Installation complete
    Description of this image

You have successfully installed the Oracle Data Integrator.

Locating your Database Prefix

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.

  1. Start an SSH terminal session and connect to your Oracle Java Cloud instance.

  2. Switch to the oracle user by executing the following command:

    sudo su oracle
  3. 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
  4. The terminal window will display the file, which will look similar to this:

    <name>mds-owsm</name>
      <jdbc-driver-params>
        <url>jdbc:oracle:thin:@MyJCSODI:1521/PDB1.fmwcert.ucfc2z3a.usdv1.cloud.com</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>
    							

    You will find the prefix under the user property. (All the characters before the underscore).

Creating Oracle Data Integrator Repository using the Repository Creation Utility (RCU)

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 when the opening screen is displayed.

    Repository Creation Utility startup screen
    Description of this image

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

    Create repository
    Description of this image

  3. You must use the Database you seleted when creating you ODI Cloud Service instance. 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.
    Host Name This is the instance name of main Oracle database you attached to your Java Cloud instance.
    Port The designated port the database instance communicates through. For Oracle databases this is usually port 1521.
    Service Name The external name of the service can be found in the service details page of your Oracle Java Cloud instance. 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

    Database connection details
    Description of this image

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

    Database prerequiste checks
    Description of this image

  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 .

    Select components
    Description of this image

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

    Checking RCU prerequisites
    Description of this image

  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 when you have entered and confirmed the password

    Schema passwords
    Description of this image

  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”

    Set custom variables
    Description of this image

  9. The default tablespaces are fine, just click .

    Map tablespaces
    Description of this image

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

    Tablespace creation warning
    Description of this image

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

    Creating table spaces alert
    Description of this image

  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 to continue.

    RCU Summary
    Description of this image

    RCU Creating Tablespaces
    Description of this image

  13. On the Summary screen, click .

    Completion summary
    Description of this image

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

Updating the Java Cloud Service Domain

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.

    WLS Console Login
    Description of this image

  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 to continue. Wait a minute.

    Shutdown Managed
    Description of this image
  3. On the same panel, select the adminserver and shut it down in the same way. This also kills the Console.

    Click .

    Admin Server Shutdown message
    Description of this image

    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 to continue on to the next screen.

    config 1 of 6
    Description of this image

  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 .

    Selecting repository templates
    Description of this image
  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 , then press

    Database configuration type
    Description of this image

  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

    Component data sources
    Description of this image

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

    JDBC test
    Description of this image

  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 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 .

    Supervisor credentials
    Description of this image

  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.

    Advanced configuration
    Description of this image

  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 .
    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 .

    Allocate addresses to managed servers
    Description of this image
  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 .

    Assign ports to clusters
    Description of this image

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

    Server templates
    Description of this image

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

    Description of this image

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

    Assign servers to clusters
    Description of this image

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

    Set up Coherence clusters
    Description of this image

  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 .

    Machine configuration
    Description of this image

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

    Click .

    Assign servers to machines
    Description of this image

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

    Configure virtual targets
    Description of this image

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

    Assign Partitions
    Description of this image

  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 .

    Configure system components
    Description of this image

  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.

    ODI configuration page
    Description of this image
  24. Do not change anything on the Assign System Components screen. Click

    Assign System Components
    Description of this image

  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

    Deployments targeting
    Description of this image

    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 .

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

    Repositories under clusters
    Description of this image

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

    Configuration summary
    Description of this image

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

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

    Configuration progress
    Description of this image

    End of configuration
    Description of this image

You have successfully updated the JCS domain to support ODI JEE Agents.

Creating Agents in the Master Repository Using ODI Studio

If there is no physical agent entry for an agent, then the agent startup will fail when starting the WLS Administration Server.

To create an agent using ODI Studio, see Section 5.3 "Creating an Agent in the Master Repository Using ODI Studio" in Installing and Configuring Oracle Data Integrator.

Note — Running ODI Studio on-premises on your local laptop or desktop is not supported as it may slow down the user interface to the point of being unusable. You should use VNC connected to the JCS instance to run ODI Studio.

  1. Start ODI Studio from the command line by using the following commands:

    cd /u01/app/oracle/middleware/odi/studio
    ./odi.sh
    .

    Studio splash logo
    Description of this image

  2. You will be asked if you would like to import preferences from a previous ODI installation. Click

    Import ODI preferences
    Description of this image

  3. Login to the Repository created by RCU.

    1. Create a Login by clicking on Connect to Repository and then click the green plus.

      Connect to Repo
      Description of this image

    2. Fill in all of the connection information that match the entries you made in the RCU.

      Field Description
      Oracle Data Integrator Connector
      Login Name Choose a suitable login name for the connection.
      User This is the name you picked when creating the tablespaces in the Repository Creation Utility. Click here to return to the RCU section of the tutorial.
      Password The password you created for the SUPERVISOR
      Database Connection (Master Repository)
      User The user name created for the master repository in Repository Creation Utility. You should already have made a note of this value earlier on. Click here to return to the relevant section.
      Password The password for the master repository user.
      Driver List The list contains the JDBC drivers supported by the ODI Studio. Select Oracle JDBC driver.
      Driver Name The name of the JDBC driver will be filled in when you select from the Driver List.
      URL This is the location of the database given as a standard JDBC connection string. You should have a note of the string as shown here.

      Repo Connect Info
      Description of this image

    3. Select Work Repository and click Browse (magnifying glass). to display the Work Repository selection window.

      Select Repo workrep
      Description of this image

    4. Select WORKREP and click .

    5. Click . (If the selection worked, then the Test should work…)

    6. If successful, click .

    7. Enter a Wallet password twice. Click .

      New Wallet Password
      Description of this image

    8. All the information should be saved and pre-populated. Just click and the Designer, Operator, and Topology tabs should appear on the left.

      ODI Login
      Description of this image

  4. Create a Physical Agent. On the Topology tab, expand (plus) Physical Architecture, right-click Agents, and select New Agent.

    Update image

    New Physical Agent
    Description of this image

    Fill in the information for for Oracle Data Integrator J2EE agent:

    • Name — This is unique name given for the agent, and it must match the name of the J2EE agent application running on your server

    • Host — The IP address, or host name, of the server that the J2EE agent is running on.

    • Port — The port of the server that the J2EE agent is running on. This is the same value (9073 in our example) as the listen port set in step 12 of Updating the Java Cloud Service Domain section.

    Physical Agent Definition
    Description of this image

    Click Save (diskette)

  5. Create a Logical Agent. On the Topology tab, expand (plus) Logical Architecture, right-click Agents, and select New Agent.

    New Logical Agent
    Description of this image
  6. For simplicity, keep all the names the same: OracleDIAgent. Click Save (diskette). Close the OracleDIAgent tab.

    Logical Agent Definition
    Description of this image

  7. Optionally, you can repeat steps 4, 5 and 6, but for the standalone collocated agent.

    Create a Physical Agent. On the Topology tab, expand (plus) Physical Architecture, right-click Agents, and select New Agent.

    Update image

    New Physical Agent
    Description of this image

    Fill in the information for for Oracle Data Integrator standalone collocated agent:

    • Name — This is unique name given for the agent, and it must match the name of the standalone collocated agent application running on your server

    • Host — The IP address, or host name, of the server that the standalone collocated agent is running on.

    • Port — This is the same value as the server listen port, 20910, set in step 23 of Updating the Java Cloud Service Domain section.

    Physical Agent Definition
    Description of this image

    Click Save (diskette)

  8. Create a Logical Agent. On the Topology tab, expand (plus) Logical Architecture, right-click Agents, and select New Agent.

    New Logical Agent
    Description of this image
  9. For simplicity, keep all the names the same: OracleDIAgent1. Click Save (diskette). Close the OracleDIAgent1 tab.

    Logical Agent Definition
    Description of this image

You now have a physical and logical agents, but WLS (and therefore the agents) is not started yet, so you cannot test it yet.

Starting the Administration Server

The Administration Server normally does not host any user applications, it simply controls the other Managed Servers. Once the Managed Servers are running, the Administration Server only collects statistics and logs.

Weblogic servers in the cloud environment are usually monitored and controlled by the Node Manager, so it is better to use the Node Manager to restart the Administration Server.

  1. From your vncviewer console, open a new terminal window and run the Weblogic Scripting Tool using the following commands:

    cd /u01/app/oracle/middleware/oracle_common/common/bin
    ./wlst.sh

    The command prompt should change to show that you are now in the WLST environment.

  2. Now connect to the Node manager using the nmConnect command.

    nmConnect('weblogic_admin_user', 'admin_password', 'cloud_service_ip', 'port', 'domain','domain_path')

    where

    parameter meaning
    weblogic_admin_user is the administrator user name for your Oracle Cloud Service
    admin_password is the administrator password.
    cloud_service_ip is the ip address of your Oracle Java Cloud service instance
    port is the listener port for the Node Manager. This is usually 5556
    domain is the name of your Weblogic domain. This can be found in the service details page of the Oracle Java Cloud service console.
    domain_path is the fully qualified path where the domain resides on your virtual machine.

    For example:

    nmConnect('weblogic', 'gTY78Hcv', '10.10.10.10', '5556', 'MyJCSODI_domain','/u01/data/domains/MyJCSODI_domain')

    Note– all the parameters are enclosed in single quotes.

  3. Now you are connected to the Node Manager, you can start your administration server. Use the following command:

    nmStart('MyJCSODI_adminserver')

    Remember to replace the parameter with the name of your own administration server domain.

Post-Configuration Tasks

Use the WLS Administration Console to update the Oracle Coherence parameters. To configure Oracle Coherence:

  1. Log into the Oracle WebLogic Server Administration Console.

    WLS Console Login
    Description of this image
  2. In the Domain Structure panel, expand the Environment node. Click Coherence Clusters.

    Environment Coherence Clusters
    Description of this image
  3. In the Coherence Clusters table, click DataGridConfig.

    Data Grid Config
    Description of this image

  4. Select the Configuration tab and ensure that the Cluster Listen port has been set. If there is no value then click and set Cluster Listen port to 9000. (If this port is in use then you may have to change it later on)

    Description of this image

  5. Click the , then change to the Members tab. Select Part of the cluster under the Clusters section, and then select your managed server.

    Now click and

    Members tab
    Description of this image

The post-configuration tasks pertaining to Coherence membership are done. When you start the servers (next section), you may need to come back here to adjust the Coherence membership again.

Starting the Servers

To get your deployments up and running, you must start the Administration Server and Managed Servers that were created during domain extension.

Start (or if necessary restart) the servers. Use the command line script to restart the Admin Server, and use the WebLogic Server console to start the Managed Servers. The Admin Server may already be running!

  1. You can now access the WLS Administration Server Console by using the following link: http://admin_server_host:admin_server_port/console.

    WLS Console Login
    Description of this image

  2. In the Domain Structure panel, expand the Environment node. Click Servers.

    Servers
    Description of this image

  3. Click the Control tab, select your managed server (click the checkbox, not the server name), click . (This assumes your Node Manager is running.)

    Start Managed Server
    Description of this image

  4. Click to continue. Wait a minute.

    Confirm
    Description of this image

    Troubleshooting Starting Managed Server:

    Problem Statement: When you start the your managed server, it may fail with the following message in the /u01/data/domains/myjcs_domain/servers/managed_server/logs/managed_server.log file:

    This member could not join the cluster because of a configuration mismatch between this member and the configuration being used by the rest of the cluster. This member specified a cluster name of "DataGridConfig" which did not match the name of the running cluster. This indicates that there are multiple clusters on this network attempting to use overlapping network configurations. .

    Cause: Your server is trying to join another Coherence cluster, perhaps from another node.

    Workaround: In the WLS Console, go to Domain Structure > Environment > Coherence Clusters then click DataGridConfig and change the Listen Port from the default of 8088 to something else, perhaps 9000.

  5. The agent should now be deployed in JCS. You can see it by going to Domain Structure > Deployments then in Summary of Deployments panel click Deployment Order twice to get it sorted low-to-high. You should see oraclediagent near the top, and it should be State=Active and Health=OK.

    Deployments
    Description of this image

    Troubleshooting oraclediagent State and Health:

    Problem Statement: The agent oraclediagent may fail to start with the following message:
    weblogic.application.ModuleException: com.tangosol.net.RequestPolicyException: No storage-enabled nodes exist for service oracle.wls.internal.odi:OdiDistributedCache:com.tangosol.net.RequestPolicyException:No storage-enabled nodes exist for service oracle.wls.internal.odi:OdiDistributedCache
    /!\ Warning Errors were encountered while performing this operation.


    Cause: Your managed server is failing to fully join the Coherence cluster.

    Workaround: In the WLS Console, go to Domain Structure > Environment > Coherence Clusters then click DataGridConfig > Members tab and and change the Clusters from the default of All servers in the cluster to just Part of the cluster > managed_server, then click and and View changes and restarts to restart the managed server.

  6. Go back to ODI Studio to test the agent. In Topology > Physical Architecture > Agents > OracleDIAgent, click .

    Agent Test
    Description of this image

  7. If you chose to configure the standalone collocated agent, then you can test it by repeating step 6, but for OracleDIAgent1.

    Note: This Agent would need to be started first, which you do from the command line. For more information on how to do this, see: section 7.5 - Starting a Standalone or Standalone Collocated Agent Using Node Manager - of the Oracle Fusion Middleware Installing and Configuring Oracle Data Integrator.

The WLS admin server and managed servers are now running. All deployed applications are running.

ODI is now provisioned on the JCS instance. The agents are running and available for ad hoc and scheduled work.

Want to Learn More?