Starts a Search Server that listens for client connections on the specified port number.

Starts an XML Search Server that listens for client connections on the specified port number.

Starts a Synchronization Server that listens for client connections on the specified port number.

Starts a HTTP Search Server that listens for client connections on the specified port number.

Starts a RuleBase Server that listens for client connections on the specified port number.

Starts a Search Server configured to access a remote Rulebase Server. Specify the host name of the Search Server and the port number on which the server listens for client connections. Use the

-h

switch with the

-m

switch.

Specifies the Rulebase Server Group.

Specifies the polling frequency of a Rulebase Server Group in seconds. Default is 1.

List of ZooKeeper servers based on the host name of the ZooKeeper server and the port on which the host listens for connections.

Specifies the number of requested match threads. The default value is 1. Specify this argument if your typical usage is a small number of long running searches that might require multiple threads.

Specifies the maximum number of times to retry (Max) when a connection to the database fails and the number of seconds (Wait) that a Search Server or the Rulebase Server waits to retry the connection. For example,

-y5,3

indicates that the Search Server or the Rulebase Server can try up to five times to connect to the database for every three seconds. The default value is

0,0

. If

Max=0

, the Search Server or the Rulebase Server retries indefinitely until the connection to the database succeeds.

Specifies the file that logs the standard output messages (

stdout

).

Specifies the file that logs the standard error messages (

stderr

).

Optional. Specifies the file that logs the error and debug messages.

Controls optional aspects of the Rulebase Server behavior.

Use the following Rulebase Server options:

0x0001 (1
10
). Stores the Rulebase cache in memory when no users are currently connected. Specifying this option improves the Rulebase Server performance, and omitting this option reduces the memory utilization.
0x0100 (256
10
). Forces the Rulebase Server to restart when a Rulebase read operation fails. This option is helpful when the database server bounces and disconnects the Rulebase Server’s connections. If you do not set this option, the Rulebase Server might fail a client’s requests that require database access. However, the clients that access the cached rules function normally.