Pickups and deliveries for PeSIT

In , you configure PeSIT exchanges with applications and trading partners principally through the creation and management of PeSIT pickups and deliveries.

Types of PeSIT exchanges

In you can configure three types of exchanges for PeSIT message trading:

• Delivery exchanges – see Pickups and deliveries for PeSIT
• Pickup exchanges – see Pickups and deliveries for PeSIT
• Polling exchanges – see Pickups and deliveries for PeSIT

Each of these exchange types are available for exchanging files with both applications and remote trading partners.

Each or these exchange types can be configured over clear or secured TLS connections.

The following sections describe the characteristics and functions of PeSIT exchanges.

PeSIT functions for partner trading and back-end integration

The following table summarizes the PeSIT protocol functions for exchanges for exchanging with applications and with partners:

Activator exchange type	PeSIT function	Back-end application exchanges	Trading partner exchanges
Delivery	Send
	Fetch	–
Pickup	Polling
	Multi-community
	Respond to fetch
Common	Restarts
	Metadata attachments
	TLS handling
	Ack handling
	Pickup exchange identifier	Protocol IDs (PI3 and PI4)

PeSIT delivery exchanges

A PeSIT delivery exchange acts as a PeSIT caller (client).

• For application deliveries, you add the delivery exchange to a community. You configure the exchange to call a back-end PeSIT server.
• See Add or modify a PeSIT application delivery.
• For trading partner deliveries, you add the delivery exchange to a trading partner. You configure the exchange to call a PeSIT server residing on the partner's computer.
• See Add or modify a PeSIT partner delivery.

A PeSIT delivery exchange operates in one of two roles:

• Initiator-Sender role (back-end integration and partner trading)
• This is the default role for PeSIT delivery exchanges.
• The delivery exchange extracts the file and attributes from the message and sends them to a remote PeSIT Server (using PeSIT CREATE). If some attributes are missing, default values will be taken from the delivery settings. Any additional missing attributes are taken from the delivery exchange configuration settings.
• Initiator-Receiver role (partner trading only)
• If you he message Action attribute equals Fetch, the delivery exchange extracts the attributes from the message, builds a fetch request (PeSIT SELECT) and sends the request to the remote server.
• If any attributes are missing, default values are taken from the delivery exchange configuration settings.
• If a file on the remote server corresponds to the request (File name and File type), the file is returned. This triggers creation of a new incoming message in Activator, assigned to the matching community’s PeSIT server. The attributes from the request are used and updated with the effective transfer characteristics (File name, File type, Transfer Id and so on). The payload is included as a file.
• If no file is available on the remote server, no incoming message is generated

For details about how to configure, view and modify PeSIT exchanges, see Manage PeSIT pickups and deliveries.

PeSIT pickup exchanges

A PeSIT pickup exchange acts as a PeSIT server.

When you create a PeSIT pickup on the application side, the pickup is shared between communities.

When you create a PeSIT pickup on the trading side, the pickup is not shared between the communities. It is dedicated to a single community.

A PeSIT pickup exchange operates in one of two roles:

• Responder-Receiver (back-end integration and partner trading)
• In this role, the PeSIT pickup:
  1. Responds to a client (caller) connection and checks that:
     • The PeSIT server identifier (PI4) corresponds to a routing ID of the community.
     • On the trading side only, the PeSIT caller identifier (PI3) must correspond to a routing ID of a partner that is linked to that community and that has a PeSIT delivery configured. It’ll use the parameters of both pickup and delivery exchanges for the verification (password…). If the verification fails, the PeSIT connection will be refused immediately
  2. Creates a new incoming message
  3. Fills the message with the metadata received through the PeSIT CREATE
  4. Receives the payload and attaches it as a file to the message
• Responder-Sender (back-end integration and partner trading)
• In this role, the PeSIT pickup:
  1. Responds to a client (caller) connection and checks that:
     • The PeSIT server identifier (PI4) corresponds to a routing ID of the community.
     • On the trading side only, the PeSIT caller identifier (PI3) must correspond to a routing ID of a partner that is linked to that community and that has a PeSIT delivery configured. It’ll use the parameters of both pickup and delivery exchanges for the verification (password…). If the verification fails, the PeSIT connection will be refused immediately
  2. Reads a PeSIT SELECT request. It looks for a message in the HeldForPickup state that matches the SELECT criteria.
  3. If it finds one, it takes the oldest matching message and produces it over the delivery exchange of the partner.
  4. If it doesn’t find a matching message, it returns a standard PeSIT “No file” response to the caller.
• For the server to act in the Responder-Sender role, you must prepare messages in the HeldForPickup state, so that there is content a remote client can fetch. There are two ways to do this:
  • Select the option Hold all outbound messages for pick up by the remote client option on the delivery exchange.
  • Set the message.HoldForPickup attribute to true. This attribute will override the delivery exchange setting.
• In this case, the message is sent to the partner or the back end, but with the "Hold for pickup" option set. The message stops just before sending and remains (with all necessary information), ready for the intended partner or back end application to pick it up.

For procedures on how to add PeSIT pickup exchanges of the non-polling type, see:

• Add or modify a PeSIT application pickup (embedded server)
• Add or modify a PeSIT trading pickup (embedded server)

For details about how to configure, view and modify all PeSIT exchanges, refer to Manage PeSIT pickups and deliveries.

PeSIT polling pickups

The polling pickup is available:

• On the application side, dedicated to a community (this is an exception due to PeSIT’s need for party identification)
• On the partner trading side, attached to a community

Plays Initiator-Receiver role on both sides

The polling pickup always polls the same pattern of files for the same community and partner/back end pair. You need to set one polling pickup per type of polling you want to do.

You can use the wild card “*” when you specify the file name to pickup, to select multiple files.

• If the polled server has a file that matches the pattern of the polled file, the server sends the file to the polling pickup. The polling pickup:
  • Creates a new incoming message,
  • Fills the incoming message with the metadata received through the ACK SELECT
  • Receives the payload and attaches it as a file to the message.

The polling session continues until either:

• The polled server has no matching file
• The polling pickup reaches the Maximum files per polling interval setting

The next polling session starts after the polling interval specified in the exchange configuration (if within the scheduled time window).

For procedures on how to add polling-type PeSIT pickups, see:

• Add or modify a PeSIT application pickup (polling client)
• Add or modify a PeSIT trading pickup (polling client)

For details about how to configure and modify all PeSIT exchanges, refer to Manage PeSIT pickups and deliveries.

Special note for community backups

When you back up a community, application side PeSIT polling pickups are not backed up. They are handled by the back-up tool as if they are "normal" pickups that belong to any community.