Provisioning and Accessing the Clustered Oracle Data Integrator Cloud Instance

Provisioning the Clustered Oracle Java Cloud Instance

How to configure the clustered Oracle Java Cloud instance on which you want to install and run Oracle Data Integrator Cloud

To start with you will create a new clustered Oracle Java Cloud instance that is linked to your database. This provision will also include the Oracle Data Integrator installation software as part of its virtual machine set up.

Log on to your Oracle Cloud service and select Java from the main services menu.
From the Oracle Java Cloud Instances page, click the Create Instance button. Select Java from the drop-down list.
On the first page you will fill out the service details:
1. Instance Name — This is the unique name you will assign to your service.
2. Description — This is optional text you can use to describe the service.
3. Notification Email — This is optional. You can enter an email address for alerts and notifications.
4. Service Level — From the dropdown, select Oracle Java Cloud Service for Fusion Middleware.
5. Software Release — Select Oracle Weblogic Server 12c(12.2.1.2)
6. Software Edition — Select Enterprise Edition
7. Metering Frequency — Select Monthly from the dropdown.
Press Next when you have completed your entries.

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:

Enter parameter details for these sections:

WebLogic Configuration

Parameter	Description
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	Set to 2, so you can load balance.
Fusion Middleware	Select Oracle Data Integrator from the drop-down list.
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, but you can select it if you want.

WebLogic Access

Parameter	Description
Local Administrative Username	Assign an administrator user name for the Weblogic server
Password	Assign a password for the Weblogic administrator
Password	Assign a password for the Weblogic administrator

Database Configuration

Parameter	Description
Database Instance Name	Select in the drop down list the database you want to use to store the Oracle Data Integrator 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

Parameter	Description
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 container already exists.

Load Balancer

Parameter	Description
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

When you have entered all the details, click Next.

On the instance creation confirmation page, click Create.
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.

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.

Connecting to the Oracle Java Cloud Instance Environment Using SSH

Steps to use SSH to connect to Oracle Java Cloud Instance.

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.

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.

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@192.0.2.1

You are now logged in as user opc.

Switch to user oracle on the JCS Admin Server VM.
```
sudo su oracle
```

Turn off the lock screen on the JCS Admin server.

gconftool-2 -s -t bool /apps/gnome-screensaver/lock_enabled false

Start the VNC Server. If prompted for a password, enter one. Make a note of it.
```
vncserver -nolisten local -geometry 1680x1050
```

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

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.
```
vncviewer
```
In the Window that opens, enter localhost:5901 and click OK.

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

The steps to install 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.

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.
Unpack the archive file using the unzipcommand.
```
unzip ODI.zip
```
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:
To run the sintaller, use the Java command:
```
java -jar fmw_12.2.1.2.6_odi_generic.jar
```
to initiate the installation.
When prompted, set the Inventory Directory to /u01/app/oraInventory, then click OK to create the Central Inventory Directory.
When the Welcome screen opens, click Next.
Select Skip Auto Updates and then click Next.
For the installation location enter
```
/u01/app/oracle/middleware
```
, then click View to check the features that will be installed at this location. Click Next to move to the next step.
In the Installation Type form, select Enterprise Installation. Click Next.

Note:
The Standalone Installation is not supported in this configuration. Do not select it.
Click Next 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.
On the Installation Summary form, click Install.
The Installation Progress screen will show the name and status of each component as it copied and configured. When the operation has completed, click Next.
Click Finish on the Installation Complete screen.

You have successfully installed the Oracle Data Integrator.

Installing Oracle Data Integrator on the Second Oracle Java Cloud Instance Node

The steps to install Oracle Data Integrator on the second Oracle Java Cloud Instance.

As with all things Linux, directories are case sensitive.

Get the host name and private IP address of VM2 and of the Load Balancer:
1. Sign in to the My Services application and go to the My Services Dashboard.
2. In the Oracle Compute Cloud Service section, click the Open Service Console link.
3. On the instance details page, make a note of the host name and the public IP address of the second node, and the Public IP address of the load balancer.

Copy the private key file to the Administration server.

Close the VNC connection to the Administration server, and then close the two terminal sessions you used to create the SSH tunnel.

Copy the private key file to the /tmp directory on the Administration Server. Open a terminal session and enter the command:

scp -i path_to_private_key_file path_to_private_key_file opc@IP_of_JCS Instance_Admin_Server:/tmp

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:

scp -i keys/key-20170605 keys/key-20170605 opc@192.0.2.1:/tmp

