This is very important to know the service limits. A service limit is the quota or a allowance set on a resource.
Follow are few of the service limits.
1. Oracle Cloud Infrastructure Console Service Limits
Resource: Integration instance countService Limit: 200 instances per region
2. Adapters
A. Timeouts for all outbound adapter invocations. The following values are set and cannot be changed:
• READ timeout is set to 5 minutes.
• Connection timeout is set to 5 minutes.
B. Oracle Autonomous Data Warehouse Adapter, Oracle Autonomous Transaction Processing Adapter, Oracle Database Cloud Service Adapter, MySQL Adapter, Microsoft SQL Server Adapter, Oracle Database Adapter, and IBM DB2 Adapter:
Starting with the August 2021 release, all new integrations that include stored procedure or PureSQL database operations must finish within 240 seconds. Otherwise, the query times out.
C. Timeouts for all connectivity agent-based outbound adapter invocations:
Connection timeout is set to 4 minutes.
D. File Adapter - file size:
10 MB.
Note:
The size of CSV files increases when translated into a message. Therefore, the file size must be less than 10 MB, so that the after-translation message size does not exceed 10 MB.
E. FTP Adapter - file size
For invoke configurations
Read File operation:
• 1 GB when used without a schema (with a connectivity agent).
• 10 MB when using a schema for transformation.
Write File operation:
• 1 GB when used without a schema (with a connectivity agent).
• 10 MB when using a schema for transformation.
Download File operation: 1 GB.
F. AS2 Adapter - file size limit
10 MB
G. REST Adapter
For trigger configurations
• XML document size for schema generation: 3 MB. See REST Adapter Capabilities.
• Incoming message size (without attachment): 10 MB. Messages with attachments, for example, multipart/mixed and multipart/form-data, are not subject to this constraint.
• Incoming JSON attachments size: 1 GB.
• Incoming structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML): 10 MB.
• Incoming content as raw bytes (application/octet-stream as content type): 1 GB.
• Specifying the response payload format: JSON sample files of up to 100 KB in size are supported.
For invoke configurations
• XML document size for data definition generation: 3 MB. See REST Adapter Capabilities.
• Attachment size in outbound requests: 1 GB. These attachments can be multipart/mixed, multipart/form-data, or application/octet-stream.
• Outgoing structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML): 10 MB.
• Outgoing unstructured message payload size (multipart/form-data and binary/octet-stream): 1 GB.
• Specifying the request payload format: JSON sample files of up to 100 KB in size are supported.
H. 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 Adapter, etc.)
For trigger configurations (wherever applicable)
• XML document size for schema generation: 3 MB. See REST Adapter Capabilities.
• Incoming message size (without attachment): 10 MB. Messages with attachments, for example, multipart/mixed and multipart/form-data, are not subject to this constraint.
• Incoming JSON attachments size: 1 GB.
• Incoming structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML): 10 MB.
• Incoming content as raw bytes (application/octet-stream as content type): 1 GB.
• Specifying the response payload format: JSON sample files of up to 100 KB in size are supported.
For invoke configurations (wherever applicable)
• XML document size for data definition generation: 3 MB. See REST Adapter Capabilities.
• Attachment size in outbound requests: 1 GB. These attachments can be multipart/mixed, multipart/form-data, or application/octet-stream.
• Outgoing structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML): 10 MB.
• Outgoing unstructured message payload size (multipart/form-data and binary/octet-stream): 1 GB.
• Specifying the request payload format: JSON sample files of up to 100 KB in size are supported.
I. Salesforce Adapter - batch file size
For trigger configurations
• XML document size for schema generation: 3 MB. See REST Adapter Capabilities.
• Incoming message size (without attachment): 10 MB. Messages with attachments, for example, multipart/mixed and multipart/form-data, are not subject to this constraint.
• Incoming JSON attachments size: 1 GB.
• Incoming structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML): 10 MB.
• Incoming content as raw bytes (application/octet-stream as content type): 1 GB.
• Specifying the response payload format: JSON sample files of up to 100 KB in size are supported.
For invoke configurations
• XML document size for data definition generation: 3 MB. See REST Adapter Capabilities.
• Attachment size in outbound requests: 1 GB. These attachments can be multipart/mixed, multipart/form-data, or application/octet-stream.
• Outgoing structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML): 10 MB.
• Outgoing unstructured message payload size (multipart/form-data and binary/octet-stream): 1 GB.
• Specifying the request payload format: JSON sample files of up to 100 KB in size are supported.
H. 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 Adapter, etc.)
For trigger configurations (wherever applicable)
• XML document size for schema generation: 3 MB. See REST Adapter Capabilities.
• Incoming message size (without attachment): 10 MB. Messages with attachments, for example, multipart/mixed and multipart/form-data, are not subject to this constraint.
• Incoming JSON attachments size: 1 GB.
• Incoming structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML): 10 MB.
• Incoming content as raw bytes (application/octet-stream as content type): 1 GB.
• Specifying the response payload format: JSON sample files of up to 100 KB in size are supported.
For invoke configurations (wherever applicable)
• XML document size for data definition generation: 3 MB. See REST Adapter Capabilities.
• Attachment size in outbound requests: 1 GB. These attachments can be multipart/mixed, multipart/form-data, or application/octet-stream.
• Outgoing structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML): 10 MB.
• Outgoing unstructured message payload size (multipart/form-data and binary/octet-stream): 1 GB.
• Specifying the request payload format: JSON sample files of up to 100 KB in size are supported.
I. Salesforce Adapter - batch file size
8 MB (10,000 records).
J.SOAP Adapter
For trigger configurations
• Structured payload (XML) size in Request and Response: 10 MB.
For invoke configurations
• Structured payload (XML) size in Request and Response: 10 MB.
• MTOM attachment (binary and non-binary content) size in Request and Response: 1 GB.
K. 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)
• Structured payload (XML) size in Request and Response: 10 MB.
For invoke configurations (wherever applicable)
• Structured payload (XML) size in Request and Response: 10 MB.
• MTOM attachment (binary and non-binary content) size in Request and Response: 1 gb
For trigger configurations
• Structured payload (XML) size in Request and Response: 10 MB.
For invoke configurations
• Structured payload (XML) size in Request and Response: 10 MB.
• MTOM attachment (binary and non-binary content) size in Request and Response: 1 GB.
K. 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)
• Structured payload (XML) size in Request and Response: 10 MB.
For invoke configurations (wherever applicable)
• Structured payload (XML) size in Request and Response: 10 MB.
• MTOM attachment (binary and non-binary content) size in Request and Response: 1 gb
L. Database Adapters (Oracle Database Adapter, IBM DB2 Adapter, Microsoft SQL Server Adapter, MySQL Adapter, Oracle Autonomous Data Warehouse Adapter, Oracle Autonomous Transaction Processing Adapter, and Oracle Database Cloud Service Adapter)
For trigger configurations
• Polling Operation: 10 MB with schema transformation.
For invoke configurations
• Stored Procedure/Operation on Table/Run PureSQL Statement Operations: 10 MB with schema transformation for all the outbound operations.
M. Apache Kafka Adapter
For invoke configurations
• Produce/Consume Message Operations: 10 MB with schema transformation for all the outbound operations.
N. JMS Adapters (Oracle WebLogic JMS Adapter and IBM MQ Series JMS Adapter)
For trigger configurations
• Consume Message Operation: 10 MB with schema transformation.
For invoke configurations
• Produce Message Operation: 10 MB with schema transformation.
O. Oracle CPQ Cloud Adapter - response payload
For trigger configurations
• Polling Operation: 10 MB with schema transformation.
For invoke configurations
• Stored Procedure/Operation on Table/Run PureSQL Statement Operations: 10 MB with schema transformation for all the outbound operations.
M. Apache Kafka Adapter
For invoke configurations
• Produce/Consume Message Operations: 10 MB with schema transformation for all the outbound operations.
N. JMS Adapters (Oracle WebLogic JMS Adapter and IBM MQ Series JMS Adapter)
For trigger configurations
• Consume Message Operation: 10 MB with schema transformation.
For invoke configurations
• Produce Message Operation: 10 MB with schema transformation.
O. Oracle CPQ Cloud Adapter - response payload
10 MB.
3. Integrations:
A. 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.
B. Connectivity agent - message payload
10 MB, through the use of compression.
All connectivity-agent-enabled adapters
• 10 MB as request.
• 10 MB as response.
SOAP and REST adapters configured with connectivity agent
• 10 MB (structured XML/JSON document) as request.
• 10 MB (structured XML/JSON document) as response from private SOAP/REST endpoints.
• 1 GB for attachments as part of a request.
• 1 GB for attachments as part of a response from private SOAP/REST endpoints.
C. Stage File action (in orchestrated integrations) - file size
Read Entire File operation: 10 MB. For files greater than 10 MB, use the Read File in Segments operation.
Encrypt File operation: 1 GB.
Decrypt File operation: 1 GB.
D. Synchronous integration message timeout
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.
B. Connectivity agent - message payload
10 MB, through the use of compression.
All connectivity-agent-enabled adapters
• 10 MB as request.
• 10 MB as response.
SOAP and REST adapters configured with connectivity agent
• 10 MB (structured XML/JSON document) as request.
• 10 MB (structured XML/JSON document) as response from private SOAP/REST endpoints.
• 1 GB for attachments as part of a request.
• 1 GB for attachments as part of a response from private SOAP/REST endpoints.
C. Stage File action (in orchestrated integrations) - file size
Read Entire File operation: 10 MB. For files greater than 10 MB, use the Read File in Segments operation.
Encrypt File operation: 1 GB.
Decrypt File operation: 1 GB.
D. Synchronous integration message timeout
300 seconds.
Synchronous integrations (integrations that return a response payload) return a timeout error if they run more than 300 seconds.
E. Oracle Integration Messaging - message size
Synchronous integrations (integrations that return a response payload) return a timeout error if they run more than 300 seconds.
E. Oracle Integration Messaging - message size
10 MB.
F. Encode and Decode File Attachment Content (mapper)
The functions encodeReferenceToBase64(String reference) and decodeBase64ToReference(String base64Content) have a file size limit of 10 MB.
4. File Server
Storage: 500 GB.
Storage: 500 GB.
Concurrent connections: Maximum of 20 connections per service instance
Oracle doc reference:
No comments:
Post a Comment