Meet the Requirements for the Connectivity Agent

System Requirements

Before installing the on-premises connectivity agent, make sure that the on-premises host, often a virtual machine, meets the system requirements.

Area Requirements

Operating system

Install the connectivity agent on one of the following certified operating systems:
  • Oracle Linux 6.x

  • Oracle Linux 7.x

  • Oracle Linux 8.x

  • RedHat Enterprise Linux 6.6

  • RedHat Enterprise Linux 7.x

  • RedHat Enterprise Linux 8.x

  • Suse Linux Enterprise Edition 12 SP2

  • Windows Standard Edition 2016

  • Windows 2019

Note:

  • The connectivity agent is not certified on Kubernetes (K8s).
  • IBM or Open JDK are not supported.

Memory

Provide a minimum of 8 GB memory with 4 GB of heap size dedicated for the connectivity 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 a value greater than 8 GB.

Software

Install and use JDK version 17.

You do not need to purchase a JDK license for the sole purpose of installing and/or running the connectivity agent. See JDK license and support for OIC Connectivity Agent (Doc ID 2611142.1).

The JDK installation can be the same one as used with other products installed on the same host. However, separate JDK licensing may be required for any use of Java beyond the use of the connectivity agent. Ensure that the JDK installation is not modified for use with these other products.

Network Requirements

Area More information

General requirements

If your organization requires one or more connectivity agents, make sure that the connectivity agent is compatible with your organization's operating procedures and requirements.

For example, the connectivity agent must establish an outbound call from your intranet to Oracle Integration. Therefore, your organization must allow outbound calls from your intranet. If your organization has a sensitive network, any outbound communication to outside the firewall might be restricted.

See About the Connectivity Agent.

Authentication

You must make sure that your organization allows the connectivity agent to use OAuth 2.0 token-based authentication when invoking Oracle Integration endpoints.

See Create an Agent Group.

Requirements for the local host on which you install the connectivity agent

The connectivity agent must be able to access the application that you're integrating with. Therefore, the host that you install the connectivity agent on must also have access to the application.

Requirements for agent groups

To install an agent group, you must allow egress from the agent network to Oracle Integration design-time and runtime and the identity domain or Oracle Identity Cloud Service.

Requirements for the person who installs the connectivity agent

The person who installs the connectivity agent must have the required permissions and roles.

See Agent Download and Installation.

Authentication for Windows hosts

When you install the connectivity agent on a Windows host, the connectivity agent does not work when a proxy uses NT LAN Manager (NTLM) authentication. If you are using the connectivity agent on a Windows host, you must use an alternate authentication method.

Requirements for the Oracle WebLogic JMS Adapter

When you use the Oracle WebLogic JMS Adapter and the connectivity agent, you must use Oracle WebLogic Server version 12.2.1.4 and higher. Prior versions of Oracle WebLogic Server are not supported with the connectivity agent and this adapter.

To determine your version of Oracle WebLogic Server:

  1. Enter the Oracle WebLogic Server URL. For example:
    http://abcweblogic.oracle.com:7001/console
  2. At the bottom left, find the version. For example:
    WebLogic Server Version: 12.2.1.4.0