Modify a PeSIT application pickup (embedded server)

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

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 pickup in the navigation graphic to open the Application pickups page.
  4. From the list of available exchanges, click the name of a PeSIT exchange to open the maintenance page for that exchange.
  5. View and modify fields as required. The fields are described in the following section.

PeSIT application pickup maintenance fields (embedded server)

PeSIT server settings tab

  • Click the View setting for this embedded server link to view the server configuration. This link describes the server whose address and port is displayed in the Local connection string field.
  • Access to this server requires a password – Select this option if you want the back-end client to provide a password in order to connect to this server. Enter and confirm the required password.
  • Send acknowledgments for messages received by this exchange – Select this option if any application expects an acknowledgment.
  • For each application that expects an acknowledgment:
    • In the Inbound sender field, enter the caller identity (PI3) used by the application to connect. If you do not enter a caller identity, no acknowledgements are sent on this exchange.
    • Click on the ellipsis button (...) to select the community that sends the acknowledgment, and then select the connection string that corresponds to the back-end server which should receive the acknowledgment. This is how you select the delivery exchange that is used to send the acknowledgement.
  • An acknowledgment is sent to the Sender/Server pair, when the reception is completed and the corresponding incoming message is successfully unpackaged. This means that it is a protocol acknowledgment (Activator received the file). A receipt message is generated and sent through the selected application delivery exchange.

Advanced tab

  • Back up the files that go through this transport – Indicates whether the system backs up copies of the messages it retrieves from the back end. 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. Backups are needed to resubmit messages to back-end applications or resend messages to partners.
  • Process consumed messages using community collaboration settings –Select this option if you want the trading engine to perform routing using normal community collaboration settings. When you select this option, no See Post-processing of consumed messages.-related processing is performed on consumed messages.
  • Restrict maximum file size for this transport – Select this option to specify the maximum size of files a the exchange can handle.
  • If the trading engine receives a file larger than the maximum, the file is rejected and a message is written to the events log.

    Maximum file size – Enter the maximum file size in bytes. Do not use commas.

Related Links