Add or modify a PeSIT application pickup (embedded server)

Add a PeSIT application pickup (embedded server)

Prerequisite

Add a community. For details, see Add a community.

Procedure

1. In the user interface, select Trading configuration > Manage application pickup exchanges.
2. Click Add an application pickup exchange to open the exchange wizard.
3. Select PeSIT and click Next.
4. Select the From address and To address that match your needs.
5. Select Define a new embedded PeSIT server and click Next.
6. Complete the fields of the Configure the PeSIT server page.
7. • Server name – Enter a name for the new embedded PeSIT server. This is the name that appears in the embedded servers list.
   • Port – Enter the port on which the server will listen.
   • Access to this server requires a password – If you want the back-end application to provide a password to connect to your server, choose this option, and then enter the required password.
   • Clients must use SSL to connect to this server – Select this option if you want to secure the connections to your server over SSL/TLS. You will need to add a server certificate and private key for this server.
     • This server requires client authentication – Select this option if you require the client to authenticate itself with its own certificate when connecting (mutual authentication). This means you must import the client’s certificate to the community’s personal certificate list. If you want to use the pickup for multiple communities, you must import the same certificate to each community
7. Enter a name for the exchange to identify it in the user interface. Hint: Enter a name that is easily identifiable in a list of exchanges in the user interface.
8. Click Finish.

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, and can only be modified after you add the object.

Procedure

1. In the 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 Delivery exchanges page.
4. From the list of available exchanges, click the name of an exchange to open the maintenance page for that exchange.
5. View and modify fields as required. The fields are described in the following section.
6. After making any modifications, click Save changes.

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 integration 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 stops or restarts. Backups are needed to resubmit messages to back-end applications or resend messages to partners.
• Restrict maximum file size for this transport – Select this option to specify the maximum size of files a the exchange can handle.
• If Activator 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.