Command Line Options: Display Server
The
following command line arguments are enabled when you run
the
Display Server from a Windows
Command Prompt or UNIX terminal window. For command line options for your data
source, refer to the Data Sources section of this documentation. NOTE: If a command line argument contains
a space or a semicolon, then the entire argument must be enclosed in quotes
(e.g.:
"-sub:$data:my Data").
| Name |
Description |
| -daemon |
Run the Display
Server as a daemon process. NOTE: This parameter must be the first command
line argument given.
Example:
run_displayserver
-daemon
|
| -imageformat |
Specify image format:
jpg or png. By default, the Display Server will
automatically select the image that results in the fewer number of bytes for
each display. Example:
-imageformat:jpg |
| -imagequality: |
A value between 0 and 100
which controls the quality of the generated images. If the value is 100,
the Display Server will output the highest quality image with the lowest
compression. If the value is 0, the Display Server will output the lowest
quality image using the highest compression. Default is 75.
Example:
-imagequality:75
|
| -jmxport:(port
number) |
The port number
to use to expose JMX methods to monitor
and manage the Display Server. There is no default port. If not
specified, these JMX methods will not be accessible.
Example:
-jmxport:9998
|
| -passclientlogin |
Pass
Enterprise RTView login information into all data sources that have the Use
Client Credentials option enabled.
NOTE: Some data sources do not support
this feature.
For information on Application Options for your data source, refer to the
Data Sources section of this
documentation.
Example:
-passclientlogin
|
| -sub:(substring:subvalue) |
Add a substitution string/value pair.
Multiple substitution pairs can be specified on the command line. NOTE:Substitution
strings cannot contain the following:
|
:
|
|
|
.
|
tab
|
space
|
,
|
;
|
=
|
<
|
>
|
'
|
"
|
& |
/ |
\ |
{ |
} |
[ |
] |
( |
) |
If your substitution value contains
single quotes, you must escape them using a /.
Example:
-sub:$1:myValue
-sub:$filter:Plant=/'SanFrancisco/' |
| -timezone |
Set the default timezone
for interpreting and displaying dates. Include a Java timezone
ID or a custom ID, such as "GMT-8:00". Unrecognized IDs will
be treated as GMT.
If you run the Enterprise
RTView Builder with a valid timezone parameter and then save Application
Options, the timezone information will be persisted.
To prevent the persisted
timezone value from being used, pass "none" as the timezone ID.
Example:
-timezone:US/Eastern
-timezone:none |
| -u(milliseconds) |
Set update rate
in milliseconds. Default is 2000.
Example:
-u5000
(updates
every 5 seconds)
|
Options Enabled with Alerts
In addition to the General Options, the
following command line arguments are enabled with
the Alert data
source.
| Name |
Description |
| -alertds:history:(size of table) |
Sets the number of rows
that are stored in the AlertTable.
Example:
-alertds:history:1000 |
| -alertds:alertdef:(filename) |
Adds an alert definition file. Cannot specify
substitutions. To specify substitutions, use the
Application Options dialog.
Example:
-alertds:alertdef:myalerts.rtv |
| -alertcleartime:(number of seconds) |
Specifies the rate, in seconds, to remove
cleared alerts. If set to
greater than
zero, all cleared alerts are removed every x seconds where x is the value
specified.
Example:
-alertcleartime:30000 |
| -alertinitdelay:(number of
milliseconds) |
The number of seconds to
wait after startup to begin executing alerts.
Example:
-alertinitdelay:5000 |
| -alertds:enabled:(true or false) |
Enables/disables all
alerts in the active alert definition files.
Example:
-alertds:enabled:false |
|
