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

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. On the Oracle Java Cloud Service Instances page, click the instance you just created.
   2. The public IP address of the Administration Server is available under the Resources 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.

      

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.

vncviewer

In the Window that opens, enter localhost:5901 and click OK.

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. However, once you have unzipped the ODI installer files, you must apply patch 22384876 before installing ODI.

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, from which you can also apply patch 22384876. To run the installer. Use the Java command:

   java -jar fmw_12.2.1.3.0_odi_generic.jar

   to initiate the installation.

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

   

5. When the Welcome screen opens, click Next.

   

6. On the Auto Updates screen, select Search My Oracle Support for Updates.

   Enter your user name and password for My Oracle Support. Click Search.

   Select 22384876 13.9.3 PREFLIGHT ON FMW 12.2.1.3.1. Click Next.

   Click Yes on the popup dialog box Some of the updates require restart of the installer. Do you want to continue?. The installer will restart.

   Click Next.

   

7. For the installation location enter /u01/app/oracle/middleware. Click Next to move to the next step.

   

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

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

   

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

   

10. On the Installation Summary form, click Install.

    

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 Next

    

12. Click Finish on the Installation Complete screen.

    

You have successfully installed Oracle Data Integrator.

1. Open a browser in the JCS instance.
2. Log on to My Oracle Support https://support.oracle.com, and search for patch 26669648. Download it to your instance.
3. Verify your OPatch version. Execute the command:

   cd /u01/app/oracle/middleware/OPatch
   ./opatch version

   The command should not error and must return an OPatch version of 13.3 or later.

4. Verify the OUI Inventory. Execute the command: ./opatch lsinventory -jre $JAVA_HOME/jre. This command should NOT error out.
5. In your Oracle Home, edit file .bashrc and add the following lines at the end:

   export ORACLE_HOME=/u01/app/oracle/middleware
   export PATH=${ORACLE_HOME}/OPatch:${PATH}

6. Navigate to the directory where the patch downloaded, for example: /home/oracle/Downloads.

   Unzip patch 26669648, using the command:

   unzip p26669648_122130_Generic.zip

7. Navigate to the patch directory (for example /u01/app/oracle/tools/home/oracle/Patches/26669648).
8. Run the command:

   opatch apply

   to apply the patch.

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

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

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

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

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

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

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

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

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

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

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

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

   Click Next when the opening screen is displayed.

   

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

   

3. You must use the Database you seleted when creating you ODI Cloud Service instance. The database details you define here will be designated as the supervisor database:

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

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

   

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

   

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

   

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

   

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

   

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

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

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

   

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

   

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

    

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

    

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

    

    

13. On the Summary screen, click Close.

    

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

Before you begin updating the Java Cloud Service Domain, use the WebLogic Administration Console to shutdown all Managed Servers and the Administration Server. If they are already shut down, go straight to step 4.

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

   

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

   Click Yes to continue. Wait a minute.

   

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

   Click Yes.

   

   Just ignore the web browser for the moment.

4. To update your domain, use the Configuration Wizard to extend (update) the Java Cloud Service domain with ODI. Open a terminal session and enter the following commmands:

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

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

   

6. In the Templates form, do the following:

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

   Click Next.

   

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

   Click Get RCU Configuration. When the Connection Result Log displays "Successfully Done", press Next

   

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

   

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

   

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

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

    Click Next.

    

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

    

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

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

    Click Next.

    

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

    

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

    

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

    

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

    

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

    

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

    

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

    Click Next.

    

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

    

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

    

22. Do not change anything on the System Components page. This screen is used to configure an optional standalone collocated agent. If you are going to use a standalone collocated agent, make a note of the System Component, which is the agent's name, for use when you define the agent in ODI's Topology. Click Next.

    

23. On the ODI Configuration page, set a SUPERVISOR password for the optional Oracle Data Integrator standalone collocated agent. If you are going to use a standalone collocated agent, make a note of the values from this page for use when you define the agent in ODI's Topology.

    

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

    

25. The ODI applications are deployed to the cluster. Check that they have been deployed correctly. On the right side under Targets, confirm that you can see odiconsole and oraclediagent under your cluster > Application. If they are still on the left-hand side, follow the instructions in the Configuration Wizard to transfer them to the right-hand side.

    

    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.3.0 and oracle.odi-sdk#2.0@12.2.1.3.0.
    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.3.0 and oracle.odi-sdk#2.0@12.2.1.3.0.
    2. Click the middle < to move the items from the right. They don't actually go to the left, they just go away from the right.

    Now click Next.

26. Confirm that odiMasterRepository and odiWorkRepository are in the right side under Targets/cluster/JDBC/JDBC System Resource. If not, copy them across using described in the previous step.

    

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

    

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

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

    

    

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

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

   .

   

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

   

3. Login to the Repository created by RCU.

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

      

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

      

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

      

   4. Select WORKREP and click OK.

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

   6. If successful, click OK.

   7. Enter a Wallet password twice. Click OK.

      

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

      

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

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

   

   Click Save ()

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

   

6. For simplicity, keep all the names the same: OracleDIAgent. Click Save (). Close the OracleDIAgent tab.

   

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 () Physical Architecture, right-click Agents, and select New Agent.

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

   

   Click Save ()

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

   

9. For simplicity, keep all the names the same: OracleDIAgent1. Click Save (). Close the OracleDIAgent1 tab.

   

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

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.

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

1. Log into the Oracle WebLogic Server Administration Console.

   

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

   

3. In the Coherence Clusters table, click DataGridConfig.

   

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

   

5. Click the 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.

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.

   

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

   

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

   

4. Click Yes to continue. Wait a minute.

   

   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.

   

   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 Lock & Edit and change the Clusters from the default of All servers in the cluster to just Part of the cluster > managed_server, then click Save and Activate Changes 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 Test.

   

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.