Running the MobiLink server in a server farm

Separately licensed component required

Running the MobiLink server in a server farm is a feature of the MobiLink high availability option, which requires a separate license. See Separately licensed components.

A MobiLink server farm is an environment where there is more than one MobiLink server synchronizing the same set of remote databases with the same consolidated database. This is often required for large scale deployments or for fail-over capability. These MobiLink server farm deployments may require the use of the Relay Server if an HTTP communication link is used. For TCP-based streams, a TCP load balancer should work. When using multiple servers, restartable download does not work.

To enable shared server state

If you are using the Notifier with server-initiated synchronization, use the -lsc option to specify the local server connection settings. These settings are passed to the other servers in the farm so that they can connect to each other to share the handling of notifications. For example, if running on host farm_host22: mlsrv12 -x tcpip(port=3245) -zs server5 -lsc tcpip(host=farm_host22;port=3245) -c ...

MobiLink arbiter server

When running a MobiLink server farm with server-initiated synchronization or QAnywhere messaging, use the MobiLink arbiter server to make sure there is always one primary server in the farm. Having a primary server at all times prevents redundant notifications and lost messages.

Use the mlarbiter command to start the MobiLink arbiter and use the MobiLink server -ca option along with the -lsc option to start the MobiLink servers with the arbiter information. See MobiLink arbiter server utility (mlarbiter) and -ca mlsrv12 option.