Search and display collaboration settings

Use the Show collaboration settings command to search and display the currently active collaboration settings between your communities and partners.

Viewing collaboration settings between parties is a way to check whether pickup and delivery exchanges are properly set up. Although this does not rule out possible infrastructure or configuration issues that could affect trading, it does help ensure that two parties’ security and packaging preferences are correct for outbound payloads and receipts from partners.

Before checking collaboration settings between two parties, make sure your community and the partner use the same type of message protocol and transport.

In addition, the partner’s transport must be the default exchange. This means the transport must be identified as the default delivery on the Partner deliveries page. Activator uses the default protocol to send messages to partners. Click Partner delivery on the navigation graphic on the partner summary page to check. The only exception is a transport for the ebXML message protocol. It must be present, but does not have to be the default transport.

Settings for inbound messages are controlled on the message validation page in the user interface. For more information see Inbound message validation rules.

1. On the main trading configuration page or a community summary page, click Show collaboration settings to display the Collaboration settings page.
2. If you navigated from a community summary page, by default the page uses the current community as the sender. You can use the default or change it.
2. Click Pick to select the community or partner sender (sent from) and the community or partner receiver (sent to).
3. Click Show settings. The system searches for the collaboration settings. It checks for any settings specific to the community or partner that override the default global settings. The page refreshes with the settings for the sender and receiver.
4. In some cases, the system reports that a collaboration could not be created between the parties. A common reason for failed collaboration is that the sender and receiver message protocols are not the same (for example, not both AS2).

Related topics

• Collaboration settings
• Manage default collaboration settings
• Manage community-specific collaboration settings
• Manage community-specific collaboration settings
• Manage community-to-partner specific collaboration settings
• Manage community-to-partner delivery specific collaboration settings