CL_BS_SOA_ASYNCPRX_OUT - Trigger proxy outbound

General Data in Customer Master   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Functionality

This class can be used to invoke consumer proxies for asynchronous enterprise services.

Compared to a direct call to a generated consumer proxy class it takes care of following:

• Technical sequencing based on the configured runtime
  If a customer configures the XI protocol, XI's Exactly Once In Order (EOIO) feature is used with the passed technical sequencing context.
  If however the WS protocol is configured a persistent sequence as defined within the WebService Reliable-Messaging(WS-RM) protocol is created for each passed technical sequencing context - and reused in subsequent service consumptions with identical context.

• Response Receiver Correlation
  For response messages (such as a Confirmation in a Request-Confirmationpattern) a CorrelationID might be passed. In this case the response message is automatically enriched with the relevant ReferenceID and routed to the original sender.

• Handling of Service Groups and Routing
  Service Groups can be used to enable mass-configurationfor consumer proxies and to enable routing. This however requires an alternate way of instantiatingthe consumer proxy instances and calling the proxy. This again is automatically handled - if the passed consumer proxy is assigned to a service group.
  Appropriate logic is contained to ensure compatibility if a consumer proxy is assigned to a service group in a later release then the initial consumption.

• In-application sequencing
  The technical sequencing based on WS-RM only provides correct sequencingwithin a limited timeframe. As soon as a persistent sequence is closed by a service provider, subsequentmessages might arrive in different persistent queues. In-application sequencing provides a sequencevalidation on application level to avoid any inconsistencies. The appropriate sequencing fields of amessage are set automatically within this class if an appropriate application sequencing context is passed - alongside with a path where the sequence fields are contained in the message.

Note:

The are two different ways to make use of this class.

Method EXECUTE provides a 'black box' handling all the above described features in one go. It also callsthe final proxy class method for sending the message. The possibilities of a caller to interact aretherefore very limited. The usage of this method is therefore NOT recommended. The advantage however is a minimized migration effort of a 'classical' service consumption (direct call to an 'EXECUTE_ASYNCHRONOUS' method).

Methods CREATE_PROXIES, PREPARE_SEND, SET_SEQUENCE_FIELDS and AFTER_SEND provide a much more fine-granular API with more possibilities for a caller to keep the control.

Relationships

Example

Report RBSSOA_IAS_TST_INVENTORY_OUT2 shows the usage of the methods for a sample message.

Notes

Further information

PERFORM Short Reference   General Data in Customer Master  
This documentation is copyright by SAP AG.


Length: 3039 Date: 20120526 Time: 093553     triton ( 142 ms )