DestinationParty property is used to resolve the send port within the RoleLink. Once DestinationParty is initialized, the orchestration looks back (thru bts_Party and bts_party_sendport tables in Management DB) for the associated send ports for desired operation. Therefore, the question of interest is how to initialize DestinationParty?

Generally, it depends on the initiating role of the RoleLink.

If the role stated for initiating is an implements role (thus, the orchestration receives messages thru this role), the DestinationParty property is initialized automatically by receive.  Such an initialization occurs as follows:

·          involved uses role is determined from RoleLink,

·          its enlisted party is determined from configuration settings,

·          its PartyID inserted into DestinationParty property.

From here the orchestration resolves the send port as mentioned below.

If the role stated for initiating is a consumer or uses role (thus, the orchestration send messages thru this role), the DestinationParty property must be initialized explicitly in the orchestration:

ConfirmOrder(Microsoft.XLANGs.BaseTypes.DestinationParty) =

new Microsoft.XLANGs.BaseTypes.Party(<value>, <qualifier> );