Manage community-to-partner specific collaboration settings
You can specify collaboration settings that apply between one specific community and one specific partner.
These settings:
- Override:
- Default collaboration settings
- Community-specific collaboration settings
- Partner category-specific collaboration settings
- Are overridden by any collaboration settings that you set between the community and a delivery of the partner.
Use example: Your default collaboration settings could specify that messages sent over the AS2 protocol should return signed acknowledgements. Partner A might want to send unsigned acknowledgements. You can specify that Partner A send unsigned acknowledgements for the AS2 protocol, while all other partners in the community use the default or community-level settings.
Select a partner for specialized collaboration settings with a community
Before you can set specific collaboration settings between a specific community and a specific partner, you must select the partner for specialized collaborations. To do this you must have:
- At least one community.
- At least one partner.
To specialize collaboration between a community and a partner:
- Open a community summary page.
- Click Collaboration settings on the navigation graphic at the top of the page to open the Configure community-specific collaboration settings page.
- In the left pane, from the tasks list, click Specialize collaboration settings for a partner to open the Add special collaboration settings for a partner page.
- Complete the Messages sent to field. Click Pick a partner and then select a partner from the list of available partners in the pop-up window.
- Click Add.
- The partner that you selected is added to the list of partners associated with the community.
Specialize community-to-partner collaboration settings
- Open a community summary page.
- Click Collaboration settings on the navigation graphic at the top of the page to open the Configure community-specific collaboration settings page.
- In the left pane, in the community/partner tree, click the name of a partner to open the Configure community to partner specific collaboration settings page.
- Select the settings to specialize and modify settings as required.
- After making any modifications, click Save changes.
- The following list describes the override options:
- Pick the sender routing ID – If a community has multiple routing IDs, you can pick one as the ID that is included in packaged messages.
- Pick the receiver routing ID – If a partner has multiple routing IDs, you can pick one as the ID that is included in packaged messages.
- Set sending rules for the AS1 message protocol – Overrides the AS1 global defaults. For field descriptions see AS1 default settings.
- Set sending rules for the AS2 message protocol – Overrides the AS2 global defaults. For field descriptions see AS2 default settings.
- Set sending rules for the AS3 message protocol – Overrides the AS2 global defaults. For field descriptions see AS3 default settings.
- Set sending rules for the AS4 message protocol – Overrides the AS4 global defaults. For field descriptions see AS4 default settings.
- Set sending rules for the Secure file message protocol – Overrides the secure file global defaults. For field descriptions see Secure file default settings.
- Set sending rules for the Generic email message protocol – Overrides the secure email global defaults. For field descriptions see Generic email default settings.
- Set sending rules for the Odette FTP V2 message protocol – Overrides the OFTP 2.x global defaults. For field descriptions see Odette FTP V2 default settings.
- Set sending rules for the PGP message protocol – Overrides the PGP global defaults. For field descriptions see PGP default settings.
- Set sending rules for the cXML message protocol – Overrides the cXML golbal defaults. For field descriptions see cXML default settings.
- Set sending rules for the RosettaNet (RNIF) 1.1 message protocol – Overrides the RosettaNet 1.1 global defaults. For field descriptions see RNIF 1.1 default settings.
- Set sending rules for the RosettaNet (RNIF) 2.0 message protocol – Overrides the RosettaNet 2.0 global defaults. For field descriptions see RNIF 2.0 default settings.
- Set sending rules for the Web services message protocol – Overrides the web services global defaults. For field descriptions see Web Services default settings.
- Set resend attempts and interval for reliable messaging – Overrides the defaults for resending messages. For field descriptions see Reliable messaging default settings.
- Specify the signing certificate to use – Lets you specify the certificate to use for signing messages, if it is different than the community default signing certificate.
- Specify the partner's encryption certificate to use – Select this option to choose which of the partner’s certificates to use to encrypt messages.
- Specify the receipt signing certificate to use – Select this option to choose which of the partner’s certificates to use to sign message receipts.
- Specify whether to encrypt or sign messages and choose algorithms– Overrides the global and community-level defaults for encrypting and signing messages. This option overrides not only the default collaboration settings for your installation, but the protocol-specific signing and encrypting settings you might have set up for this partner.
- When selected the following fields display.
- Encrypt messages – Select this check box to encrypt the messages you send.
- Message encryption algorithm – If you select encrypt messages, select an algorithm.
- Sign messages. Partners use your certificate to verify you as the sender – Select this checkbox to digitally sign the messages you send.
- Message signing algorithm – The algorithm for creating a hash of the unencrypted message. This hash is a number that is encrypted with your community’s private key. It is decrypted by the partner using the community’s public key. The partner rehashes the decrypted message and compares the result with the hash that came with the message. If the two are identical, it ensures the contents have not been altered.
- Specify the delivery exchange to send messages to – Lets you choose the transport for sending messages to this partner.
Related topics