About this task
A delivery channel record links a document exchange record and a transport record. The combination of these two records provides a complete description of how a trading partner expects to receive documents. A delivery channel record eliminates re-entry of document exchange information for every transport protocol. You can define several delivery channels in one trading profile.
To create a delivery channel record:
Procedure
- From the Trading Partner menu, select .
- Next to Create New Delivery Channel, click Go!
- In the Information page, complete the following fields and click Next:
- Field
- Description
- Name
- Name for the delivery channel record to create for this trading partner profile. Required.
Note: You should use part of a company name or DUNS in this field or use an indicator that references AS1.
- Identity
- Unique ID that links the delivery channel record to the identity record. The Identity needs to be selected from the available list. Required.
- In the Channel Definition page, complete the following fields and click Next:
- Field
- Description
- Transport
- Name of the transport that links this delivery channel record to the transport records. You need to select the name from the available list. Required.
- Document Exchange
- Name of the document exchange associated with this delivery channel record. You need to select the name from the available list. Required.
- You can skip the Security page as it is not applicable for AS1 and click Next.
- In the Delivery Settings page, complete the following fields and click Next:
- Field
- Description
- Receipt Type
- Used only by the EDIINT Message service. The type of receipt to request. Valid values are Message Disposition Notification (MDN) and NONE (default). Optional.
- Receipt Signature Type
- This is the message digest algorithm used when computing signatures, if a payload type requiring a signature is selected. Optional.
Valid values are:
Note: Selection of a value other than None prompts the EDIINT Message service to request a signed Message Disposition Notification (MDN) when building messages to the trading partner. We recommend that you only use MD5 if your implementation requires this algorithm.
- Receipt Timeout
- Time-out value for receipt of expected MDNs, in seconds. Default is 3600 seconds. Optional.
- Delivery Mode
- Used only by the EDIINT Message service to deliver receipts for messages received. Required.
Valid values are:
- Asynchronous HTTP – Used for AS2 and RosettaNet if you want an asynchronous receipt.
- Asynchronous HTTPS – Used for AS2 if you want an asynchronous receipt.
- Asynchronous SMTP – Used for AS1 and AS2 if you want an asynchronous receipt.
- Synchronous – Used for AS2 if you want a synchronous receipt.
Select Synchronous here for AS1 as synchronous means that only the Disposition-Notification-To header is placed in a message. The other options add the Disposition-Notification-Options header. Only Disposition-Notification-To is needed for AS1, since it is assumed all messages are exchanged through e-mail.
- Receipt to Address
- Not applicable for AS1.
- In the Confirm page, verify the settings that you have selected and click Finish to update the document channel record.
- Click Return to continue.
Results
You are now ready to create a packaging record.