Add or modify a PeSIT trading pickup (polling client)

Add a PeSIT trading pickup (polling client)

Use this procedure to add a trading pickup to a community for polling a partner's PeSIT server.

The polling pickup is linked to a trading partner delivery.


  • You must have a community with a PeSIT pickup.
  • To add a community, see Add a community.
  • You must have a partner that is linked to your community. For details, see Add a partner.


  1. In the Interchange 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 Trading pickup in the navigation graphic to open the Trading pickups page.
  4. Click Add a pickup.
  5. Choose the transport protocol PeSIT and click Next.
  6. Select Define a new PeSIT polling client and click Next.
  7. Complete the fields of the Configure the PeSIT client settings page.
    • Remote partner URL – Use the Pick polling URL button to select the URL that corresponds to the delivery exchange of the partner to poll. The URL has the format: pesit://<Server Address>:<Port>
    • This polling pickup uses all of the settings from the selected partner delivery exchange.
    • FileName (PI12) – Enter here the name of the file you want to poll from the server. You can enter a star (*) at the end to select all files starting with the characters before the star.
  8. Enter a name for the pickup to identify it in the user interface. Hint: Enter a name that is easily identifiable in a list of pickups in the user interface.
  9. Click Finish.

Modify a PeSIT trading pickup (polling client)

When you add a trading pickup, the wizard prompts you to provide a basic set of parameters. After you create the pickup, you can open the maintenance page for the pickup to view and manage a comprehensive set of parameters. Some of these parameters were automatically set when you added the object, and can only be modified after you add the object.


  1. In the Interchange 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 Trading pickup in the navigation graphic to open the community's Trading pickups page.
  4. From the list of available pickups, click the name of a PeSIT pickup to open the maintenance page for that pickup.
  5. View and modify fields as required. The fields are described in the following section.
  6. After making any modifications, click Save changes.

PeSIT trading pickup (polling) maintenance fields

PeSIT settings tab

The trading side polling pickup configuration relies on a partner’s delivery exchange.

To change these settings, do one of the following:

Click on the Matching delivery exchange link to open the corresponding delivery exchange maintenance page.

Click on Pick polling URL to select another partner delivery exchange.

  • Community settings (Server)
    • PeSIT Identifier (PI3) – Taken from the selected partner’s delivery exchange. You cannot modify this field.
  • Remote partner settings (server)
    • Remote partner – Taken from the selected partner’s delivery exchange. You cannot modify this field.
    • Remote partner URL – The URL of the remote PeSIT server.
    • PeSIT identifier – The PI14 value used as the remote partner identity in the PeSIT message.
  • Matching Delivery exchange – The delivery exchange (defined on the partner object) that corresponds to this pickup exchange. Click the hyperlink to open the maintenance screen for the partner delivery exchange.
  • Acknowledge each fetched file – Select this option if the polled server expects an acknowledgment for each fetched file.
  • 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, Interchange 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. Interchange automatically adds the root certificate to the linked communities' trusted SSL root certificates.
    • If you don’t select this option, Interchange 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, Interchange 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, Interchange 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).

PeSIT polling parameters tab

Use this tab to set the parameters for the PeSIT SELECT polling command.

This tab is identical for PeSIT application and trading polling pickup exchanges.

  • File name (PI12) – Mask of the files to poll. For example, enter "test" to poll only the files named “test”. You can use the wildcard character at the end of any character string. For example, enter "test*" to poll all files that begin with the string "test", including "test1', test_myTest", and so on.
  • File type (PI11) – Leave this value to 0, except if it has a special meaning for the remote server. Check this setting with the remote PeSIT server administrator.
  • Compression (PI21) – This compression option applies to the polled file, not on the request.
    • None (0) – (default) No compression.
    • Horizontal (1) – Compresses the consecutive identical characters in the records.
    • Vertical (2) – Records are compared to one another and the consecutive identical columns are compressed.
    • Both (3) – Combination of the above two compression methods.
  • If pesit.compressionType.out is set in the message, at runtime it overrides the value you select in this UI field (the attribute uses the numeric value).
  • Note: The compression is negotiated between the caller and the server. If the server can’t handle the compression set in this field, a lower type of compression or no compression is applied.
  • Priority (PI17) – In most cases, you can accept the default value (medium). Check with the remote server administrator to know if you can make use of this setting. As a server, Interchange ignores the priority and handles every request at the same level.
    • High (0) – Highest priority
    • Medium (1) – Default
    • Low (2) – Lowest priority
  • Free text (PI99) – Free text often used to transfer metadata. In most cases, you can leave this field blank, unless the server makes a special use of it. Check with the remote server administrator to know if you can make use of this setting.
  • Maximum length = 4096 characters.

