How to install the Oracle Integration Cloud on premises connectivity agent (18.1.3)

Recapitulation on how to install the Oracle Integration Cloud on premises connectivity agent

Recently (april 2018) I gained access to the new Oracle Integration Cloud (OIC), version 18.1.3.180112.1616-762,  and wanted to make an integration connection to an on-premise database. For this purpose, an on premise connectivity agent needs to be installed, as is thoroughly explained by my colleague Robert van Mölken in his blog prepraring-to-use-the-ics-on-premises-connectivity-agent.

With the (new) Oracle Integration Cloud environment the installation of the connectivity agent has slightly changed though, as shown below. It gave me some effort to get the new connectivity agent working. Therefore I decided to recapture the steps needed in this blog. Hopefully, this will give you a headstart to get the connectivity agent up and running.

Prerequisites

Access to an Oracle Integration Cloud Service instance.

Rights to do some installation on a local / on-premise environment, Linux based (eg. SOA virtual box appliance).

Agent groups

For connection purposes you need to have an agent group defined in the Oracle Integration Cloud.

To define an agent group, you need to select the agents option in the left menu pane.  You can find any already existing agent groups here as well.

Select the ‘create agent group’ button to define a new agent group and fill in this tiny web form.

Downloading and extracting the connectivity agent

For downloading the connectivity agent software you also need to select the agents option in the left menu pane, followed by the download option in the upper menu bar.

After downloading you have a file called ‘oic_connectivity_agent.zip’, which takes 145.903.548 bytes

This has a much smaller memory footprint than the former connectivity agent software (ics_conn_agent_installer_180111.0000.1050.zip, which takes 1.867.789.797 bytes).

For installation of the connectivity agent, you need to copy and extract the file to an installation folder of your choice on the on-premise host.

After extraction you see several files, amongst which ‘InstallerProfile.cfg’.

Setting configuration properties

Before starting the installation you need to edit the content of the file InstallerProfile.cfg.

Set the value for the property OIC_URL to the right hostname and sslPort *.

Also set the value for the property agent_GROUP_IDENTIFIER to the name of the agent group  you want the agent to belong to.

After filling in these properties save the file.

* On the instance details page you can see the right values for the hostname and sslPort. This is the page which shows you the weblogic instances that host your OIC and it looks something like this:

Certificates

For my trial purpose I didn’t need a certificate to communicate between the OIC and the on-premise environment.

But if you do, you can follow the next 2 steps:

a. Go to the agenthome/agent/cert/ directory.

b. Run the following command: keytool -importcert -keystore keystore.jks -storepass changeit -keypass password -alias alias_name  -noprompt -file certificate_file

Java JDK

Before starting the installation of the connectivity agent, make sure your JAVA JDK is at least version 8, with the JAVA_HOME and PATH set.

To check this, open a terminal window and type: ‘java –version’ (without the quotes)

You should see the version of the installed java version, eg. java version “1.8.0_131”.

To add the JAVA_HOME to the PATH setting, type ‘setenv PATH = $JAVA_HOME/bin:$PATH’ (without the quotes)

Running the installer

You can start the connectivity agent installer with the command: ‘java –jar connectivityagent.jar’  (again, without the quotes).

During the installation you are for your OIC username and corresponding password.

The installation finishes with a message that the agent was installed succesfully en is now up and running.

Check the installed agent

You can check that the agent is communicating to/under/with the agent group you specified.

Behind the name of the agent group the number of agents communicating within it is shown