Create a Delivery Channel Record

You can create a delivery channel record from the Administration Menu.

About this task

To create a delivery channel record:

Procedure

  1. From the Administration menu, select Trading Partner > Advanced > Delivery Channels.
  2. Under Create, next to New Delivery Channel, click Go!
  3. Specify the Information settings.
    On the Information page, complete the following fields and click Next:
    Information Fields Description
    Name Name for the delivery channel record to create for this trading profile. Required.
    Identity Unique ID that links the delivery channel record to the identity record. It must match the Name field of the identity record. Required.
  4. Specify the Channel Definition settings.
    On the Channel Definition page, complete the following fields and click Next:
    Channel Definition Fields Description
    Transport Name of the transport that links this delivery channel record to the transport records. It must match the Transport Name field of the transport record. Required.
    Document Exchange Name of the document exchange associated with this delivery channel record. It must match the Document Exchange Name field of the document exchange record. Required.
  5. Specify the Security settings.
    On the Security page, complete the following fields and click Next:
    Security Fields Description
    Sync Reply Mode What the receiving system expects in a response when bound to a synchronous communications protocol, such as HTTP. Required.Valid values are:
    • Response Only – Only the business response message is returned.
    • Signals and Response – System returns the business response message in addition to one or more business signals.
    • Signals Only – Response includes one or more business signals as defined in the ebXML Business Process Specifications Schema (ebBPSS), but not a business response message.
    • msh Signals Only – Response includes errors or acknowledgments only. Business response messages or business signals must be returned asynchronously.
    • NONE – No business response messages, business signals, or msh signals are returned (default).
    Non Repudiation of Origin Whether the message sender must sign the message with a digital certificate. Valid values are Yes and No. Required.
    Non Repudiation of Receipt Whether the message receiver must sign the message with a digital certificate. Valid values are Yes and No. Required.
    Secure Transport Whether the delivery channel record uses a secure transport protocol such as SSL or IPSEC. Valid values are Yes and No. Required.
    Confidentiality Whether the message must be encrypted. Valid values are Yes and No. Required.
    Authenticated Whether the digital signature of the message must be checked to verify that it came from the expected sender and it has not been modified in transit or storage. Valid values are Yes and No. Required.
    Authorized Whether the message sender must be authorized (granted access to a network resource) before the message can be delivered to the system. Valid values are Yes and No. Required.
  6. Specify the Delivery settings.
    On the Delivery Settings page, complete the following fields and click Next:
    Delivery Settings 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). Required.
    Receipt Signature Type Used only by the EDIINT Message service to transfer data to the trading partner. Identifies the fixed-length of compressed representation of messages requested on receipts. Required.Valid values are:
    • None
    • MD5 – Message digest algorithm that verifies the integrity of data through a 128-bit message digest.
    • SHA1 – Secure hash algorithm that verifies the integrity of data through a 160-bit (20 byte) message digest. Transmission is a bit slower that MD5; however, the larger message digest size offers a more secure data transference.
    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.
    Receipt Timeout Timeout value for receipt of expected MDNs, in 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.
    Receipt to Address Used only by the EDIINT Message service. Indicates where a receipt must be sent if it is not going to the e-mail address in the associated identity. Required if you are using EDIINT AS2 requesting asynchronous MDNs. You must type the complete URL where you want the message to be sent. Required.
  7. Click Finish to add the delivery channel record.
  8. Click Return to continue.