Advanced tab

Note   This tab enables you to view and modify advanced parameters. In most cases the default values are the correct values. Do not modify values without first consulting with the administrator of the remote server.
  • Maximum concurrent connections - Default = 100. The maximum number of concurrent connections Interchange can open to a remote server.
  • For example, if the value is 100 connections and there are 150 messages to consume, Interchange opens only 100 connections to that partner. The remaining 50 messages are queued until connections become available.
  • If you are operating in a cluster environment, this is the total number across the entire cluster, no matter how many nodes are running.
  • Max data unit size in bytes (PI25): – The largest of chunk of data, in bytes, to be transferred at one time. For high-speed networks, use the default 32700 bytes.
  • This value is related to the client setting for record length on the PeSIT parameters tab.
  • The value of this field must be the same or larger than the value of the record length field. Do not change this value unless advised by the administrator of the back-end PeSIT application you are trading with.
  • Synchronization option (PI7):
    • Intervals between sync points (Kbytes): – Each time an amount of data equal to this value has been sent, the client is expected to ask the server to confirm whether data totaling this value has been received. The server responds optionally with a confirmation. This represents a check point in the progress of a file transfer. If a connection is lost before a file transfer has been completed, the transfer resumes, upon restart of the transport, at the point of the last successful check point.
    • The default value is 1024 kilobytes (1 megabyte).
    • This setting corresponds to the pacing setting in Axway Transfer CFT.
    • Sync acknowledgement window – The number of check-point cycles that the client waits for the server to respond to a request to confirm file-transfer progress.
    • For example, if the value of Kb per sync point (pacing) is 1024 (1 megabyte) and the value of this field is 1, the client stops sending data after 1024 kilobytes unless the server responds, although the transfer remains active.
    • If this value is 2, the client keeps sending until 2 megabytes (1024 x 2) of data are sent, and so on.
    • If the client’s value for this field is 0 (zero), the client does not ask the server to confirm at intervals the amount of data received.
    • If the server’s value for this field is 0, the server does not send confirmations at intervals of data received.
    • The default value is 3. In most situations this is the correct value.
    • This setting corresponds to chkw setting in Axway Transfer CFT.
  • Read timeout (seconds) – Time in seconds Interchange waits to read data from the delivery exchange before terminating the connection.
  • Connection timeout (seconds) – PeSIT Tc timeout. The time the caller waits for a connection acknowledgment from the server.
  • Transfer timeout - caller mode (seconds) – PeSIT Td timeout. The time the caller keeps the connection open, waiting for another message to send.
  • Network timeout (seconds) – PeSIT Tr timeout. The time the caller waits for an expected and effective network disconnection, before forcing it.
  • Protocol timeout (seconds) – PeSIT Tp timeout. The time the caller waits for the response of the remote, in the middle of a protocol action (such as a transfer).
  • Back up the files that go through this transport – Indicates whether the system backs up copies of the messages it retrieves from integration or receives from partners. Backing up files. This is required for the system to perform fail-over operations such as attempting to send messages again (retries) in case of a transport connection failure. Without backups, a message in process cannot be recovered if the server or a processing node stops or restarts.
  • Restrict maximum file size for this transport – Optionally specify the maximum size of files that this transport can handle. If Interchange receives a file larger than the maximum, the file is rejected and a message is written to the events log.
  • Maximum files per polling interval – The highest number of messages the system can retrieve each time it polls.
  • Polling interval – The interval, in seconds, Interchange waits before polling for messages to retrieve.
  • Specify preferred nodes – If there are one or more nodes for Interchange, you can select one or more as the preferred nodes for consuming messages. If the preferred nodes are running, these are used to process messages. If the preferred nodes are stopped, work is distributed among the remaining running available nodes. Selecting preferred nodes lets you manage work distribution among nodes.
  • In general, you should not use this setting. It is usually preferable to let Interchange automatically determine which node should be responsible for initiating the polling of which exchange point. This setting is useful if you have a cluster that spans geographical locations and each location has its own local transport servers. In this situation, you would use this setting to ensure the exchange points associated with the transport servers are assigned to nodes in the vicinity of the transport servers.

Related Links