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.

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.

Both mkreplica and syncreplica support the following options:

The –fship option places the packet files and shipping order files in one of the host’s storage bays and runs the shipping server to send the packet files to their destination host or to route them to an intermediate host.
The –ship option places the packet files and shipping order files in a storage bay, but does not invoke the shipping server. The packet files are sent the next time the shipping server polls the bay. For information about running the shipping server automatically, see c_automated_synch.html#sii-synch-40665.