Create a Document Exchange Record

About this task

To describe properties of the documents and messages passed between you and your AS1 trading partner, you must create a document exchange record.

To create a document exchange record:

Procedure

  1. From the Trading Partner menu, select Setup > Advanced > Document Exchange.
  2. Next to Create New Document Exchange, click Go!
  3. In the New Document Exchange: Information page, complete the following fields and click Next:
    Field
    Description
    Name
    Name for the document exchange to create for this AS1 trading partner. Required.
    Note: You should use part of the company name or DUNS number in this field.
    Identity
    Unique ID associated with the identity that links this document exchange record to the identity record. You need to select an identity from the available list. Required.
  4. In the Retry Settings page, complete the following fields and click Next:
    Field
    Description
    Number of Retries
    Number of times that Sterling B2B Integrator tries to contact the trading partner before timing out. Type the value 3. Required.
    Retry Interval (sec)
    Number of seconds that Sterling B2B Integrator waits before trying again to contact the trading partner after the previous attempt timed out. Type the value 30. Required.
    Persist duration (sec)
    Number of seconds that a message received is kept before being passed to the integration engine. This parameter is not applicable for AS1.
  5. In the Enveloping Properties page, complete the following field and click Next:
    Field
    Description
    Protocol
    Used only by the EDIINT Message service. The security protocol to be used is SMIME for AS1 (if not exchanging AS1 messages, select None). Required.
  6. You can skip this step if the record is created for a hub, This is because the choices in an exchange are taken from the profile for the spoke. If this record is for a spoke, select the algorithms that you and your trading partner agree to use for the different cryptographic operations. If you do not pick a payload type that uses one of those operations, the algorithm choice for it will not be used. Do not skip this step if the record is for a spoke.
    Note: Encryption algorithms are not used for signatures; that is why there are two distinct fields for encryption and signature algorithms.

    In the Security page, complete the following fields and click Next:

    Field
    Description
    Encryption Algorithm
    Used by the EDIINT Message service only if a payload type requiring encryption is selected. Identifies the encryption algorithm to be used. Required if Protocol value is anything other than None. Required.

    Supported algorithms are:

    • Triple DES 168 CBC with PKCS5 padding
    • 56-bit DES CBC with PKCS5 padding
    • 128-bit RC2 CBC with PKCS5 padding
    • 40-bit RC2 CBC with PKCS5 padding
    Signing Algorithm
    This is the message digest algorithm used when computing signatures, if a payload type requiring a signature is selected. Required.

    Valid values are:

    • MD5
    • SHA1
    Note: We recommend that you do not use MD5 unless there is no other alternative in order to interoperate with an older application and you determine interoperating outweighs the security risk of using MD5. Use MD5 as less times as possible.
    Signing Key Certificate
    The key certificate for the encryption key of the identity, if available, that is used to encrypt the message when using SMIME. Required.
    Note: This is also the private key the EDIINT Message service uses to sign messages it builds. To guarantee that messages are signed, you have to select a payload type in the packaging that incorporates signing.

    You must have already checked the certificate in to Sterling B2B Integrator for it to be displayed in this list. The Configure Certificates link enables you to open a common window displaying all certificates list that you may use. This window is used to select multiple certificates for the purpose of seamless transition from one certificate to the other when its validity expires and to select the policy for this certificate. The default policy is Closest non-future Go Live Date or the only certificate in the list.
    Signing User Certificate
    This is a certificate from the trusted certificate store that you want to use to verify signed messages from the trading partner. You need to select a certificate if this profile is for a spoke and you expect the partner to sign messages.
    Note: This is also a trusted certificate that the EDIINT Message service uses to verify signatures on messages it receives.

    You must have already checked the certificate in to Sterling B2B Integrator for it to be displayed in this list. The Configure Certificates link enables you to open a common window displaying all certificates list that you may use. This window is used to select multiple certificates for the purpose of seamless transition from one certificate to the other when its validity expires and to select the policy for this certificate. The default policy is Closest non-future Go Live Date or the only certificate in the list.
  7. In the Confirm page, verify the settings that you have selected and click Finish to update the document exchange record.
  8. Click Return to continue.

Results

You are now ready to create a delivery channel record.