Synchronous communication is called by a requirement and response process, and the output of the process is returned immediately after the process. In general, you can say that a synchronous scenario is when a sending process sends a request to the recipient and waits for a response. If an error occurs on the recipient`s side, the sender application is responsible for re-transmitting the message. Hello Rajiv, “but if I use the synchronous interface name in the Agreeemnt string, in determining the interface, there is no mapping operation identification” For the string agreement: so you have the same behavior with mine. Recently I tried Async/Sync Bridge with Sync REST adapter not working. This blog by Alexey Pitroff also mentioned Async/Sync Bridge with Sync RFC will not work, but the module must be used on the chain adapter. See the commentary on Figure 26 on his blog. scn.sap.com/community/pi-and-soa-middleware/blog/2014/03/27/bridges-construction-site-part-13-asynchronous-Synchron-Bridge For the determination of the interface: in this 2nd stream for OM_RFC2FILE, I use the Sync interface of the 1st stream to determine the OM, if you can get a similar result. Check your OM again.
saprainbow.com/wordpress/wp-content/uploads/2015/07/async_sync_2_id2_interface_determination.jpg Merry Christmas! 🙂 Greetings, Yee Loon Step 5 – The type of adapter can be chosen as transmitter or receiver depending on the type of communication channel. In this approach, it is possible that the sender can send the message after the time-out and there is a double message. This approach in PI is called BE (Best Effort). Network level error – There is an error in the communication network between the transmitter and receiver. The sender is not aware of this and the message remains in between and the sender waits for the time of the operation. Channel start error: com.sap.aii.af.service.cpa.impl.object.ChannelImpl@574b687d because of java.lang.NoClassDefFoundError: com/ibm/msg/client/jms/jms/jmsQueueConnectionFactory ————————- Loader Info ————————- ClassLoader name: [service:com.sap.aii.adapt.j Loader hash code: 3bbd6883 Living status: alive Direct parent loader: [system:Frame] [interface:com.sap.aii.af.ms.ifc] [service:com.sap.aii.adapt.xi.svc] [ service: com.sap.aii.adapt.xi.svc] [ Library: com.sap.aii.adapt.lib] Resources: /usr/sap/RPD/J00/j2ee/cluster/bin/services/com.sap.aii.adapter.jms.svc/lib/com.sap.aii.adapter.jms.svc_api.jar ————————————————————— Error loading com.ibm.mq.jms.MQQueueConnectionFactory Step 3 – Select the communication channel created for the sender in the Inbound Processing tab. This function consists of performing a mass migration of your communication channel between the source system and the target system, and bringing all the channel information outside the password. As with Scenario Migration, you can also rename the channel. .