We have lately shipped a new version of the Pipeline Concept package on the SAP Business Accelerator Hub based on customer and partner feedback, this is now version 1.0.5. The package can be accessed from here. If you have already copied the package to your workspace in your SAP Integration Suite tenant, you can simply run the update of the package to be able to use the latest features.
As part of the package, we have now added a change list which allows you to see all increments that we have shipped so far. In the latest version, we have delivered the following:
- Extension for custom error handling
- In generic IDoc inbound processing flow, display list of IDoc numbers in case of IDoc bulk messages
- For IDoc inbound, sender interface is calculated as a combination of MESTYP, IDOCTYP and CIMTYP
- Supporting test mode via testMode header in the allowed headers configuration
- In standard error handling, copied messages from the dead letter queue are switched to DEBUG log level
The custom error handling extension is a sort of customer exit which allows you to implement your own error handling in a separate integration flow which is then called via ProcessDirect instead of the standard error handling if the standard error handling doesn't meet your requirements. This way you can customize the pipeline processing without changing the generic integration flows that we ship as part of the pipeline concept. For more details, see Monitoring and Error Handling in the Pipeline Concept.
For improved monitoring of IDoc bulk messages, all IDoc numbers are stored in a custom header property. This allows you to search the message processing logs in the message monitoring based on a particular IDoc number. Furthermore we have revised the sender interface for IDoc messages. Before it contained the message type only, now it's a combination of the message type, the IDoc type and a potential IDoc extension which brings you more flexibility in setting up your IDoc scenarios. See Special Cases.
If you like to run your integration scenarios using a regression test tool, you may benefit from the test mode flag. This is simply a header which is passed through the whole sequence of pipelines. Depending of your test case setup you may then pass the test message to a virtualized or mocked receiver instead of to the actual receiver. By the way, our partners providing regression test tools already support the pipeline concept in their tools. See Testing the Pipeline.
We are currently working on the next increment. For the test flag for instance we plan to extend the generic flows so that test messages which go into an error won't be restarted. Furthermore, we plan to extend the partner directory approach that is used to dynamically configure the runtime behavior. In some cases, the partner ID which is limited to 60 chars might not be sufficient, so we need to react on this. Furthermore, we like to provide you the option to use alternative partners which provides you more flexibility in setting up your integration scenarios, e.g., with this, sender wildcard scenarios can be easily setup.
So, stay tuned. And if you have further ideas, requirements, feedback feel free to reach out to me or simply leave a comment.
Bluesky
