RoboServer can be started in several different ways:
-
By clicking the RoboServer program icon (or the RoboServer
with Scheduler program icon if you want to start the Scheduler
also).
-
By invoking it from the command line, which is described in
detail below.
-
By running it as a service. For more information about running RoboServer as a
service, see the Installation
Guide.
To invoke RoboServer from the command line, open up a command
window and type:
followed by Enter. If you have installed RoboServer correctly as
described in the Installation Guide,
then the following is printed in the command window after which
RoboServer terminates:
RoboServer 7.0 (C) 1999-2009 Kapow Technologies
Detected the following plugins:
...
Usage: RoboServer [-maxConcurrentRobots <num>]
[-maxQueuedRobots <num>] [-maxClippingSessions <num>]
[-verbose] [-version]
[-scheduler]
-service <service-name:service-parameters>
Available services:
...
|
RoboServer Help Text
The dots indicate information that depends on your installation.
If something different than the above is printed in the command window,
then please confirm that you have installed RoboServer as described in
the Installation Guide.
No matter how RoboServer is started, it accepts the following
parameters:
|
Parameter
|
Description
|
|
-maxConcurrentRobots
<num>
|
This parameter specifies the maximum number of
robots that can run at the same time. Additional robot execution requests will be
queued. The parameter is optional. The default value is 20. The
minimum value is 1, and the maximum value is
50.
Example: -maxConcurrentRobots
3
|
|
-maxQueuedRobots
<num>
|
This parameter specifies the maximum number of
robots that can be queued for execution. If this queue size is reached, additional robot
execution requests will be rejected by RoboServer. The parameter
is optional. The default value is 50.
Example:
-maxQueuedRobots 25
|
|
-maxClippingSessions
<num>
|
This parameter specifies the maximum number of
clipping sessions that can exist on this RoboServer. This
parameter is optional. The default value is 50. The minimum
value is 0.
Example: -maxClippingSessions
20
|
|
-verbose
|
This optional parameter causes RoboServer to output
status and runtime events.
|
|
-version
|
This optional parameter causes RoboServer to output
the version number, and then exit.
|
|
-scheduler
|
This optional parameter enables the Scheduler part
of RoboServer as well as the embedded web server that drives the
Scheduler web interface.
|
|
-service <service-name:
service-parameters>
|
This parameter specifies a RQL or JMX service that
RoboServer should start. This parameter must be specified at least once,
and may be specified multiple times to start multiple services
in the same RoboServer. The available services depend on your
installation.
Example: -service
socket:50000
Example: -service
jmx:50100
|
RoboServer Parameters
There is no required ordering of the parameters. For more
information on RQL services, see RQL Services.
The JMX service provides management information from the RoboServer on
the specified port.
Starting RoboServer
