MobiLink arbiter server utility (mlarbiter)

The MobiLink arbiter server ensures that only a single MobiLink server in a server farm is running as the primary server. This prevents redundant notifications in a server-initiated synchronization environment and preserves messages in a QAnywhere messaging environment.

The mlarbiter command is used to start the MobiLink arbiter server. This command is used in conjunction with the MobiLink server -ca option, which provides the MobiLink server with the host name of the arbiter.

Syntax

mlarbiter

Remarks

The MobiLink arbiter listens port 4953 by default.

If the MobiLink server is not able make a connection to the arbiter after the arbiter started, the MobiLink tries to establish the connection every 15 seconds, and displays periodic error messages.

If the arbiter connection is dropped after the MobiLink servers in the server farm elected a primary server, the primary server shuts down immediately and the secondary servers will try to re-establish the arbiter connection every 15 seconds. After a connection to the arbiter is established, the MobiLink servers will re-elect a primary server.

Example

The following example shows how to use the MobiLink arbiter server with a MobiLink server farm.

To use the MobiLink arbiter server

Start the MobiLink arbiter on a computer with the following command line.
mlarbiter

Start the MobiLink servers with a command line similar to the following. The MobiLink servers can be started on the same computer as the arbiter, or on different computers.

mlsrv12 -c parameter1 -lsc parameter2 -ca Host_1 -notifier

In the above example, parameter1 is the consolidated database connection parameter and parameter2 is the local MobiLink server connection parameter. All the MobiLink servers in the same server farm must contain the same setting for the -ca option.