iFlowKit Core
iFlowKit Core is a CPI-friendly Groovy toolkit for building SAP Cloud Integration logic as reusable and testable software components.
Instead of copying scripts across iFlows, iFlowKit introduces a package and plugin model that lets teams organize integration logic with clearer structure, build rules and runtime configuration.
Status
iFlowKit Core is pre-1.0. Current repository version is 0.5.0, and public APIs may change before 1.0.
What it provides
- Core runtime: package context, tenant model, credentials, URL builders and message utilities.
- Plugins: reusable libraries such as Email and Units.
- Packages: CPI-ready units that declare systems, services, plugins and credentials through a manifest.
- System catalogs: system definitions and service assets that packages can include.
- SAP stubs: compile-time stubs that make local build/test workflows possible outside CPI.
Why teams use it
Typical CPI projects accumulate duplicated Groovy snippets, hard-coded endpoints and manual environment-specific changes. iFlowKit helps teams move toward:
- package-driven reuse
- manifest-driven composition
- tenant-aware configuration
- local compilation and safer validation
- clearer separation between reusable code and runtime environment details
Core workflow
- Define a package under
packages/{packageCode}/. - Declare required systems, services, plugins and credentials in
iflowkit/package.json. - Build the package with Gradle.
- Use the resulting JAR in CPI runtime flows.
- Keep package code versioned and reviewable in Git.
bash
gradle clean buildPkg -Ppkg=iflowkit-email