Based on #1, I feel like there might be a gap in the way that response messages are processed.This approach is consistent with this document: Async/Sync and Sync/Async Bridge Scenarios: Configuring Async/Sync Bridge and Sync/Async Bridge without BPM. When I tried this on a PI 7.1 and 7.3 system, I found that the AAE could not resolve the response from the synchronous request (I called a BAPI via the RFC adapter) unless I proposed the synchronous interface as the sender. In the screenshot you have for the integrated configuration in the second leg of the exchange, I see that you have the asynchronous placeholder interface as the sender interface.I tried this out and found that it works pretty well. Everything worked just as well without making any other changes. Then I replace the File communication channels with JMS communication channels. Note: All other configurations are the same as the standard configurations.įor my testing, I used (on the sender side) a File sender communication channel and a File receiver communication channel. The receiver is the business system/component to receive the response. When creating the ICO (or iFlow), you must specify a receiver.In this example, it is an asynchronous SOAP sender communication channel. The sender communication channel must be an asynchronous sender.Asynchronous outbound response interface of the receiver (#4) –> Asynchronous inbound response interface (#2) :.Note: The rest of the configurations are the same as the standard configurations. ResponseOnewayBean module: replaceInterface = true.ResponseOnewayBean module: interfaceNamespace = interface namespace for #4 above.ResponseOnewayBean module: interface = interface name for #4 above.RequestResponseBean: passThrough = true.The Module Key’s Parameter Names and Values are: The Module Key can be any name you want.AF_Modules/ResponseOnewayBean (Module Key: ResponseOnewayBean module).AF_Modules/RequestResponseBean (Module Key: RequestResponseBean).The synchronous Receiver Communication Channel needs to have the following module configurations added (example of a SOAP web service):.For Operations Mapping, only the request message type needs to be mapped.Asynchronous outbound request interface (#1) –> Synchronous inbound interface (#3).The following Integrated Configurations (or iFlows) are needed: Asynchronous outbound response interface from the Receiver (this interface should be based on the response message of the synchronous interface in #3).Synchronous inbound interface to the Receiver.
Asynchronous inbound response interface from the Receiver side.Asynchronous outbound request interface from the Sender side.This means for JMS, we will not have to deal with all the special JMS async-sync bridge configurations you will only need to configure JMS communication channel as a “normal” configuration.īelow denotes the basic integration flows: The configuration is generic therefore, we can use any asynchronous communication channels without any other changes. In this blog, we will take a look at another configuration option that can use the async-sync bridge, but without any JMS-type of dependencies. These parameters are not valid or available for other types of adapters that can process asynchronous messages, e.g.
The configuration involves JMS specific parameters, e.g. The configuration is well documented in SAP Help and various blogs and documents on SCN. PI provides async-sync bridge for the JMS adapter.
0 kommentar(er)
