Add a PeSIT partner delivery

Use this procedure to add a delivery for sending messages to a specific trading partner using PeSIT.

Prerequisites

• You must have a community with a PeSIT pickup.
• To add a community, see Add a community.
• To add a PeSIT pickup, see Add a PeSIT application pickup (embedded server) or Add a PeSIT trading pickup (polling client).
• You must have a partner that is linked to your community. For details see, Add a partner

Procedure

1. In the user interface, select Partners > Manage partners.
2. From the list of partners, click the name of a partner to display the Summary page for that partner.
3. Click Delivery exchange in the navigation graphic to open the Deliveries page.
4. Click Add a delivery exchange, to open the exchange wizard.
5. Choose the message protocol PeSIT, and click Next.
6. Complete fields of the Configure PeSIT client settings page.
   • Hostname – The IP address or the network name of the trading partner PeSIT server to connect to. This must be the fully qualified domain name or IP address of the PeSIT server your community connects to for sending messages.
   • Port – The port on which the partner PeSIT server listens for connection requests.
   • Hold all outbound messages for pickup up by the remote client:
     • Not selected: The messages sent to this delivery are produced and sent to the server.
     • Selected: The messages sent to this delivery stop in HeldForPickup state, available for the remote client to fetch them.
   • Override community settings (caller) – This controls the caller’s protocol identity (PI3). Select the following, as needed.
     • Allow any valid community routing ID – Select this option to use the message’s SenderRoutingID as the community (caller) identifier (PI3). If you select this option, the trading engine does not check the sender identity for the transfer.
     • Restrict to specific community routing ID –Select this option and then choose a community routing ID from the list of available IDs to identify the community (caller) identifier to use. When you select this option, if the SenderRoutingId from the message is different from the selected value, the trading engine rejects the transfer.
     • Use Password (This is the password the server expects) – Select this option and enter a password if the remote partner server expects a password from you.
   • Remote partner settings – In this section you set the partner server’s protocol identity (PI4) and password requirements.
     • Allow any valid partner routing ID– Select this option to use the message’s ReceiverRoutingID as the partner (server) identifier (PI4). If you select this option, the trading engine does not check the receiver identity for the transfer.
     • Restrict to specific partner routing ID – Select this option and then choose a partner routing ID from the list of available IDs to set the partner (receiver) identifier to use. When you select this option, if the ReceiverRoutingId from the message is different then the selected value, the trading engine rejects the transfer.
     • Override password settings – Select this option to override the expected password setting on the PeSIT community pickups. Either enter no password if no password is required, or select the Use password option and enter the required password to use.
   • Clients must use SSL to connect to this server – select this option If the partner server is configured to transfer over SSL/TLS. You must import the root certificate of the remote server to the community trusted SSL root certificates.
     • Enable host name verification – If you select this option, verifies that the name of the server is the same as the name in the server’s certificate. This requires that you import the server certificate chain to the partner’s personal certificates and select the option Trust this for SSL server and/or client authentication. automatically adds the root certificate to the linked community's trusted SSL root certificates.
     • Enable CFT compatibility
     • When you select this option, aligns the PeSIT record size on TLS packets. This is the only method handled by Transfer CFT up to version 3.0, and the default method for the Axway products Gateway and Interpel.
     • When unselected, adds the record size as a header of the record, as for non TLS communications. This is the default, which is recommended.
7.  Enter a name for the exchange to identify it in the user interface.
8. Click Finish.

After you add the delivery

You can view and modify the exchange. For details, see Modify a PeSIT partner delivery.