Home
Administering
Learn how to administer the product.
Administering HCL Compass Multisite
Administering HCL Compass Multisite
Packet transportation methods and configuration
The method you choose for transporting packets between replicas depends on connectivity. If your replicas do not have IP connectivity, you must use a file-based transport method. If your replicas have connectivity, you can use the store-and-forward facility.
Store-and-forward
The MultiSite store-and-forward facility (the shipping server) is a file-transfer service that automates the transport phase of replica creation and synchronization. It can handle packets of any size (up to the maximum packet size specified in the shipping.conf file on Linux™ and the UNIX™ system or the MultiSite Control Panel on Windows™), can route files through a series of MultiSite hosts (one hop at a time), and includes support for handling data-communications failures.
Store-and-forward packet submission
When you generate a replica-creation or update packet, you can specify that the store-and-forward facility must deliver it.
Packet size limitation
The hosts must be able to communicate with each other. If your network uses host names, the sending host must be able to resolve the receiving host's name to an IP address.

Packet size limitation

The hosts must be able to communicate with each other. If your network uses host names, the sending host must be able to resolve the receiving host's name to an IP address.

The mkreplica and syncreplica commands fail if they try to create a packet larger than the size supported by your system. To prevent this problem and improve reliability, use the -maxsize option to divide the packet into multiple packets:

multitool mkreplica -export -maxsize 1g ... 

multitool syncreplica -export -maxsize 500m ...

multiutil mkreplica -export -maxsize 1g ... 

multiutil syncreplica -export -maxsize 500m ...

You can also specify maximum packet sizes in the shipping.conf file (Linux™ and the UNIX™ system) or MultiSite Control Panel (Windows™).

For information about default packet size limits, see the mkreplica reference page.