Community trading pickups and partner deliveries

Trading pickups are located in community objects. A trading pickup specifies how you want the community to pick up or receive documents over the Internet from a remote partner.

Partner deliveries are located in partner objects. A partner delivery specifies how a community sends documents to a remote partner.

The user interface lists trading pickups and partner deliveries by the message protocol they use for trading. A message protocol supports one or more transports.

Your local community and trading partner can use the same or a different message protocol for exchanging messages. However, if you use different protocols, you must be prepared to return receipts via the same protocol as the payloads were received. The partner should configure his system likewise.

The following figure illustrates a trading relationship where the local community and the remote trading partner use different message protocols. The community prefers receiving payloads via the AS1 protocol. The partner prefers receiving payloads via AS2. To accommodate these preferences, both parties must be prepared to send and receive via AS1 and AS2. In this scenario, the community receives a payload via AS1 and returns a receipt to the sending partner via AS1. Meanwhile, the community sends a payload via AS2 and receives a receipt from the receiving partner via AS2. This figure shows the community and partner send via different message protocols.

In the figure above, on the community side, AS2 is the designated default protocol for sending in the partner profile. On the partner side, AS1 is the default for sending. This is necessary because Activator uses the default protocol in the partner profile for sending payloads. See Search and display collaboration settings.

The following table lists the message protocols and related transports communities and partners can use for exchanging messages. The message protocols you can use depends on your user license. Select Help > License information on the top toolbar in the user interface to see what protocols your license supports. Communities also require application pickup and delivery exchanges. For information about these exchanges, see Application deliveries and Application pickups.

The following table shows the pickup and delivery types you can use to support various message protocols in Activator. The packaging options column indicates whether a message protocol supports signing and encryption of messages using digital certificates. It also indicates whether message compression is supported.

No packaging notes

The pluggable embedded server transport is available only to users who have the optional Software Development Kit. If you are an SDK user, see the pluggable embedded server chapter in the SDK Developer’s Guide for configuration information.

Work with trading pickups and deliveries

• Add a trading pickup
• Modify a trading pickup
• Add a partner trading delivery
• Modify a partner trading delivery