Add or modify a PeSIT trading pickup (embedded server)

Add a PeSIT trading pickup (embedded server)

Prerequisite

You must have a community. If you need to add a community, see Add a community.

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 Deliveries page.
4. Click Add a delivery exchange to open the exchange wizard (this represents a pickup from the community point of view).
5. Choose the message protocol PeSIT and click Next.
6. Select Define a new embedded PeSIT server and click Next.
7. Complete the fields of the Configure the PeSIT server page.
8. • Server name – Enter a name for this embedded PeSIT server. This name appears in the Embedded servers list.
   • Port – Enter the Port on which the server listens.
   • Community settings (Server) – Set the default identity exposed by the server to the partners.
     • Allow any valid community routing ID – If you select this option, the client connecting to this server can use any community routing ID as server ID (PI4).
     • Restrict to specific community routing ID – If you select this option, the client connecting to this server can only use the community routing ID you specify as server ID (PI4).
     • Use Password – Select this option if you must provide a password for connections to the partner. Then enter the required password.
   • Remote partner settings (caller)
     • Use Password – Select this option if the partner must provide a password for connections this embedded server. Then enter the required password.
   • Clients must use SSL to connect to this server – Check this if you want to secure the connections to your server over SSL/TLS. You must 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 need to import the client’s certificate in the partners’ personal certificate list and check the option Trust this for SSL server and/or client authentication. automatically adds the root certificate to the linked community trusted SSL root certificates.
8.  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.
9. Click Finish.

Modify a PeSIT trading 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.

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 trading pickup (embedded server) maintenance fields

PeSIT server settings tab

• Click the View setting for this embedded server link to view the server configuration. The linked page describes the server whose address and port are displayed in the Local connection string field.
• Community settings (Server) – Set the default identity exposed by the server to the partners. You can override or restrict the following settings per partner through the partner PeSIT delivery exchange(s).
  • Allow any valid community routing ID – If you select this option, the client connecting to this server can use any of the of the community routing IDs as server ID (PI4).
  • Restrict to specific community routing ID – If you select this option, the client connecting to this server can only use the community routing ID you specify as server ID (PI4).
  • Use Password – Select this option if you must provide a password for connections to the partner. Then enter the required password.
• Remote partner settings (caller) – You can override or restrict the following settings per partner through the partner PeSIT delivery exchange(s).
  • Use Password – Select this option if the partner must provide a password for connections this embedded server. Then enter the required password.
• Send acknowledgments for messages received by this exchange – If you select this option, the server sends an acknowledgment to the partner when it receives a file successfully. This occurs when the corresponding message is correctly unpackaged. This is a protocol level acknowledgement, which indicates only that Activator has correctly received the file.

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 remote partner. 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.
• 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.