Configure a peer network

The procedure in this topic shows the basic steps for setting up a peer network. You must apply these steps to each instance or cluster of Interchange that you want to belong to the peer network.

  1. All instances of Interchange must use Interchange 5.8 or later.
  2. If the ebXML message protocol is used for exchanging messages with trading partners, all instances must be Interchange 5.8 or later. Note that ebXML can be used for peer-to-peer communications, but a protocol with less overhead, such as AS2, is recommended.
  3. Follow the usual procedure for installing, configuring and, if applicable, setting up multiple-node clusters. See the appropriate sections of the documentation for details. Make sure each instance of Interchange is operating properly before proceeding with the peer network configuration.
  4. If you plan on using the peer network to link instances of the trading engine that are actively trading, see Manage duplicate messages in peer network.
  5. Log on to the user interface and click Peer network > Manage peer network on the toolbar to open the Peer network page.
  6. Click Create the peer community to launch the Add Community Wizard. Follow the prompts to add a peer community profile.
  7. When you add a peer community, the system includes the following in the profile:
    • An AS2 pickup for receiving messages from peer partners. This exchange is added as a convenience, because most peer partners choose AS2 for exchanging peer messages. If you want to use a different message protocol, edit the peer community.
    • A file system application delivery. This is added in case you want to route messages received from peer partners to the file system for debugging. It is not used unless you explicitly configure this behavior under peer network settings.
  8. Repeat this step for each Interchange instance.
  9. Export the peer community profile. Repeat this step for each Interchange instance.
  10. Distribute the peer profiles among the Interchange instances or clusters. For example, if there are three instances, distribute as follows:
    • Peer community A gives exported profile file to peers B and C.
    • Peer community B gives exported profile file to peers A and C.
    • Peer community C gives exported profile file to peers A and B.
  11. For each Interchange instance, import the peer partner profiles. For example, if there are three instances, import as follows:
    • Peer community A imports peer partner profiles B and C.
    • Peer community B imports peer partner profiles A and C.
    • Peer community C imports peer partner profiles A and B.
  12. On the peer network page, click Add a peer partner.
  13. Optionally, on one Interchange instance, click Configure peer network on the peer network page and change the ping configuration. Any changes you make affect ping behaviors for all peers. See Peer network settings.
  14. You may need to manually perform one or more of following tasks to ensure consistency across the network.
    • Inbound message validation – All peer communities should use the same settings for inbound message validation across the peer network. This becomes a maintenance issue if peer communities use other than the default settings. Note that for a peer community, the setting for duplicate EDI messages is not applicable.
    • Outbound collaboration settings – All peer communities should use the same settings for outbound collaboration settings across the peer network. This becomes a maintenance issue if peer communities use other than the default settings. If you configure peer partner settings, these must be replicated manually across the peer network. Trading partners that are sent as peer messages are packaged just like any outbound trading message.
    • Configuration files – Configuration of Interchange can require editing various system files. You may want to make sure that a change to a configuration file for one peer instance of Interchange is reflected in the same file for another peer instance. You need to know which system files have been changed and then determine whether to duplicate the changes across the peer network.
    • For instance, you may want one peer instance to send email notifications to different recipients than another peer instance. In that case, the alerts.xml file should not be the same across all instances. Conversely, you may want custom settings in the log4j.properties file to be the same for all peer communities so all peer instances generate logs at the same event levels.
    • Post-processing scripts – The names of post-processing scripts configured in trading communities and partners are replicated across the peer network, but not the script files themselves. If you are using post-processing scripts, you must make sure the script files are available on each peer. If you update a script, you also must update it on each peer.
  15. For each Interchange instance, go to the peer network page where all peer partners are listed. Click Rules next to each partner name and set the rules for distributing trading partner profile updates within the peer network. See Peer rules and Peer network business use cases.

Related topics

Related Links