Workflows for the Connectivity Agent

Use the workflows to understand how to install and use the connectivity agent.

Associate Multiple Connectivity Agents with an Agent Group

Follow these steps to install two on-premises connectivity agents and associate them with an agent group.

Step Task More information
1

Before installing the connectivity agent, ensure that the local host and network meet the requirements.

See Meet the Requirements for the Connectivity Agent.

2

Ensure that both agent instances can access the same endpoints

For example, agent 1 on host 1 and agent 2 on host 2 must both be able to access the same endpoint (for example, a Siebel system).

3

Create an agent group

You cannot use an existing group.

See Create an Agent Group.

4

Download and install the connectivity agent on one host

Ensure that you specify the agent group identifier of the new agent group.

See Download and Install the Connectivity Agent.

See Download and Install the Agent.

5

Follow the same steps to download and install the connectivity agent on a second host

You can install multiple agents on the same host. However, to use high availability capabilities, install the second agent on a second host.

That way, if one host goes down, agent processing continues running on the other host.

Create a horizontal cluster to achieve high availability. Installing the agent on the same virtual machine (VM) does not guarantee high availability.

  • Use the same JAR file that you downloaded for the first installation.

  • Use the same InstallerProfile.cfg file settings. You can also copy the file from one host to the other.

  • You cannot have more than two agent instances per agent group. Attempting to include a third agent instance in the same group during installation results in an error.

  • While you can install up to two agent instances per agent group, be aware of the current restriction with agent high availability when working in tandem with automatically upgraded agents. To ensure that both agent instances do not upgrade at the exact same time, it is recommended that you start each instance with a small time gap. The time gap can be as little as 10 minutes. This ensures that there is no outage due to both agent instances being upgraded at the same time.

Note:

Specify the same agent group identifier and Oracle Integration URL in the InstallerProfile.cfg file as with the first installation.
6

Confirm the installation

  • After installation completes, go to the Agents page and note that two agents are associated with the same agent group.

  • Go to the Monitor agents page and note the same information. In this case, both agent instances are running.

Associate One Connectivity Agent with an Agent Group

Follow these steps to install the on-premises connectivity agent and associate a single agent with an agent group.

Step Task More information

1

Before installing the connectivity agent, ensure that the local host and network meet the requirements.

See Meet the Requirements for the Connectivity Agent.

2

Create an agent group

See Create an Agent Group.

3

Download and run the on-premises connectivity agent installer on your host

During installation, you associate the on-premises connectivity agent with the agent group.

See Download and Install the Connectivity Agent.

Use the Connectivity Agent in an Integration

Follow this workflow to use the on-premises connectivity agent.

Step Task More information
1

Create an adapter connection in Oracle Integration and associate the connection with the connectivity agent group

If an adapter supports using the connectivity agent, you must select the agent's group while creating a connection that is based on the adapter. See Create a Connection with an Agent Group.

For adapters that don't support the connectivity agent, you don't select an agent group. See Create Connections.

2 Design an integration that uses this connection See Create an Integration.
3 Activate the integration See Activate an Integration.