Peer network cloning restrictions

The following information details the restrictions of the peer network cloning process.

Global attributes

The peer networking feature does not clone certain global attributes to remote peer partners. Instead, the settings must be manually configured on the remote peer partner server. This ensures each peer partner remains synchronized within the peer network and allows for successful trading. The following are settings and attributes that are not cloned and must be manually configured:

  • Global embedded servers (for any applicable transport)
  • Global external SMTP server (any protocol that has SMTP as a transport)
  • Global transport settings (for protocols):
    • FTP
    • SFTP
  • Message attributes templates
  • IP address whitelist

Deleting objects when auto-cloning is turned off

If auto-cloning is turned off and objects are deleted on the peer network main server that was previously cloned to a peer partner, these objects are not deleted when a manual clone occurs on the main server. These objects include CPAs, trading pickups, and trading partners.

To delete these objects and remain synchronized with all of the peers in the network, you must manually log in to each peer partner server and remove or delete the same objects.

Note: Application pickups and deliveries are dropped and rebuilt on peers when cloned.

Generated SSL certificates

All generated SSL certificates for any applicable transport are not cloned to the peer partner server. The administrator must manually import the SSL certificate to ensure successful trading and synchronization between peer partners.

Asynchronous AS2 message disposition notifications (MDNs)

All asynchronous AS2 MDNs (returned receipts) are correctly recognized in a peer network environment if the message is returned on a trading engine different from the original request. This is so that the original transfer of the message is correctly returned.

PeSIT trading pickup routing IDs

PeSIT trading pickups can have multiple routing IDs, but the additional routing IDs are not cloned. PeSIT routing IDs must be manually added to each peer partner.

Importing a backed-up Interchange system configuration

Peer Network auto-cloning will not occur for the objects you import through the system import feature.

Workaround: After you execute a system import and restart the trading engine, if you have Peer Network auto-cloning configured, you can force peer cloning by re-saving the objects that you want to clone.

Related topics

Related Links