Oracle Integration Cloud Service provides an agent framework that enables you to create integrations and exchange messages between on-premises applications and Oracle Integration Cloud Service. Message payloads of up to 5 MB are supported through the use of compression, which may bring the payload down to 512 KB in size. The on-premises agent provides multithreading support, which allows for multiple executors to perform downstream message processing.
• Saas Agent
• On-premises agent
SAAS agent: This agent is installed and runs in Oracle Integration Cloud Service and supports communication with on-premises applications. There is one SAAS agent per Oracle Integration Cloud Service environment.
On-premises agent: This agent is installed and runs in an on-premises environment on the same network as internal systems such as Oracle E-Business Suite, Oracle Siebel, Oracle Database, and etc. You download the on-premises agent installer from the Agents page in Oracle Integration Cloud Service to your on-premises environment for installation. There can be multiple host systems, each running one or more agents, in a cloud/on premises topology. The on-premises agent does not permit any explicit inbound connections. All connections are established from the on-premises environment to Oracle Integration Cloud Service.
Functionality of On-Premises Agent are as follows:
• All communication is initiated by the on-premises agent.
• The on-premises agent registers with Oracle Integration Cloud Service over SSL using the provided Oracle Integration Cloud Service credentials.
• The on-premises agent checks for work by making outbound requests through the firewall.
• The on-premises agent can use a proxy to access the internet (the same proxy as other internal applications and browsers use).
• The on-premises agent connections are configured by the agent retrieving the configuration details from Oracle Integration Cloud Service.
• The on-premises agent processes requests by pulling messages from Oracle Integration Cloud Service across SSL.
• The on-premises agent posts responses by pushing messages to Oracle Integration Cloud Service across SSL.
Pre-requisites
• Ensure that you have created the agent group. You must specify the agent group identifier when installing the on-premises agent
• Install only Oracle JDK version 1.7 or 1.8. Other JDKs such as Open JDK are not supported.
• Set the JAVA_HOME property to the location of the JDK installation.
Example: JAVA_HOME=/usr/java/jdk1.7.0_79
• Install the on-premises agent on one of the following supported operating systems:
a. Linux OEL version 5 or 6
b. Red Hat Enterprise Linux Server release 6.6 (Santiago)
• Ensure that a Derby database is not running.
Steps for ICS Agent installation
The high-level steps for getting the On-Premises Agent installed on your production PROD consist of two activities:
1. Create an Agent Group in the ICS console.
2. Run the On-Premises Agent installer, this will be done on an on-premise Linux machine and the end result will be a lightweight Weblogic server instance that will be running on port 7001.
Create an Agent Group
1. Login to the production ICS console and view landing page.
2. Verify that the ICS version is 15.4.5 or greater.
3. Scroll down on ICS Home page and select Create Agents. Notice this brings you to the Agents page of the Designer section.
4. On the Agents page click on Create New Agent Group.
5. Provide a name for your agent group (e.g., AGENT_GROUP).
6. Review the Agent page containing new group.
1. Click on the Download Agent Installer drop down on the Agent page, select Connectivity Agent, and save file to an on-premise Linux machine where the agent will be installed/running. This Linux machine needs to be able to establish a non-proxy TCP/IP connection to the on-premises resource(s) it will be communicating with.
2. Extract the contents of the zip file for the cloud-connectivity-agent-installer.bsx. This .bsx is the installation script that will be executed in the on-premise machine where the agent will reside.
3. Set the proxy authentication so that proxy server doesn’t interrupt installation.
$export http_proxy="http://USER:PASSWORD@PROXY_SERVER:PORT”
$ export https_proxy="https://USER:PASSWORD@PROXY_SERVER:PORT"
4. Make sure the /etc/hosts file is updated with the machine IP & hostname for localhost.
5. Make sure the cloud-connectivity-agent-installer.bsx file is executable and give the permissions to execute (e.g., chmod +x cloud-connectivity-agent-installer.bsx) and execute the shell script.
NOTE: It is important to specify the SSL port (443) as part of the host URL. Also, there are optional properties for the proxy details if a proxy is required for your network.
./cloud-connectivity-agent-installer.bsx -h=https://<ICS_HOST>:443 -u=[username] -p=[password] -au=weblogic -ap=welcome1 -ad=AGENT_GROUP -ph=<PROXY_HOST> -pp=<PROXY_PORT> -pu=<PROXY_USERNAME> -ppw=<PROXY_PASSWORD>
For example:
./cloud-connectivity-agent-installer.bsx -h=https://xxxxxxx-xxx.integration.us2.oraclecloud.com:443 -u=xxxxxxxxx@xxxxx.com -p=xxxxxx -ad=ONPREMISE -au=xxxx -ap=xxxx -ph=ccxxxaaa.xxxxx.com -pp=8080
