Examples of Generically/Specifically Defined Interface Determinations

Example 1

The following interface determination 1 can be applied at runtime to all messages that are sent from A, B, myOutbound, and http://example to any receiver parties and receiver services.

Key Attributes	Example of an Interface Determination
Sender Party	A
Sender Component	B
Interface Name	myOutbound
Interface Namespace	http://example
Receiver Party	*
Receiver Component	*

By using wildcard characters, you are able to apply multiple interface determinations to a message at runtime. In a situation such as this, the “most specific” interface determination is always used.

Example 2

At runtime, a message is sent from A, B, myOutbound, http://example to the receiver (party: C, component: D). However, neither is more specific than the other.

Key Attributes	A writing synchronous agent ensures that changes to the calling business object are documented and prepared for process persistence (PIP).	Values for IF Determination 1	Values for IF Determination 2
Sender Party	A	A	A
Sender Component	B	B	B
Outbound Interfaces	myOutbound http://example	myOutbound http://example	myOutbound http://example
Receiver Party	C	*	C
Receiver Component	D	*	*

Interface determination 2 is actually used in this case because it is “more specific” than interface determination 1.

There must always be a most-specific interface determination for each message. For this reason, it is not possible to simultaneously activate some interface determinations that use the wildcard character.

Example 3

The following two interface determinations 2 and 3 cannot be active simultaneously.

Key Attributes	Values for IF Determination 2	Values for IF Determination 3
Sender Party	A	*
Sender Component	B	*
Outbound Interfaces	myOutbound http://example	myOutbound http://example
Receiver Party	C	C
Receiver Component	*	D

At runtime, a message is sent from A, B, myOutbound, http://example to the receiver (party: C, Service: D). However, neither is more specific than the other. In this case, no most-specific interface determination exists for the message.

Note

If you use the wildcard character ( *) for the receiver service when creating an interface determination, define this interface determination (with a particular interface mapping IM1) as valid for all receiver services. This generic interface determination is used for a particular integration process and is therefore assigned to a particular configuration scenario S_1. A more specific interface determination (for example, for a particular sender/receiver service pair), is then created for the same interfaces, for example, for another integration process. This interface determination is therefore assigned to a second configuration scenario S_2. This interface determination might reference another interface mapping ( IM2), for example. In this case, the definition of the interface mapping IM1 (runtime perspective) made in the generic definition is now obsolete for the specified sender/receiver service pair. In this way, a more specific definition of an interface determination at runtime can have an affect on the configuration data grouped together in configuration scenario S_1.

Examples of Generically/Specifically Defined Interface Determinations

Use