Integration service instance count

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.

Service instance creation

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

Private endpoint limits

Custom endpoints - maximum number

1 custom endpoint

Oracle Integration internal diagnostic logs retention in Oracle Cloud Infrastructure Logging

Retained for 30 days for debugging use.

See Logging Analytics.

For file and FTP with the connectivity agent, the limit for an invoke response is 50 MB for structured payloads.

For any other protocol (for example, database, JMS, MQ, Kafka, and others), the payload limit is 10 MB for structured payloads.

• 1 GB when used without a schema (with the connectivity agent)
• 50 MB when using a schema for transformation
• 50 MB for a read operation with structured payload (The File Adapter is only available with connectivity agent.)

Polling with the connectivity agent: 50 MB

Download File operation: 1 GB

For invoke configurations

Read File operation:

Download File operation: 1 GB (when used both with or without a connectivity agent).

Write File operation: There is no limit.

For trigger configurations

For invoke configurations

For trigger configurations (wherever applicable)

For invoke configurations (wherever applicable)

For trigger configurations

For invoke configurations

For trigger configurations (wherever applicable)

For invoke configurations (wherever applicable)

For trigger configurations

For invoke configurations

For trigger configurations

For invoke configurations

For invoke configurations

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

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

• READ timeout is set to 5 minutes.
• Connection timeout is set to 5 minutes.

See SAP Ariba Adapter Restrictions.

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.

10 MB, through the use of compression.

All connectivity-agent-enabled adapters

SOAP and REST adapters configured with connectivity agent

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

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.

The limit is applicable to all variables of type string, including global variables. The limit is also applicable to all functions, including a concat function 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: A maximum of 600 concurrent requests. Users receive 100 concurrent requests per message pack. This concurrent request increase 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.

• Asynchronous: No limit (50 at a time can execute, the rest are queued).

• 20,000 for non-error events
• 30,000 for error events (extra 10,000 if events are associated with errors)
• 2000 max error recorded

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.

• Asynchronous: Six hours (The integration instance is marked as aborted due to deadline timeout.)
• Scheduled: Six hours (The integration instance is marked as aborted due to deadline timeout.)
• Synchronous: Five minutes (An HTTP 502 occurs.)

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

Encrypt File operation: 1 GB.

Decrypt File operation: 1 GB.

Synchronous integrations (integrations that return a response payload) return a timeout error if they run more than 300 seconds.

• If using the default method: 2 MB.
• If using your customer tenancy: A default value of 2 MB that 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.

• If using the default method: 10,000 emails.
• If using your customer tenancy: Sets your limit to the number allowed by the Oracle Cloud Infrastructure Email Delivery Service.

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

• Synchronous concurrent request: 100.
• Asynchronous concurrent executions: 50.

  Asynchronous concurrent execution includes scheduled + triggered + connectivity agent.

Note: There is no limit for a for-each loop.

• 100 integrations, 20 connections, 50 lookups, and 20 JavaScript libraries per project.
• 50 deployments per project.

• Production: 32 days for Standard and Enterprise editions, 184 days for Healthcare edition
• 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 is aborted. This can happen due to integration deactivation.
• It is successfully recovered or the recovery leads to a nonrecoverable error.
• It is beyond its associated retention time, which is 32 days (default) for Standard and Enterprise editions, 184 days for Healthcare edition.

See Manage Trading Partners and Track B2B Messages in Using B2B for Oracle Integration 3.

Maximum duration for a robot instance

4 hours.

Timeout for assigning a robot instance to an environment

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.

Maximum wait time for downloading a file

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

Maximum file size for downloading a file

50 MB.

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.

Maximum number of environments in an environment pool

100 environments.

Character limits for robots

• Name: 50 characters.

• Description: 1024 characters.

• Keywords: 1024 characters.

Character limits for environment pools

• Name: 50 characters.

• Description: 1024 characters.

• Keywords: 1024 characters.

Character limits for robot connection types

• Name: 50 characters.

• Description: 1024 characters.

• Keywords: 1024 characters.

Character limits for robot connections

• Name: 50 characters.

• Description: 1024 characters.

• Keywords: 1024 characters.