Add a PeSIT application delivery

Prerequisite

You must have a community. If you need to add a community, see Add a community.

Procedure

  1. In the Activator user interface, select Trading configuration > Manage trading configuration.
  2. From the list of communities, click the name of a community to display the Summary page for that community.
  3. Click Application delivery in the navigation graphic to open the Application delivery exchanges page.
  4. Click Add an application delivery exchange to open the Exchange Wizard.
  5. Choose the PeSIT transport protocol and click Next.
  6. Complete fields of the Configure PeSIT client settings page.
    • Hostname – The IP address or the network name of the back-end 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 back-end 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, and are available for the remote client to fetch.
    • Server settings – In this section you set the back-end server’s protocol identity (PI4).
      • Use the final destination ID from the message – Select this option to have the trading engine read pesit.finalDestinationId.out (which corresponds to PI62), and use it as PI4.
      • Use this identifier, PeSIT Identifier (PI4) – If you select this option, you must then enter a specific identifier for PI4. This value must correspond to the value used by the application to identify the server. For Axway Sentinel users, the PI4 value is reported as the receiverRoutingId.
      • Use password (This is the password expected from the server) – Select this option if you expect an authentication from the back-end server.
    • Clients must use SSL to connect to this server – If the back-end 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, the trading engine 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 in the partner’s personal certificates and then select the option Trust this for SSL server and/or client authentication. The trading automatically adds the root certificate to the linked communities' trusted SSL root certificates.
      • If you do not select this option, the trading engine only verifies that the server certificate is signed by a certificate that is among the community trusted SSL root certificates.
      • Enable CFT compatibility – When you select this option, Activator aligns the PeSIT record size on TLS packets. This is the only method handled by Axway Transfer CFT before version 3.0, and is the default method for the Axway products Gateway and Interpel.
      • If you do not select this option, Activator adds the record size as a header of the record, as for non TLS communications. This is the default and the recommended handling (when the remote application supports it).
  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 application delivery.

Related Links