System Scope and Resource Optimization in SAP Cloud Integration
In this lesson, you will learn about the system scope for Cloud Integration tenants deployed in the Cloud Foundry environment. You will also discover recommendations for optimizing resources when system limits are exceeded.
System Scope Overview
The following table outlines the default resource limits for the Cloud Integration tenants and provides guidance on optimizing these resources.
| Resource | Default Scope | Recommendations |
| Integration Content | 500 MB | Review the Content Size Limits blog for tips on reducing integration content size. |
| JMS Queues | Default: 9 GB, 150 transactions (30 queues) | JMS Resource and Size Limits: Learn to set queue size limits and delete unused queues. |
| Scalable: Upto 30 GB, 500 transactions (100 queues) | ||
| Message Processing Log Persistence | 35 GB | See: Setting the Log Level for Message Processing |
| Runtime Database | 35 GB | Optimize database performance. Refer to Optimize Performance. |
| Disk Space | 4 GB | Avoid "No More Space Left on Disk" errors. Refer to SAP Note 2648415. |
Optimizing Resources
Integration Content
- Regularly monitor the size of integration content to ensure it stays within the 500 MB limit.
- Delete unused or outdated integration flows.
- Refer to the SAP Blog on Content Size Limits for detailed strategies to reduce integration content size effectively.
JMS Queues
- By default, you cannot utilize 9 GB of space for JMS queues with 150 transactions across 30 queues.
- To scale, increase the limit to 30 GB with 500 transactions across 100 queues.
- Manage queue sizes by restricting limits to avoid overflow and deleting unused queues to free up resources.
- For guidance, consult the SAP Blog on JMS Resources and Size Limits or visit the admin course for the SAP BTP.
Message Processing Log Persistence
- Logs occupy up to 35 GB of storage.
- Set appropriate log levels to minimize unnecessary storage usage. See the blog on Setting the Log Level for Message Processing for step-by-step instructions.
Runtime Database
- The runtime database is limited to 35 GB.
- Optimize performance by:
- Regularly cleaning up outdated data.
- Referring to SAP documentation on Optimize Performance.
Disk Space
- Disk space is limited to 4 GB.
- Prevent errors like "Not More Space Left on Disk" by optimizing integration flow development by following the SAP Note 2648415 for best practices.
Summary
SAP Cloud Integration (Cloud Foundry) operates within predefined system scope limits for resources such as integration content, JMS queues, logs, runtime database, and disk space. Efficient resource optimization is crucial to ensure smooth operations and prevent errors.
SAP offers detailed guidance and monitoring tools to help manage and scale resources effectively. For further details, refer to the section on Data Storage Features.