Skip to Content
Technical Articles

Cloud Integration – Content Size Limits

This blog describes the resource and size limits of the integration flow content that can be deployed in Cloud Platform Integration. It describes the limits apply and gives some guidance on how to optimize the overall integration flow development.

Size Limits:

The total size of all integration flows deployed on a single tenant would be 500 MB which would apply even for the dependencies like scripts, JAR etc…

Recommendations to reduce the content size:

  1. Remove unused integration flows and resources

Remove integration flows and their resources (Groovy/Java script, EDMX, Jar) from the tenant which are not used by un-deploying and deleting it from your design workspace, if applicable.

  1. Use ProcessDirect adapter to Re-use of integration flows by multiple integration processes

The large mapping or other resources (Groovy/Java script, EDMX, Jar) that are repeated in multiple integration flows can be placed in a single integration flow, which can be called with process direct adapter from the main integration flows.

Here is an example:

  • Multiple Integration flows using same mapping and script

  • Flows optimized with the usage of process direct adapter
    • Flow1 with mapping and script resources
    • Flow2 calling Flow1 using process direct adapter. Mapping and script resources can be removed.
    • Flow2 calling Flow1 using process direct adapter. Mapping and script resources can be removed.

For detailed information on the ProcessDirect adapter usage and benefits.

Refer Help Documentation.

 

Conclusion:

Design your integration flows following the above guidelines, so that the content size of the integration flows doesn’t exceed the limits of CPI. 

Be the first to leave a comment
You must be Logged on to comment or reply to a post.