Peer network settings

Use the Peer network settings page to:

  • Turn the peer network on and off for your peer community
  • Set how the peer community sends and receives ping messages
  • Determine whether inbound peer messages are written to a back-end file

To open the "Peer network settings" page, click Configure peer network at the bottom of the Peer network page.

Tabs and fields

The following sections describe the tabs and fields of the Peer network settings page.

General setting

Enable the peer network

Select this option to activate the peer community online and make it available to peer partners. When enabled, trading partner changes can be sent or received, either through auto-cloning or manually, depending on the peer partner rules settings.

There may be times when you want to disable the peer network temporarily. For example, to make changes to trading partners that you do not want cloned to peer partners. As long as the peer network is disabled, no changes are cloned, even to peers for whom the auto-clone rule is enabled.

Pings tab

Send pings

If you select this option, the peer community sends ping messages to peer partners at the specified interval. Sending pings at regular intervals helps all peers to be aware continuously of the operational status of other peers in the network.

Ping settings apply globally for all peers. If you enable pings for one peer, all peers are directed to send and receive pings. If pings are enabled, the other settings also apply to all peers.

The "Peer network" page has columns for the peer community and peer partners to display the status of the last pings sent or received.

A ping message is an application/x-cyclone-peer-to-peer message with content that identifies it as a ping message. A ping message is not encrypted or signed.

Ping interval

The time in minutes between ping broadcasts.

Hours to retain ping history

The time in hours to retain ping history. Ping history events are displayed on the "Peer network" page.

Ping tolerance

The number of minutes within which a peer partner must respond to a ping. If a partner fails to respond within the tolerance limit, a late warning is displayed for the partner in the "Peer partners" section on the "Peer network" page.

Advanced tab

Use these options to choose whether to write inbound ping messages or other inbound peer messages to a back-end application. Interchange provides a default file system application delivery for sending inbound peer messages to a back-end folder. Writing peer messages to the back-end may be helpful in troubleshooting or for auditing purposes.

Write inbound ping messages

Write only inbound ping messages to a back-end file system folder.

Write other inbound peer messages

Write other inbound peer messages to a back-end file system folder.

Peer message folder maintenance: Peer messages are small, so do not rapidly create disk space issues. If you select this option, it is a good practice to apply the same global purge and backup configuration settings as for trading engine messages.

Related topics

Related Links