Integration service instances

• 200 service instances per region

  Note: This value is the number of service instances you provision per region, and not the number of integration instances (for example, application and schedule) that you activate and monitor under the Observability tab in Oracle Integration.

  The ability to create service instances outside your home region depends on several factors. See Restrictions.

Private endpoints

• 1 private endpoint per service instance

• 1 subnet per private endpoint

Custom endpoints

• 1 custom endpoint per service instance

Oracle Integration internal diagnostic logs

• 30 days - retained in Oracle Cloud Infrastructure Logging for debugging use

  See Logging Analytics.

• 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

• SOAP and REST: 50 MB
• File and FTP invoke responses: 50 MB
• Other protocols: 10 MB (for example, database, JMS, MQ, Kafka, and others)

• Cloud endpoints: 100 MB (not using the connectivity agent)
• Private endpoints: 100 MB

• 1 GB

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.

For invoke configurations

Produce/Consume Message operations:

• 10 MB with schema transformation for all the outbound operations

• 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

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.

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

• 50 MB for response payloads

• 100 MB for public internet-based endpoints
• 50 MB for agent-based endpoints

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 Field Service Cloud 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

• 8 MB per batch (10,000 records)

  See Process Large Data Sets Asynchronously with Different Bulk Operations.

• 50 MB

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

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

• 4 minutes for connection timeout

• READ timeout: 5 minutes
• Connection timeout: 5 minutes

• 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.

• 800 active integrations

  See Activate an Integration in Using Integrations in Oracle Integration 3.

• 16 invocations

  For example, a parent integration (schedule integration) invokes a child integration (application integration), which in turn recursively invokes the parent integration.

  Integration entry points along the request execution path are counted towards the limit. When 16 is exceeded, it results in an error.

• 10,000 characters

This limit applies to all variables of type string, including global variables, and all functions, including concat functions used inside an assign, stitch, or mapper.

For example. a parallel action with three branches needs two extra concurrency slots for the duration of the parallel action; one branch is counted towards the original flow already obtained.

• Synchronous: 100 concurrent requests per message pack, up to a maximum of 600

  Increasing the concurrent request limit with additional message packs is useful if you have high concurrency requirements in respect to synchronous integration executions.

  For details about how concurrent request scalability is calculated, see Message Pack Usage and Synchronous Requests.

  Parallel action branches independent of the integration type (synchronous, asynchronous, and so on) count towards the concurrency limits on synchronous requests.

  For example. a parallel action with three branches needs two extra concurrency slots for the duration of the parallel action; one branch is counted towards the original flow already obtained.

• Asynchronous: No limit; the following number of requests can execute at a time, the rest are queued; 50 requests per message pack, up to a maximum of 300

  Asynchronous concurrent execution includes scheduled + triggered + connectivity agent.

• 50 integrations per service instance

• Non-error events: 20,000
• Error events: 30,000 (extra 10,000 if events are associated with errors)
• Maximum errors recorded: 2,000

After those limits are reached, events are no longer recorded in the activity stream, but they continue to be processed, and the integration instance overall state is calculated. This ensures that the integration instance state is updated in all scenarios.

• Synchronous: 5 minutes

  After that, an HTTP 502 occurs.

• Asynchronous: 6 hours

  After that, the integration instance is marked as aborted due to deadline timeout.

• Scheduled: 6 hours

  After that, the integration instance is marked as aborted due to deadline timeout.

• Read Entire File operations: 100 MB

  For files greater than 100 MB, use the Read File in Segments operation.

• Encrypt File operations: 1 GB

• Decrypt File operations: 1 GB

• 300 seconds

  After that, the integration returns a timeout error.

• 10 MB

• 10 MB for encodeReferenceToBase64(String reference) and decodeBase64ToReference(String base64Content) functions

• 1,024 characters

• Default method: 2 MB

• Customer tenancy method: 2 MB default

  This value can be increased until the maximum value supported by the Oracle Cloud Infrastructure Email Delivery Service is reached.