Now you need to make a copy of the file so that it can be accessed by the oracle user as you will be SSH tunnelling from the Administration server to the managed server (on the second node).

Start by connecting to the Administration server using SSH:
```
ssh -i path_to_private_key_file opc@IP_of_JCS Instance_Admin_Server
```
For example:
```
ssh -i keys/key-20170605 opc@192.0.2.1
```
Change to the /tmp directory:
```
cd /tmp
```
Make a copy of the private key file on the Administration server and give anyone full access to it:
```
cp key-20170605 key-20170605-1
chmod 777 key-20170605-1
```
Delete the private key file you originally copied over:
```
rm keyfile
```
For example:
```
rm key-20170605
```
Change to the oracle user:
```
sudo su oracle
```
Make a copy the copy of the private key file and give it the original name:
```
cp keyfile-1 keyfile
```
For example:
```
cp key-20170605-1 key-20170605
```
Now you have the private key file owned by the oracle user. All that needs doing is to set the permissions on it to be limited as before:
```
chmod 600 keyfile
```
For example:
```
chmod 600 key-20170605
```
Change back from the oracle user to opc.
```
exit
```
Delete the private key file copy owned by opc:
```
rm keyfile-1
```
For example:
```
rm key-20170605-1
```
Close the terminal session.

Now, reconnect to the Administration server and start VNC again.

Use the ssh command as in step 3 - Connecting to the Oracle Java Cloud Service Environment Using SSH - to log in to the second node as oracle user.
1. Open a terminal session and enter the following command:
```
$> ssh –i /tmp/private_key_file opc@host_name_of_VM2
```
  Where private_key_file represents the name of the private key file you just copied over, and host_name_of_VM2 represents the host name of the second node. Note: Use the host name of the second node, not its public IP address.
  
  For example
```
ssh -i /tmp/key-20170605 opc@myjcsodi-wls-2
```
  Enter the passcode for the private key file, if prompted.
2. Switch to the oracle user
```
sudo su oracle
```
3. Disable the screen saver and start the VNC server
```
gconftool-2 -s -t bool /apps/gnome-screensaver/lock_enabled false
vncserver -nolisten local -geometry 1680x1050
```
4. Open a second terminal session and enter the following command to open a tunnel to the second node:
```
ssh -i /tmp/private_key_file -L 5901:127.0.0.1:5901 opc@host_name_of_VM2 -N
```
  Where host_name_of_VM2 represents the host name of the second node. As before, it is not an IP address!
  
  For example:
```
ssh -i /tmp/key-20170605 -L 5901:127.0.0.1:5901 opc@myjcsodi-wls-2 -N
```
  You can ignore any messages about the bind address already being in use. Enter the password for VNC when prompted.
5. To get desktop access for the Oracle Java Cloud Server instance, use the VNC Viewer on the Administration server to connect to localhost:5901.
```
vncviewer
```
  In the Window that opens, enter localhost:5901 and click OK.
6. Enter the password when prompted.
7. Once VNC connects you to the second node, as before, you want to turn off the screen saver, otherwise you could find yourself locked out of it. Select System/Preferences/Screensaver menu item. In the resulting Screensaver Preferences dialog box, make sure Activate screensaver when computer is idle is not selected.
Install the Oracle Data Integrator software as shown in the Installing Oracle Data Integrator section.
Once Oracle Data Integrator is installed, close the VNC Viewer and then shut the two terminal sessions that you opened on the Administration server for the SSH tunnel.

Locating your Database Prefix

Steps to locate the prefix fo your database cloud service you will use with Oracle Data Integrator Cloud.

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.

Start an SSH terminal session and connect to your Oracle Java Cloud instance.
Switch to the oracle user by executing the following command:
```
sudo su oracle
```
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:@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)

Steps to create the database repository for Oracle Data Integrator Cloud, using the Repository Creation Utility.

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

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.
On the Create Repository panel, accept the defaults and click Next.

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

The Repository Creation Utility will check the entries by connecting to the specified database. When the checks have been completed click OK.
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.
The Repository Creation Utility will display a message window while it is checking prerequisites for creating the database. Press OK when it has finished.
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

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”

The default tablespaces are fine, just click Next.
You will now receive a warning stating that the RCU is about to create any missing table spaces. Press OK to continue.
The Repository Creation Utility will now proceed to create the tablespaces. Press OK when it's finished.
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.
On the Summary screen, click Close.

You now have the tablespaces and schemas needed to support Oracle Data Integrator Repositories in the database.

Updating the Clustered Oracle Java Cloud Instance Domain

