Component: Adapters

Resource Service Limit
Connectivity agent memory A minimum of 8 GB memory with 4 GB of heap size dedicated to the on-premise agent's Java Virtual Machine (JVM). To include any other processes on the host besides the agent, increase the physical memory to a value greater than 8 GB.
Connectivity agent message payloads
  • 10 MB through the use of compression

All connectivity-agent-enabled adapters

  • 50 MB as request
  • 50 MB as response

SOAP and REST adapters configured with connectivity agent

  • 50 MB (structured XML/JSON document) as response from SOAP/REST endpoints
  • 1 GB for attachments as part of a response from SOAP/REST endpoints
Structured payloads (JSON, XML) for connectivity-agent-based adapters
  • SOAP and REST: 50 MB
  • File and FTP invoke responses: 50 MB
  • Other protocols: 10 MB (for example, database, JMS, MQ, Kafka, and others)
Structured payloads for trigger connections and responses from invoke connections
  • Cloud endpoints: 100 MB (not using the connectivity agent)
  • Private endpoints: 100 MB
Binary (unstructured) payloads (for example, attachments, MTOM) for trigger connections and responses from invoke connections
  • 1 GB
Private endpoint support

Connecting to private endpoints is supported in a growing list of adapters.

See Adapters that Support Connecting to Private Endpoints in Using Integrations in Oracle Integration 3.

Apache Kafka Adapter

For invoke configurations

Produce/Consume Message operations:

  • 10 MB with schema transformation for all the outbound operations
AS2 Adapter
  • 100 MB

Database adapters

  • Oracle Autonomous Data Warehouse Adapter
  • Oracle Autonomous Transaction Processing Adapter
  • Oracle Database Adapter
  • Oracle Database Cloud Service Adapter
  • IBM DB2 Adapter
  • Microsoft SQL Server Adapter
  • MySQL Adapter
  • Netezza Adapter
  • PostgreSQL Adapter
  • SAP ASE (Sybase) Adapter
  • Snowflake Adapter

For trigger configurations

Polling operations:

  • 50 MB with schema transformation for agent-based endpoints
  • 100 MB with schema transformation through private endpoints

For invoke configurations

Stored Procedure, Operation on Table, and Run PureSQL Statement operations:

  • 10 MB with schema transformation for all the outbound operations

Database Select operations:

  • 100 MB for public internet-based endpoints
  • 100 MB for private endpoints
  • 50 MB for agent-based endpoints
File Adapter (available only with the connectivity agent)

Read File operations:

  • 1 GB when used without a schema
  • 50 MB when using a schema for transformation
  • 50 MB for a read operation with structured payload

Polling with a connectivity agent:

  • 50 MB

Download File operations:

  • 1 GB

Note: The size of CSV files increases when translated into a message. Therefore, the file size must be less than 50 MB, so that the after-translation message size does not exceed 50 MB.

FTP Adapter

For invoke configurations

Read File operations:

  • 1 GB when used without a schema (when used with or without a connectivity agent)
  • 100 MB for cloud-based endpoints when using a schema for transformation
  • 50 MB for agent-based endpoints when using a schema for transformation
  • 100 MB for public internet-based endpoints
  • 100 MB for private endpoints

Download File operations:

  • 1 GB (when used with or without a connectivity agent)

Write File operations:

  • There is no limit

JMS adapters

  • Oracle WebLogic JMS Adapter
  • IBM MQ Series JMS Adapter

For trigger configurations

Consume Message operations:

  • 10 MB with schema transformation

For invoke configurations

Produce Message operations:

  • 10 MB with schema transformation
Oracle CPQ Adapter
  • 50 MB for response payloads
Oracle E-Business Suite Adapter
  • 100 MB for public internet-based endpoints
  • 50 MB for agent-based endpoints
REST Adapter

