cpi-iflow-developmentlisted

# SAP CPI iFlow Development Full development lifecycle for SAP Cloud Integration (CPI) iFlows — from source code to deployed integration. ## Prerequisites - SAP BTP subaccount with Integration Suite enabled - Service Key for Process Integration Runtime (OAuth2 client_credentials) - Environment vars set: `CPI_TENANT_URL`, `CPI_TOKEN_URL`, `CPI_CLIENT_ID`, `CPI_CLIENT_SECRET` - Groovy 2.4+ syntax knowledge (CPI uses Nashorn engine, ECMAScript 5.1 dialect) - Access to CPI Web UI for monitoring and trace ## iFlow ZIP Structure ``` my-iflow.zip/ ├── META-INF/MANIFEST.MF └── src/main/resources/ ├── flow.xml ← Main integration flow definition ├── script/*.groovy ← Groovy scripts ├── mapping/*.xslt ← XSLT transformations ├── mapping/*.mmap ← Message mappings ├── resources/*.xsd ← EDI/XML schemas └── parameters.prop ← Externalized parameters ``` ## Step 1 — Create iFlow Source Files Create the project directory and core files: ```bash mkdir -p iflows/my-integration-flow/{src/main/resources/script,src/main/resources/mapping} ``` Write the `MANIFEST.MF`: ``` Manifest-Version: 1.0 Bundle-SymbolicName: my_integration_flow Bundle-Version: 1.0.0 Bundle-Name: My Integration Flow ``` ## Step 2 — Write flow.xml Define sender channel, integration process steps, and receiver channel: ```xml <IntegrationFlow id="my_integration_flow" version="1.0"> <Sender id="sender_1" type="HTTPS" directio