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 |
Description |
---|---|
Document exchange |
References a DocExchange element Scripting name: DocExchange |
Transport |
References a Transport element that should be defined by using a Resource object having <<Transport>> stereotype Scripting name: Transport |
Synchronization reply mode |
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 Scripting name: MsgCharacteristicsSyncReplyMode |
Requests acknowledgement |
Possible values are: always, never, or perMessage Scripting name: MsgCharacteristicsAckRequested |
Eliminates duplicate |
Possible values are: always, never, or perMessage Scripting name: MsgCharacteristicsDuplicateElimination |
Requests acknowledgement signature |
Possible values are: always, never, or perMessage Scripting name: MsgCharacteristicsAckSignatureRequested |
Actor |
Possible values are: urn:oasis:names:tc:ebxml-msg:actor:nextMSH or urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH Scripting name: actor |
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:
The nested CanSend elements can represent:
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).