You must download the agent installer from Oracle Integration Cloud Service and run the installer to install the on-premises agent in your local environment. During installation, you associate the agent with the agent group identifier you generated in Oracle Integration Cloud Service. After completing on-premises agent installation, you must apply a patch.
System Requirements
You must satisfy the following prerequisites on your on-premises host before running the agent installer in a production environment:
Ensure that you have created the agent group. You must specify the agent group identifier when installing the on-premises agent. For information, see Creating an Agent Group.
Install JRE version 1.7 or higher.
Set the JAVA_HOME
property to the location of the JDK installation. For example:
JAVA_HOME=/usr/java/jdk1.7.0_79
Install the on-premises agent on Linux OEL version 5 or 6 only.
Provide a minimum of 8 GB memory with 4 GB of heap size dedicated for the agent JVM. If you want to include any other processes on that host besides the on-premises agent, it is strongly recommended that you increase physical memory to greater than 8 GB.
Set the number of worker threads to a value appropriate to your environment. By default, the on-premises agent is set to 3
. This may be sufficient for some low-load environments and most demo environments. However, for high-load environments, the agent instance may need additional tuning. Increase concurrency on the on-premises agent installation host by setting agentWorkerThreads
to a recommended value of 40
in the CpiAgent.properties
file. This change requires an agent restart.
agentWorkerThreads=40
For information about editing this file, see Updating Property Values.
Do not install the on-premises agent in an environment that includes an existing Oracle WebLogic Server installation.
Installation
To download and run the on-premises agent installer:
Note:
It is recommended that you retain a copy of thecloud-connectivity-agent-installer.bsx
agent installer file after completing installation.Log in to Oracle Integration Cloud Service.
In the Integration Cloud Service toolbar, click Designer.
On the Designer Portal, click Agents.
The Agent Groups page is displayed. This page shows any current agent groups and on-premises agents associated with the agent groups.
Description of the illustration GUID-CA56DDEA-B243-4A84-A0D1-89ACEB01483D-default.png
Click Download Agent Installer.
Select Connectivity Agent.
This selection enables you to integrate Oracle Integration Cloud Service with on-premises environments.
Select Save File when prompted to save the file to a directory location on your on-premises host.
Unzip the downloaded file.
Locate the cloud-connectivity-agent-installer.bsx
agent installer file.
chmod +x cloud-connectivity-agent-installer.bsx
Execute the file with the following properties specified. Do not install the on-premises agent in a directory path that includes /tmp
. Note the use of the dash (-
) when specifying the property value. The output of this command is displayed on-screen. For troubleshooting purposes, you can also redirect the output to an output file.
./cloud-connectivity-agent-installer.bsx —h=https://ICS_host.us.oracle.com:port —u=weblogic —p=my_password —ad=agent_group_identifier
Parameter | Status | Description | Additional Notes |
---|---|---|---|
-h |
Required | Specifies the Oracle Integration Cloud Service hostname and port. As an example, when installing from your Oracle Integration Cloud Service POD, the host and port you specify are typically the Oracle Integration Cloud Service URL (for example, https://icsapps.integ.dc4.c1234.oraclecorp.com:443 ). |
Note the following issues:
|
-u |
Required | Specifies the Oracle Integration Cloud Service user name. | |
-p |
Required | Specifies the Oracle Integration Cloud Service password. | Note:
|
-ad |
Required | Specifies the agent group identifier that was generated in the Identifier field when you created the agent group in the New Agent Group - Information dialog in Creating an Agent Group. You must create the agent group before you can install the on-premises agent. | |
-ph |
Optional | Specifies the outbound proxy hostname. | If your on-premises host includes a proxy server, you must specify this property. The agent can work with any proxy in the DMZ. |
-pp |
Optional | Specifies the outbound proxy hostname port. | If your on-premises host includes a proxy server, you must specify this property. |
All on-premises adapters are registered.
Oracle WebLogic Server and a Java database are installed.
The Oracle WebLogic Server and JRF domain is created.
The on-premises agent is deployed.
Once installation is complete, an agent instance is created for interacting with Oracle Integration Cloud Service. You can verify that the agent instance was created by going to the Agent Groups page and noting that the agent count was increased by one. If you click the number, details about the agent are displayed. For more information, see Viewing and Editing Agent Groups.
Troubleshooting Issues
If there is a Derby database (DB) already in use on the host on which the agent is being installed, you receive the following error:
2016-01-27 20:48:51,714 FINE [47] com.oracle.cie.domain.jdbc.DatasourceXBeanAspectHelper - prop str: user=dummy;portNumber=1527;databaseName=dummy;create=true;serverName=localhost url: jdbc:derby://localhost:1527/dummy;ServerName=localhost;databaseName=dummy 2016-01-27 20:48:51,714 FINE [47] com.oracle.cie.domain.jdbc.DatasourceXBeanAspectHelper - Selected DB ID/CAT: DerbyDerby's Driver (Type 4) Versions:Any 2016-01-27 20:48:51,714 FINE [47] com.oracle.cie.domain.jdbc.DatasourceXBeanAspectHelper - Selected DB vendor: Derby 2016-01-27 20:48:51,714 FINE [47] com.oracle.cie.domain.jdbc.DatasourceXBeanAspectHelper - adding normal datasource: opss-data-source 2016-01-27 20:48:51,714 FINE [47] com.oracle.cie.domain.jdbc.DatasourceXBeanAspectHelper - datasource: opss-data-source component name: OPSS Schema . . . . . .
Check if the Derby database is running.
ps -ef | grep "derby"
If any processes are displayed, run the following command to terminate them:
ps -ef | grep "derby" | awk '{print $2}' | xargs kill -9
At the end of on-premises agent installation, the following message is displayed:
Agent installation completed Successfully. Agent Instance creation successful
After this message is displayed, you may receive the following error message that can be safely ignored. On-premises agent installation was successful. This issue occurs during KSS store creation. If KSS store creation is required, you can manually perform this task at a later time.
javax.naming.AuthenticationException: User: [...], failed to be authenticated. [Root exception is java.lang.SecurityException: User: ..., failed to be authenticated.] Problem invoking WLST - Traceback (innermost last): File "/private/downloads/ICS_1.6.15_Agent/selfextract.TKERY8/agentInstaller/./scrip ts/import_cert_kss.py", line 45, in ? File "<iostream>" line 19, in connect File "<iostream>" line 552, in raiseWLSTException WLSTException WLSTException: Error occurred while performing connect : User: ..., failed to be authenticated. : User: ..., failed to be authenticated. Use dumpStack() to view the full stacktrace :