Designing a Delivery Channel

Chapter 5 Building a Collaborative Business Process Model

Designing a Delivery Channel

You design a Delivery Channel using a resource with a <<DeliveryChannel>> stereotype.

The name of this object constitutes the Id of the Delivery Channel element. If at least, one CanSend/CanReceive action references the Id of the Delivery Channel, then the generation function produces a corresponding Delivery Channel in the CPA template.

The following extended attributes (accessible from the Extended Attributes tab of the resource property sheet) apply to the Delivery Channel:

Name	Internal code	Description
Document exchange	DocExchange	References a DocExchange element
Transport	Transport	References a Transport element that should be defined by using a Resource object having <<Transport>> stereotype
Synchronization reply mode	MsgCharacteristicsSyncReplyMode	Possible values are: mshSignalsOnly, responseOnly, signalsAndResponse, signalsOnly, or none. With a value different from "None", it indicates what the sending application expects in a synchronous response. This parameter impacts the generation of the sequence of actions in the CPA
Requests acknowledgement	MsgCharacteristicsAckRequested	Possible values are: always, never, or perMessage
Eliminates duplicate	MsgCharacteristicsDuplicateElimination	Possible values are: always, never, or perMessage
Requests acknowledgement signature	MsgCharacteristicsAckSignatureRequested	Possible values are: always, never, or perMessage
Actor	actor	Possible values are: urn:oasis:names:tc:ebxml-msg:actor:nextMSH or urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH

The extended attribute MsgCharacteristicsSyncReplyMode on the resource object with <<DeliveryChannel>> stereotype impacts the sequence of actions in the CPA.

With a value different from "None", PowerDesigner generates:

A CanReceive element (Receive action) for the party receiving a business document
A nested CanSend elements (Send action) to express that the requests and responses are synchronized

The nested CanSend elements can represent:

Send signal actions (signalsOnly)
Send response document actions (responseOnly)
Send signal actions and Send response document actions (signalsAndResponse)

If the MsgCharacteristicsSyncReplyMode attribute is None, the CanSend actions using the Delivery Channel are not nested in the CanReceive element.

With a value different from None, the Sender and the Receiver must use the same channel Id (SenderChannelId and ReceiverChannelID attributes on the flow must reference the same resource with a <<DeliveryChannel>> stereotype).