Skip to Content
0
Former Member
Aug 04, 2016 at 08:40 AM

Extending Module Chain for SAP PI Adapters

299 Views

Hi All,

Our customer wants to go to SAP PI from another ESB, but he also wants to temporarily retain legacy monitoring system, where business users can see statuses of processing key-business scenarios.

In most cases the customer uses asynchronous dataflows like JMS-to-SAP or SAP-to-JMS.

My idea is to create custom-adapter module, which will get message payload and send it to legacy monitoring system. Then I plan to set this custom-module in sender adapter and twice in receiver adapter, one time before adapter module and the second time after adapter module. For example for JMS receiver communication channel it should look like:

  1. my custom adapter module
  2. specific adapter module (in case with JMS it is CallSapAdapter)
  3. my custom adapter module


But I am not sure if it is possible to set my custom module after adapter module in asynchronous receiver adapter, I concern that it will be unachievable and message processing finishes right after CallSapAdapter.

Could anybody prove or disprove my concern?

Any thoughts or other suggestions how to organize the proposed task welcome.

Thank you in advance.