(Some) Advantages of the OCA are:
- No ports need to be opened on the on-prem server,
- all connections between COA und OCI will be SSL secured,
- all communication is initiated from the OCA.
The basic pattern of how to use the OCA is the public internet pattern. In this pattern, the OAC will be installed in the customer network and communicate between the on-prem application and the OIC. The all connections will be via the public internet.
More information about the OCA can be found in the according Oracle Documentation (namely https://docs.oracle.com/en/cloud/paas/integration-cloud/agent.html) as well as in the related tutorial provided by Oracle (at https://docs.oracle.com/en/cloud/paas/integration-cloud/integrations-user/create-integration-exchange-messages-oracle-integration-and-local-host.html#GUID-F92564A0-8C6F-4C35-A5EE-B3F19571B616).
To create an OCA, you first need to login into the OIC, then navigate to „Integration“ – „Agents“ – „Create Agent Group“. The next step is to fill out the basic information for the OCA and save it.
After clicking “Create”, you should see the newly created agent in your agents list.
Next, download the agent ZIP file and copy it on the server, where the agent should run. Be aware that the agent cannot be run as a Windows service, so if you want to use the agent on a Windows server, the user must be logged in all the time. In the following, the explanation will apply to a Linux server.
After copying the files, unzip them into the folder where you want to store the data:
and modify the InstallerProfile.cfg
# Required Parameters
# oic_URL format should be https://hostname:sslPort
Check if JAVA_HOME is part of the PATH variable. If not, add it. After this, start the agent with:
java -jar connectivityagent.jar
If you want to run the connectivity agent as background service, you need to add
into the InstallerProfile.cfg and start it with
nohup java -jar connectivityagent.jar
After this, the agent is running and can be used. In the integration cloud, you will see now that the agent is running.
Unfortunately (currently), it is not possible to define a virtual cloud network for the OIC to create a site-to-site connection between the Oracle Cloud and the customers network, so that the OIC connectivity agent is a good way to access on-premise systems that are not exposed to the internet. It is important to know the limitations of the adapters together with the agent. We suggest an installation of the connectivity agent on a Linux server.