Proposed rewording at the end of 2.8.1.1 (RoutingInput.BusinessInfo)

["Jacques R. Durand" <JDurand@us.fujitsu.com>]

 

 

 Proposed rewording at the end of 2.8.1.1:

• RoutingInput.BusinessInfo concerns the destination endpoint. All or a subset of the children parameters {Service, Action, Properties, MPC} of this parameter may be specified. Although several Service instances may be associated with an endpoint (same for Action and MPC), it is possible that only one instance of {Service, Action, Properties, MPC}values is known from the I-Cloud routing function and is necessary to route all messages to this endpoint. In that case, the EPR PMode parameter associated with this endpoint will only contain this instance of {Service, Action, Properties, MPC}under its BusinessInfo sub-parameter. All PModes associated with this destination endpoint will refer to this same EPR and its unique RoutingInput.BusinessInfo parameter even though each one of them may use a different Service / Action pair (or different MPC) in its PMode.BusinessInfo parameter. In such cases the EPR.RoutingInput reference parameter must always be used even for routing User Messages, as the routing function would be unable to use other Service / Action pairs - as specified under the eb:Messaging/eb:UserMessage element - that are also supported by this endpoint.

   

-jacques