Both the email body and attachment are considered in calculating the total size.

See Configure Notification Emails and Email Delivery Service Capabilities and Limits.

• Default method: 10,000 emails
• Customer tenancy method: The limit is the number allowed by the Oracle Cloud Infrastructure Email Delivery Service.

See Configure Notification Emails and Email Delivery Service Capabilities and Limits.

• 15 seconds

• 20 parameters

• 120 seconds

• Scheduled or out-of-band: 1

  An out-of-band request is a run now run associated with a schedule.

• Ad-hoc: 1

  An ad-hoc request is a run now run not associated with a schedule.

• User interface: 100 requests per second per tenant and 20 requests per second per user
• Observability (instances/errors) API: 50 requests per second

• 6 hours

  After that, the integration is terminated by Oracle Integration.

  See When a Schedule Integration Instance Gets Terminated in Using Integrations in Oracle Integration 3.

• While loop: 5,000 iterations

• For-each loop: No limit

• Tracked loop iterations: 1,000 iterations

  Maximum number of iterations captured across all loops for a single instance ID for which tracking data is captured.

• Integrations: 100
• Connections: 50
• Lookups: 50
• JavaScript libraries: 20
• Deployments: 50

• 5 branches

• 8,191 characters

• Production: 32 days (default) for Standard and Enterprise editions, 184 days for Healthcare edition

  You can increase the data retention period for Standard and Enterprise editions if you want. See Edit the Data Retention Period for an Instance.

• Audit: 8 days
• Debug (Not Recommended): 24 hours

  Note: After 24 hours, Debug (Not recommended) is automatically reset to Production. See Activate an Integration in Using Integrations in Oracle Integration 3.

• It's aborted. This can happen due to integration deactivation.
• It's successfully recovered or the recovery leads to a nonrecoverable error.
• It's beyond its associated retention time, which is 32 days (default) for Standard and Enterprise editions, 184 days for Healthcare edition.

• 5,000 rows (when expanding the tree)

• No limit

• 50 instances

• 10 resubmissions

• 256 characters

• 5 parameters

• 256 characters

• Name: 50 characters
• Package name: 50 characters
• Version: 10 characters
• Description: 1,024 characters

• 500

• 50

• 2 minutes

• The same limit supported by the inbound (trigger) adapter.

  See Component: Adapters.

• 32 KB per payload

  Payloads larger than 32 KB are stored in the Object Store. There is no limit for payloads stored in the Object Store.

• 25 MB total per integration instance

• 20 deployments per gateway
• 50 routes per deployment

This allows for a total of 1,000 integration endpoints per gateway.

Robot instance duration

• 4 hours

Assigning a robot instance to an environment timeout

Varies, depending upon the environments:

• If the environment pool contains no environments:

  0 seconds, and then the status of the robot instance changes to Failed

• If the robot agent on the environment doesn't accept the request:

  30 seconds, and then Oracle Integration attempts to assign the robot instance to a different environment

• If all environments in the environment pool have a status of Unavailable:

  240 seconds, and then the status of the robot instance changes to Failed

• If at least one environment in the environment pool has a status of Available:

  No limit

File download timeout

• 180 seconds by default but the robot builder can specify a different value while creating a robot

File download size

• 50 MB

Polling frequency (frequency at which the robot agent polls Oracle Integration for work)

• 15 seconds

Maximum time that Oracle Integration waits for the robot agent to poll for work before changing its environment's status to Unavailable

• 35 seconds

Environments in an environment pool

• 100 environments

Robot character limits

• Name: 50 characters

• Description: 1,024 characters

• Keywords: 1,024 characters

Environment pool character limits

• Name: 50 characters

• Description: 1,024 characters

• Keywords: 1,024 characters

Robot connection type character limits

• Name: 50 characters

• Description: 1,024 characters

• Keywords: 1,024 characters

Robot connection character limits

• Name: 50 characters

• Description: 1,024 characters

• Keywords: 1,024 characters

• 500 GB

• 50 connections per service instance