Asynchronous
Communication
Use
XI runtime is designed for asynchronous communication. This type of communication is recommended for updates in order to avoid data inconsistencies. Simple asynchronous communication is supported in the default setting and is recognizable from the communication parameters of the interfaces involved. One protocol supports further services (exactly once in order, acknowledgments).
Integration
Monitoring supports monitoring of asynchronous communication. In monitoring, you can resend any messages that could not be sent to the receiver.
See also: Displaying and Managing Messages.
Features
General
Proxy runtime gathers together all calls from asynchronous client proxies and sends the corresponding messages after the COMMIT WORK statement (see also: Sending a Message). As with synchronous communication, you must at least catch the exception CX_AI_SYSTEM_FAULT. On the receiver side, you can catch application errors to persist them for monitoring (see also: Error Handling).
Client Proxy in Update Task
If the application data is updated by the addition IN UPDATE TASK, the client proxy must also be called in the update. If this is not the case, the qRFC queue may become blocked when an update is terminated, because the update task is not complete. Due to the dependencies of different queues, this can slow or block the entire outbound processing.
Protocol IF_WSPROTOCOL_ASYNC_MESSAGING
The protocol supports the following
· Exactly Once in Order by using a serialization context