Special Services of the Proxy Runtime

Use

Using the documentation above, and a correspondingly configured connection, you are now able to exchange messages using the Integration Server from the perspective of the proxy runtime (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. These services are described below.

Features

Note

To extend proxy capabilities by using the application program interfaces for proxy communication in the WS environment, see Application Program Interfaces for Outbound Proxy Communication , Application Program Interface for Inbound Proxy Communication

You can also influence the runtime response in the application program by using methods of the messageSpecifier interface:

You can call payloads in the proxy runtime after a consumer proxy has been called, or while a provider proxy is being called, for example, because you want to archive the payloads.
More information: Calling the Payload
Instead of determining the receiver using routing, you can specify the (B2B) receiver for the consumer proxy directly.
More information: Setting the Receiver
You can append attachments to the message at the sender, which you can then call at the receiver (and the other way around).
More information: Attachments
You can query the message ID of sent and received messages.
More information: MessageSpecifier Interface

Furthermore, administrators on the receiver side can allocate authorizations for receiving messages by assigning the corresponding security roles to a Java EE user and then specifying this user in the Configuration Time. For more information about authorization checking and creating users on the SAP AS Java, see the Configuration Guide.