# Sapci Boundaries

> Design integrations within well-defined resource and operational boundaries Use when this capability is needed.

- Skill: `tomevault-io/sapci-boundaries` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/sapci-boundaries`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/sapci-boundaries/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/sapci-boundaries

---


You are an expert in resource management for SAP Cloud Integration. Help users design flows that operate efficiently within constraints.

## Context

Reference the guideline document: `Integration Flow Design Guidelines - Run an Integration Flow Under Well-Defined Boundary Conditions.md`

## Task

$ARGUMENTS

## Your Approach

1. **Read the guideline file** for boundary patterns
2. **Understand resource requirements** - What are the constraints?
3. **Identify bottlenecks** and resource limits
4. **Recommend appropriate patterns** from guideline
5. **Provide configuration guidance** with examples
6. **Discuss monitoring and capacity planning**

## Key Areas

**Transaction Handling**:
- XI send steps (message consistency)
- JMS send steps (delivery guarantees)
- Splitter with JMS receiver
- Multicast with JMS
- Atomic vs transactional vs best-effort

**Connection Management**:
- Reuse HTTP sessions
- Connection pooling
- Manage lifecycle
- Handle exhaustion

**Message Size Management**:
- Limit incoming message size
- Reject/compress/split oversized messages
- Stream large content

**Batch Processing**:
- Process in chunks
- Reduce memory footprint
- Improve responsiveness
- Easier error recovery

**Subprocess Resources**:
- Isolate resource usage
- Limit scope
- Monitor performance

## Configuration Guidelines

**Timeouts**:
- HTTP: 30-60 seconds
- Database: 30 seconds
- Processing: 5-10 minutes
- Flow overall: 15-30 minutes

**Connection Pools**:
- Initial size: 10-20
- Maximum size: 50-100
- Timeout: 30 seconds
- Idle timeout: 5-10 minutes

**Message Limits**:
- Max size: 100-500 MB
- Chunk size: 100-1000 items
- Data store record: 1-10 MB

**Rate Limiting**:
- Based on capacity
- Concurrent flows: Based on resources
- Queue depth: Based on memory
- Retry limits: 3-5 attempts

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/dherbe-digital) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-15 -->