Steps to update the clustered Oracle Java Cloud Instance domain. on which you have installed Oracle Data Integrator Cloud.

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

Access the Administration Server Console by using the following link:
```
 http://admin_server_host:admin_server_port/console
```
.
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.
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.
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
```
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.
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.
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.
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.
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.
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.
In the Advanced Configuration form, select Topology, System Components and Deployments and Services. On many of the panels you will just accept the defaults.
In the Managed Servers form, update the required managed servers.
1. To avoid targeting related libraries and applications to the default Oracle Data Integrator server instead of the Oracle Data Integrator cluster, delete the default Oracle Data Integrator 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.
3. Make a note of the Listen Port number, you will need this later on when creating an Agent in Oracle Data Integrator
Click Next.
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.
Leave the Server Templates settings as they are and click Next.
Leave the Dynamic Servers settings as they are and click Next.
In the Assign Servers to Clusters form, ensure that the servers are assigned to the cluster. Click Next.
In the Coherence Clusters form, accept the defaults and click Next.
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.
In the Assign Servers to Machines form, ensure that the servers are assigned as shown in the image below. then click Next.

Click Next.
Leave the Virtual Targets settings as they are and click Next.
Do not change anything on the Partitions screen. Click Next.
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.
Check server listen address. 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. (Although we are not going to use a collocated agent, it is sensible to specify a password and make a note if it.)
Do not change anything on the Assign System Components screen. Click Next.
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 Administration 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.
Confirm that odiMasterRepository and odiWorkRepository are in the right side under Targets/cluster/JDBC/JDBC System Resource.
In the Configuration Summary form, leave the defaults and click Update.

You can safely ignore the warning about No system component instance.
Click Next once the domain is configured, then click Finish.

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

Creating Agents in the Master Repository Using Oracle Data Integrator Studio

Steps to create physical and logical Oracle Data Integrator agents

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 Oracle Data Integrator Studio, see Creating an Agent in the Master Repository Using ODI Studio in Installing and Configuring Oracle Data Integrator.

Note:

Running Oracle Data Integrator 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 Oracle Data Integrator Studio.

Start ODI Studio from the command line by using the following commands:
```
cd /u01/app/oracle/middleware/odi/studio 
./odi.sh
```
You will be asked if you would like to import preferences from a previous ODI installation. Click No.

Log in to the Repository you created earlier using the RCU.

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

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

Field	Description
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. .
Password	The password you created for the SUPERVISOR

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

Select Work Repository and click Browse to display the Work Repository selection window.
Select WORKREP and click OK.
Click Test. (If the selection worked, then the Test should work…)
If successful, click OK
Enter a Wallet password twice. Click OK.
All the information should be saved and pre-populated. Just click OK and the Designer, Operator, and Topology tabs should appear on the left.

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

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.
Click Save.
Create a Logical Agent. On the Topology tab, expand Logical Architecture, right-click Agents, and select New Agent.
For simplicity, keep all the names the same: OracleDIAgent. Click Save. Close the OracleDIAgent tab.
Optionally, you can repeat steps 4, 5 and 6, but for the standalone collocated agent.

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

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.
Click Save.
Create a Logical Agent. On the Topology tab, expand Logical Architecture, right-click Agents, and select New Agent.
For simplicity, keep all the names the same: OracleDIAgent1. Click Save. Close the OracleDIAgent1 tab.

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

Starting the Administration Server

Once you’ve created the physical and logical agents in Oracle Data Integrator, you need to re-start the WLS 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.

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.

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.

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

Steps to update Oracle Coherence parameters

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

Log into the Oracle WebLogic Server Administration Console.
In the Domain Structure panel, expand the Environment node. Click Coherence Clusters.
In the Coherence Clusters table, click DataGridConfig.
Select the Configuration tab and ensure that the Cluster Listen port has been set. If there is no value then click Lock & Edit and set Cluster Listen port to 9000. (If this port is in use then you may have to change it later on).
Click Save , then change to the Members tab. Select Part of the cluster under the Clusters section, and then select your managed server.

Now click Save and Activate Changes.

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 Managed Servers

To get your agents up and running, use these steps to start the 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!

You can now access the WLS Administration Server Console by using the following link:
```
http://admin_server_host:admin_server_port/console
```
In the Domain Structure panel, expand the Environment node. Click Servers.
Click the Control tab, select your managed server (click the check box, not the server name), click Start. (This assumes your node manager is running.)
Click Yes to continue. Wait a minute...
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.
Go back to ODI Studio to test the agent. In Topology > Physical Architecture > Agents > OracleDIAgent, click Test.
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.