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.
Communication between replica hosts
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.

Communication between replica hosts

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.

To accomplish this, you may have to update the hosts file, hosts NIS map, or Domain Name Service. To verify TCP/IP access, use rcp on each sending host to copy a file to the receiving hosts or use store-and-forward to send a packet (see Store-and-forward packet submission).

Note: If hosts in your network are known only by their IP addresses, you can use the IP addresses instead of host names, and no resolution is necessary.