Create a Transport Record

Edit online

About this task

To define how to send a PIDX message using HTTP, you must create a transport record.

To create a transport record:

Procedure

  1. From the Trading Partner menu, select Setup > Advanced > Transports.
  2. Next to Create New Transport, click Go!
  3. In the Information page, complete the following fields and click Next:
    Field
    Description
    Name
    Name for the transport record to create for this PIDX trading partner. Required.
    Note: You may use part of a company name or DUNS in this field and an indicator that references PIDX.
    Identity
    Unique ID used when you created an identity record for this PIDX trading partner. Required.
  4. In the Communications page, complete the following fields and click Next:
    Field
    Description
    Receiving Protocol
    Communications protocol supported by this transport record when receiving data. Select HTTP. Required.
    Sending Protocol
    Communications protocol supported by this transport when sending data. Select HTTP. Required.
    End Point IP
    Leave this field blank.
    End Point Port
    Leave this field blank.
  5. In the End Point Settings page, complete the following fields and click Next:
    Field
    Description
    End Point
    Destination URL for this trading partner. Required.
    End Point Type
    Purpose of this end point. Select All Purpose. Required.
  6. In the Protocol Settings page, complete the following fields and click Next:
    Field
    Description
    Response Timeout (seconds)
    Number of seconds to wait for remote response to an outbound queue. Type the value 600 in this field. Required for PIDX.
    Firewall Proxy
    IP address, port number, login ID, and password of the remote firewall represented in URL format where commas separate values (for example, <host>, <port>). If used, you may need to specify both a login ID and a password. Used for outbound sessions. Optional.
    Firewall Connect Count (seconds)
    Number of seconds that Sterling B2B Integrator attempts to contact port address of the transport before timing out. Optional.
    Socket Timeout (seconds)
    Number of seconds to wait for remote response to a command. Type the value 600 in this field. Required.
  7. In the Security page, complete the following fields and click Next:
    Field
    Description
    SMIME Encryption User Certificate
    Certificate used to encrypt PIDX messages that are sent outbound through this transport record. This certificate has no impact in PIDX messages being received through this transport. Therefore, if this transport is for the company running Sterling B2B Integrator, leave this field blank. If this transport is for your PIDX trading partner, choose the Trusted encryption certificate from the trading partner that you previously checked in. Required for PIDX.
    SMIME Decryption Certificate (System Store)
    Certificate used to decrypt PIDX messages that are received (inbound) through this transport record. This certificate has no impact in PIDX messages being received through this transport. Therefore, if this transport is for the company running Sterling B2B Integrator, leave this field blank. If this transport is for your PIDX trading partner, choose the encryption certificate from the trading partner that you previously checked in. Required for PIDX.
    SSL
    Whether Secure Sockets Layer (SSL) must be active. Select Must to enable this transport to use this protocol with a key certificate. This field is used in conjunction with the key certificate field. If not using a key certificate, select None. Required for PIDX.
    Key Certificate Passphrase
    Password that protects the Web server key certificate. Required if SSL option is set to Must.
    Cipher Strength
    Strength of the algorithms used to encrypt messages. Select Strong (default) to indicate strength of algorithms with a key certificate. This field is used in conjunction with the key certificate field. If not using a key certificate, select All or Weak. Required.
    Key Certificate (System Store)
    Certificate used to decrypt an inbound encrypted RNIF v2.0 message sent to the identity associated with this transport. The trading partner encrypts the message with the public key and the receiver decrypts the message with this private key certificate. If using a key certificate, select the appropriate key certificate from the list (valid values are blank, OpsKey, OpsDrv, UIKey, and B2BHTTP). Otherwise, leave this field blank.
    CA Certificates
    Certificate used to verify the Web server certificate of a trading partner. These certificates must come from your PIDX trading partners and you must have previously checked them in. Required if the SSL option is Must or Optional.
  8. In the Protocol Mode page, complete the following fields and click Next:
    Field
    Description
    Protocol Mode
    Use the default value PUT. Required.
    Document
    Leave this field blank.
  9. In the Transport Account page, complete the following fields and click Next:
    Field
    Description
    User ID
    Unique ID that associates this transport with the remote system of your PIDX trading partner. Optional.
    Password
    Password that authenticates the user ID to the remote system of your PIDX trading partner. Optional.
    Confirm Password
    Password typed in the Password field. Optional.
  10. Click Finish to update the transport record.

Results

You are now ready to create a document exchange record.