For trigger configurations

  • 3 MB for XML documents used for schema generation

    See REST Adapter Capabilities.

  • 1 GB for messages with attachments (for example, multipart/form-data)

  • 100 MB for incoming structured message payloads (any content-type header containing JSON, XML, HTML, YAML, or YML)

    Note: If the string length for fields in a JSON payload exceeds 20 MB, you receive a translation failure error. See ORABPEL-15235 Translation Failure Occurrence in Using the REST Adapter with Oracle Integration 3.

  • 1 GB for incoming content as raw bytes (application/octet-stream as content type)

  • 100 KB for JSON sample files used to specify the response payload format in the Adapter Endpoint Configuration Wizard

For invoke configurations

  • 3 MB for XML documents used for data definition generation

    See REST Adapter Capabilities.

  • 100 KB for JSON sample files used to specify the request payload format in the Adapter Endpoint Configuration Wizard

  • 1 GB for responses returned as part of invoke runtime binary data (application/octet-stream)

  • 50 MB for responses returned from agent-based endpoints for structured content (for example, JSON/CSV/XML, and so on)

  • 100 MB for responses returned from private endpoints for structured content (for example, JSON/CSV/XML, and so on)

  • 100 MB for responses returned from public internet-based endpoints for structured content (for example, JSON/CSV/XML, and so on)

REST-based adapters (adapters that expose REST endpoints on the inbound or adapters invoking external REST endpoints)

For example, Oracle Commerce Cloud Adapter, Oracle Fusion Field Service Adapter, and so on.

For trigger configurations (wherever applicable)

  • 3 MB for XML documents used for schema generation

    See REST Adapter Capabilities.

  • 1 GB for messages with attachments (for example, multipart/mixed and multipart/form-data)

  • 100 MB for incoming structured message payloads (any content-type header containing JSON, XML, HTML, YAML, or YML)

  • 1 GB for incoming content as raw bytes (application/octet-stream as content type)

  • 100 KB for JSON sample files used to specify the response payload format

For invoke configurations (wherever applicable)

  • 3 MB for XML documents used for data definition generation

    See REST Adapter Capabilities.

  • 1 GB for attachments in outbound requests

  • 100 KB for JSON sample files used to specify the request payload format

  • 50 MB for agent-based endpoints

  • 100 MB for private endpoints

  • 100 MB for public internet-based endpoints
Salesforce Adapter
SAP Adapter

  • 50 MB

    For the SAP Adapter as a trigger connection, the limit is 50 MB for all document types.
SAP Ariba Adapter See SAP Ariba Adapter Restrictions.
SOAP Adapter

For trigger configurations

  • 100 MB for structured payloads (XML) in requests and responses

For invoke configurations

  • 100 MB for structured payloads (XML) in requests and responses
  • 50 MB for agent-based endpoints
  • 100 MB for private endpoints
  • 100 MB for public internet-based endpoints

SOAP-based adapters (adapters that expose SOAP endpoints on the inbound or adapters invoking external SOAP endpoints)

For example, Oracle Logistics Adapter.

For trigger configurations (wherever applicable)

  • 100 MB for structured payloads (XML) in requests and responses

For invoke configurations (wherever applicable)

  • 100 MB for structured payloads (XML) in responses
  • 50 MB for agent-based endpoints
  • 100 MB for private endpoints
Connectivity-agent-based outbound adapter invocation timeout
  • 4 minutes for connection timeout
Outbound adapter invocation timeout
  • READ timeout: 5 minutes
  • Connection timeout: 5 minutes
Integration timeout for:
  • Oracle Autonomous Data Warehouse Adapter
  • Oracle Autonomous Transaction Processing Adapter
  • Oracle Database Cloud Service Adapter
  • MySQL Adapter
  • Microsoft SQL Server Adapter
  • Oracle Database Adapter
  • IBM DB2 Adapter

  • 240 seconds

    Any integrations created after August 2021 that include stored procedure or PureSQL database operations will time out after this limit.