Private Endpoint vs. Connectivity Agent

All outbound traffic from Oracle Integration is routed through an adapter, which connects to resources via a private endpoint or the connectivity agent. Different integrations might require different connection types. For example, one connection might use the connectivity agent for a resource that's on your on-premises network, while another connection might use a private endpoint for a resource that's in your VCN.

The following table lists the differences between a private endpoint and the connectivity agent.

Area	Private endpoint	Connectivity agent
Usage	Use a private endpoint to: Connect to resources in a single subnet within a VCN. Route traffic through a private NAT gateway, if your organization requires it. This scenario is not documented in this guide or supported by Oracle Integration. Refer to Oracle Integration Blogs for use cases such as this one.	Use the connectivity agent to connect to resources in your on-premises network.
Security	Oracle Integration routes traffic and packages through the private endpoint. All traffic stays on your private network without going over the public internet.	Oracle Integration routes traffic over the public internet.
Setup and maintenance	Before you can create a private endpoint, complete the prerequisite tasks. These tasks can take some time and require your organization's networking team. However, most of this work might already be complete. For example, if you have resources in your private Oracle Cloud Infrastructure tenancy, you already have a VCN and subnet, which are required. After completing all prerequisite tasks, configure the private endpoint. Configure only one private endpoint per Oracle Integration instance.	Setup of the connectivity agent is fast. Create a virtual machine (VM) on your private network to host the connectivity agent, and then install the connectivity agent on the VM. The connectivity agent requires ongoing maintenance and management. For example, you must manage the VM and the upgrade cycles of the connectivity agent. See About the Connectivity Agent in Using Integrations in Oracle Integration 3.
Adapter support	All outbound traffic from Oracle Integration goes through a connection that is based on an adapter. Therefore, while you create a private endpoint for an instance, securing outbound traffic with the private endpoint is available on an adapter-by-adapter basis. See Adapters that Support Connecting to Private Endpoints in Using Integrations in Oracle Integration 3.	Similarly, outbound traffic for the connectivity agent goes through a connection that is based on an adapter. The connectivity agent works with a number of adapters. See About the Connectivity Agent