Peer rules

Use the Peer partner rules page to control how an individual peer partner exchanges information with other peers. Each peer partner that you create has a dedicated Peer partner rules page.

Open the Peer partner rules page

Before you can open a Peer partner rules page, you must have at least one peer partner. See Configure a peer network.

To open the Peer partner rules page, click Rules to the right of a partner listed in the "Peer partners" section on the Peer network page.

Tabs and fields

Partner tab

Accept trading partner additions, changes and deletions from the peer partner

Enables the remote peer community to accept trading partners sent by this peer partner. In most cases, you should select this option.

If this option is turned off, you cannot automatically or manually send any additions or changes to this peer partner.

Auto-clone added, changed and deleted trading partners to the peer partner

Enables trading partners on the peer community instance to be sent to this peer partner each time a trading partner has been added or changed. The peer partner also is notified when trading community membership for a trading partner is changed.

If a trading partner is deleted from the peer community instance, this peer partner is notified to also delete the trading partner. In the case of ebXML, the trading partner and the related CPA are deleted.

Important: For auto-clone to work, the option Allow this partner to be cloned to peers must be selected in the trading partner object definition. The "allow cloning" option can be set for the trading partner in two places:

  • In the add trading partner wizard when you create a trading partner
  • Under Properties in the trading partner summary page after you create the trading partner

For trading partners configured to use the RosettaNet message protocol, clear the Allow this partner to be cloned to peers option. RosettaNet partners should not be distributed via auto-cloning.

Relay to the peer partner any trading partner additions, changes, and deletions received from other peers

When this option and auto-clone are selected, the peer community instance forwards any trading partners received from this peer partner to other peer partners for whom auto-cloning is active. Select this rule unless you have a specific reason not to relay. Relaying does not result in the same trading partner crisscrossing the peer network multiple times. This is because each peer message that contains a trading partner includes a history of where the partner has been sent and received. The peer network does not forward a trading partner when the history indicates other peer partners have received it already.

Caution   If you do not enable auto-cloning and instead prefer to use the trading partner cloning wizard, you need to manually track new and changed trading partners. See Manually clone a partner. This is especially the case if you re-name a trading partner and use the wizard to distribute the updated object. From a peer partner’s perspective, the updated trading partner seems new, but will have a routing ID that duplicates a current trading partner. With auto-cloning enabled, the system keeps track of new and changed trading partners, including trading partner name changes.

Application deliveries tab

Accept application delivery additions, changes and deletions from the peer partner

Enables the peer community to accept application deliveries sent by this peer partner.

In most cases, you should select this option. Clear this option only if you want to be absolutely sure that the peer community does not accept application deliveries from this peer partner.

Auto-clone added, changed and deleted application deliveries to the peer partner

Enables application deliveries on the peer community instance to be sent to this peer partner each time an application delivery has been added or changed. If an application delivery is deleted from the peer community instance, this peer partner is notified to also delete the application delivery.

Relay to the peer partner any application delivery additions, changes and deletions received from other peers

When this option and auto-clone are selected, the peer community instance forwards any trading community application deliveries received from this peer partner to other peer partners for whom auto-cloning is active.

Select this rule unless you have a specific reason not to relay. Relaying does not result in the same application delivery crisscrossing the peer network multiple times. This is because each peer message that contains an application delivery includes a history of where the delivery has been sent and received. The peer network does not forward a delivery when the history indicates other peer partners have received it already.

Application pickups tab

Accept application pickup additions, changes and deletions from the peer partner

Enables the peer community to accept application pickups sent by this peer partner.

In most cases, you should select this option. Clear this option only if you want to be absolutely sure that the peer community does not accept application pickups from this peer partner.

Auto-clone added, changed and deleted application pickup to the peer partner

Enables application pickups on the peer community instance to be sent to this peer partner each time an application pickup has been added or changed. If an application pickup is deleted from the peer community instance, this peer partner is notified to also delete the application pickup.

Relay to the peer partner any application pickup additions, changes and deletions received from other peers

When this option and auto-clone are selected, the peer community instance forwards any trading community application pickups received from this peer partner to other peer partners for whom auto-cloning is active.

Select this rule unless you have a specific reason not to relay. Relaying does not result in the same application pickup crisscrossing the peer network multiple times. This is because each peer message that contains an application pickup includes a history of where the pickup has been sent and received. The peer network does not forward a pickup when the history indicates other peer partners have received it already.

Trading pickup tab

Accept trading pickup additions, changes and deletions from the peer partner

Enables the peer community to accept trading pickups sent by this peer partner.

In most cases, you should select this option. Clear this option only if you want to be absolutely sure that the peer community does not accept trading pickups from this peer partner.

Auto-clone added, changed and deleted trading pickup to the peer partner

Enables trading pickups on the peer community instance to be sent to this peer partner each time a trading pickup has been added or changed. If a trading pickup is deleted from the peer community instance, this peer partner is notified to also delete the trading pickup.

For auto-clone to work, the option Allow this partner to be cloned to peers must be selected in the trading partner object definition. The "allow cloning" option is located in the add trading partner wizard and under Properties in the trading partner summary page.

Relay to the peer partner any trading pickup additions, changes and deletions received from other peers

When this option and auto-clone are selected, the peer community instance forwards any trading community trading pickups received from this peer partner to other peer partners for whom auto-cloning is active.

Select this rule unless you have a specific reason not to relay. Relaying does not result in the same trading pickup crisscrossing the peer network multiple times. This is because each peer message that contains a trading pickup includes a history of where the pickup has been sent and received. The peer network does not forward a pickup when the history indicates other peer partners have received it already.

CPAs tab

The rules on this tab apply only for peers that have ebXML trading configurations. The CPAs exchanged are related to e-commerce message traffic. These are not CPAs used by the peer network itself to exchange messages between peers.

Accept CPA additions, changes and deletions from the peer partner

Enables the peer community to accept CPAs sent by this peer partner.

In most cases, you should select this option. Clear this option only if you want to be absolutely sure that the peer community does not accept CPAs from this peer partner.

Auto-clone added, changed and deleted CPAs to the peer partner

Enables CPAs on the peer community instance to be sent to this peer partner each time a CPA has been added or changed. If a CPA is deleted from the peer community instance, this peer partner is notified to also delete the CPA.

For auto-clone to work, the option Allow this partner to be cloned to peers must be selected in the trading partner object definition. The "allow cloning" option is located in the add trading partner wizard and under Properties in the trading partner summary page.

If auto-cloning ebXML CPAs, make sure to select Allow this CPA to be auto-cloned to peers when importing or managing a CPA.

When auto-cloning is turned off, keep track of the CPAs that have been changed or added in order to manually clone the proper CPAs to other peers. See Manually clone CPAs.

Relay to the peer partner any CPA additions, changes and deletions received from other peers

When this option and auto-clone are selected, the peer community instance forwards any CPAs received from this peer partner to other peer partners for whom auto-cloning is active.

Select this rule unless you have a specific reason not to relay. Relaying does not result in the same CPA crisscrossing the peer network multiple times. This is because each peer message that contains a CPA includes a history of where the CPA has been sent and received. The peer network does not forward a CPA when the history indicates other peer partners have received it already.

Related topics

Related Links