This solution provides you with a snapshot of your cloud integration tenant listing all error messages belonging to the running Integration Flows.
- Read Message-Processing Information (errors)
- Filter results by threshold configuration
- Deliver Alert E-Mails to different receivers
The tool runs periodically (e.g. every hour) and reads all error messages of a configured period (e.g. last 90 minutes). You can define the recipients per iFlow and segregate the responsibilities:
- email@example.com for all SAP Cloud for Customer iFlows in error
- firstname.lastname@example.org for all Success Factors iFlows in error
- email@example.com for all eDocuments related iFlows in error (such as SII)
WHINT Interface Monitoring helps to inform the responsible parties and allow a follow-up handling.
The solution is using the Standard OData API of SAP CPI and can be deployed on your CPI tenant as an Integration Package or provided as a service (where we would receive read access from our SAP CPI tenant).
You can decide if an e-mail is always generated (like a heartbeat) or only if errors occurred.
- Import the ZIP file (Integration Package) provided by Whitepaper InterfaceDesign as an Integration Package into your tenant
- Configure the alert receiver integration flow (see Configuration Guide)
- Configure the main integration flow
- Create a dedicated API user to access the CPI Monitoring and Administration.
- Required Roles: IntegrationOperationServer.read, AuthGroup.IntegrationDeveloper
- Create the User Credentials
- Manage Security Material -> Add User Credentials
3. Configure iFlow WHINT IMS Alert Configuration
4. Enter the E-mail receiver address(es) with e-mail subject and iFlows (using Regex) to monitor (enter .* to monitor all iFlows)
5. Configure iFlow WHINT IMS CPI
6. Enter the runtime URL (iflmap) of your tenant (taken from the deployed alert configuration artifact)
7. Enter the tenant URL (tmn) of your tenant (taken from the browser URL)
8. Select the threshold times
9. Select the timer configuration (when the snapshot shall be created)
10. Deploy the integration flow