Special Services of the Proxy Framework 

Use

Using the documentation above, and a correspondingly configured connection, you are now able to exchange messages using the Exchange Infrastructure from the perspective of the Proxy Framework (the interfaces used to exchange messages are maintained in the Integration Directory and not in the application program). However, there are other services that are required in particular application scenarios. Services of this type are described below.

There is a standard procedure for default and initial values in the message, which you can override. See: Processing Default and Initial Values.

Moreover, you can have the system return objects using the factory class of the Proxy Framework; you can also use these objects to influence the runtime response in the application program:

• You can call payloads in the Proxy Framework after an outbound proxy has been called, or while an inbound proxy is being called, for example, because you want to archive the payloads. See: Calling the Payload.
• Instead of determining the logical receiver system using routing, you can specify the receiver business system for the outbound proxy. See: Setting the Receiver System.
• You can append an attachment to the message at the sender, which you can then call at the receiver (and the other way around).
• For asynchronous messages, you can ensure that messages sent with a commit work arrive at the receiver in the same sequence that they were sent from the sender (compare with qRFC). See: Guaranteeing the Sequence of Asynchronous Messages.