Central Adapter Engine to De-Central Adapter Engine Configuration

[Former Member]

Hi Experts,

We have a requirement where, in configuring an ICO (Pass through Scenario), the sender Communication channel is of Central Adapter Engine and the corresponding receiver is one with De-Central Adapter Engine. While configuring it this way, we see an Error that says 2 Engines cannot be configured in a single ICO.

Could someone please suggest if it is possible and we went wrong somewhere?

If this type of configuration is possible, please suggest the procedure to be followed.

Thanks,

Manasa.

[vadimklimov]

Hello Manasa,

Currently Java-only scenarios cannot use communication channels running in different Adapter Engines, within a single ICo/iFlow, so you may use some workarounds:

• Pass through scenario which consists of two ICos/iFlows: the first ICo/iFlow runs on central AAE (sender channel is per scenario requirement, receiver channel is for example SOAP based and uses endpoint of an ncAAE in target URL), the second ICo/iFlow runs on non-central AAE (sender channel is SOAP based and exposes the endpoint called by the receiver channel used in the first ICo/iFlow, receiver channel is per scenario requirement),
• Invoke another required channel from the given channel at runtime using adapter module ModuleSequencerBean - the approach is described by in the blog .

Regards,

Vadim

[Former Member]

Thank you for your quick response Vadim.

Is it only SOAP adapter we can use in first case? or is it possible with other adapters too?

If it is just SOAP, based on what can we determine the URL to be configured in SOAP Channel?

2nd point isn't applicable in our case as we are in PI 7.3, dual stack

Regards,

Manasa

[vadimklimov]

Manasa, the first alternative is not only limited to usage of SOAP adapter - other adapters can be used, too. Just usage of SOAP adapter may be the most straightforward and not requiring additional intermediate steps, since the receiver channel of the first ICo will directly invoke sender channel of the second ICo.

As for URL, it can be derived from the SOAP sender channel properties based on a generic URL pattern, as described in Configuring the Sender SOAP Adapter - Advanced Adapter Engine - SAP Library (in case you use SOAP-HTTP). You may also want to try SOAP-XI as a derivative of this alternative.

Regarding ModuleSequencerBean, it shall be possible to use it in both dual stack and Java-only installations.

Regards,
Vadim