Setting the Receiver  

Use

In SAPNetWeaver Process Integration, you configure the message receiver or receivers centrally in the Integration Builder. Therefore, when you call a consumer proxy you do not need to specify the receiver. The MessageSpecifier interface enables you to set the message receiver in the application program yourself. This may be necessary in B2B scenarios in particular.

Integration

Using the MessageSpecifier interface you can specify the sender and receiver of a message. Java proxy runtime then writes the values transferred by the application program to the message. If a receiver is already specified in the message header, the Integration Server routing runtime proceeds as follows:

...

       1.      If there is no routing configuration for the sender in the message, routing runtime extracts the receiver from the message header.

       2.      If the Configuration Time contains a routing configuration for the message sender, the following options exist:

○       One of the valid receivers explicitly specifies that the receiver must be taken from the message. The message is sent to all valid receivers, including those in the message.

○       None of the valid receivers explicitly specify that the receiver must be taken from the message. In this case, the message will only be sent to those receivers that are configured in the Configuration Time.

If there is a routing configuration in the Configuration Time, administrators must explicitly authorize those receivers that are specified in the message header.

Features

Setting the Receiver

In an application program, it is possible that the receiver is already known due to the application data, or it is to be enhanced with B2B information. Using the following methods you can change the receiver list of a consumer proxy before the call.

Methods of the MessageSpecifier Interface

Method	Use
public void addReceiverService( String service)	Adds a service to the set of all receiver services of the consumer proxy.
public void addReceiver(  java.lang.String partyName,  java.lang.String partyAgency,  java.lang.String partyScheme,  java.lang.String service)	Adds a receiver to the set of all receivers of the consumer proxy. You must specify the communication party, issuing agency, and identification scheme in cross-company communication.
public boolean removeReceiverService(String service)	Deletes a specific service from the set of all receiver services of the provider proxy.
public void clearReceivers()	Deletes all specified receivers.

Receivers in B2B Applications

In B2B applications, receivers are identified by specifying an issuing agency (for example,  Dun & Bradstreet), an identification scheme (for example, D&B D-U-N-S number), and a name (the DUNS number itself). Since many agencies exist, a B2B communication party can on the one hand be identified by a DUNS number, and on the other, by an EAN number (International Article Numbering Association Number). Within SAP NetWeaver Process Integration, a communication party contains many different names. However, the content of the message header is most important when identifying the communication party at the message receiver.

More Information

Identifiers