PeSIT configuration overview

Generally, you can separate the configuration of PeSIT exchange endpoints into application configuration and trading partner configuration. This topic provides an overview of these configuration types.

Back-end configuration

To configure Activator for PeSIT exchanges with applications, you create the following objects:

  • Community – Specifies the characteristics of Activator as an exchange partner. In this object you specify internal processes for handling messages and define how Activator expects to receive messages from the back-end and from trading partners.
  • Partner – Specifies the characteristics of a remote partner with which Activator can trade (send and/or receive).
  • Application Delivery – Specifies how Activator sends messages to an application. You require a PeSIT type application delivery for each application you want to send messages to using PeSIT.
  • When you create the application delivery you:
    • Select PeSIT as the protocol type. This enables the embedded PeSIT client process to handle sending of files to the application.
    • Identify the host name and access port of the target application.
    • Specify the identity of Activator as a sender (caller ID) and the identity of the receiving back-end (server ID). If Transfer CFT is your back-end PeSIT application, then Activator caller ID = CFT nrPart, Activator server ID = CFT nsPart.
  • Application Pickup – Specifies how Activator receives messages from an application.
  • When you create this object you:
    • Select PeSIT as the protocol type. This enables the Activator-embedded PeSIT server process to handle the reception of files from the application.
    • Set the name and listening port of the Activator-embedded PeSIT Server that receives messages from the application. You must also provide these server and port values to the sending application.
  •  The configuration of an Activator Community with and Application Pickup and Application Delivery added for PeSIT excahnges with an application.

Once Activator receives a file from an application using PeSIT, it can forward the file to a remote trading partner using any of its available protocols.

Trading partner configuration

To configure Activator for PeSIT exchanges with trading partners, you create the following objects:

  • Community – Specifies the characteristics of Activator as an exchange partner. In this object you specify internal processes for handling messages and define how Activator expects to receive messages from the back-end and from trading partners.
  • Trading Pickup Exchange – Specifies how Activator receives messages from remote trading partner applications. You add the trading pickup to the Community object.
  • Partner – Specifies the characteristics of a remote partner with which Activator can trade (send and/or receive).
  • You create as many partners as you require, each with a specific set of trading characteristics.
  • Trading Delivery Exchange – Specifies how Activator sends messages and files to a specific remote trading partner application. You associate the partner delivery with a specific partner object to identify both the partner identity and the protocol to use when sending files to that partner.

A partner trading delivery and a community trading pickup configured for Activator.

Once Activator receives a file from a remote trading partner using PeSIT, it can forward the file to an application using any of its available protocols.

Role of configuration objects in exchanges

Outbound example: basic configuration

An application sends a message to Activator.

Activator uses the application pickup to collect the message. It then forwards it to the correct remote partner, using information specified in the partner and trading delivery exchanges.

In this example the transport protocol on the partner side is not specified. It is possible to use PeSIT for trading on the partner side as well as on the application side. To do this, you would configure the partner trading delivery to trade using PeSIT.

The set of objects to configure for a basic outbound PeSIT excahnge.

Inbound example: basic configuration

A remote trading partner defined in Activator sends a message to an application through Activator, using any protocol supported by Activator. Activator identifies the remote partner using the Partner object, and then directs the message to the application over PeSIT E, using information specified in the community and application delivery objects.

In this example the transport protocol on the partner exchange side is not specified. it is possible to use PeSIT for trading on the partner side as well as on the application side. To do this, you would configure the community trading pickup to trade using PeSIT.

The set of objects to configure for a basic  inbound  PeSIT exchange (trading partner to back end).

Related topics

Related Links