This blog describes the resource and size limits of the integration flow content that can be deployed in SAP Cloud 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:
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.
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:
For detailed information on the ProcessDirect adapter usage and benefits.
Refer Help Documentation.
Additional considerations:
Conclusion:
Design your integration flows following the above guidelines, so that the content size of the integration flows doesn't exceed the limits of SAP Cloud Integration.
Note: Obtaining the content size directly is not possible; one would need to download the entire content from the tenant and then assess its size.
Contact SAP to determine the suitable sizing for larger content size needs by raising a support ticket on OPS component (LOD-HCI-PI-OPS)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
20 | |
10 | |
9 | |
7 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 |