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
|
-dataserver: |
(filename)
Read data from Data Server output file
instead of directly from data sources .If no file name is specified, default
output file (rtvdata.xml) will be used. If necessary, include local
directory path or http URL.
Example:
-dataserver:rtvdata.xml |
remote:primary,backup1 Read data from Data
Server instead of directly from data sources. Specify primary and backup servers. If no host is specified, local host
will be used. If no port is specified, default port (3278) will be used.
Designation of a backup server is optional; one or multiple backup servers can
be specified.
Example:
-dataserver:remote:host:8723,host:8080 |
remote:http://host:port/rtvdata,http://host:port/rtvdata_backup1
Read data from Data Server via servlet instead of
directly from data sources. Specify primary and backup servers. The host is web server hosting
the servlet. The port is port used by the web server. Designation of a
backup server is optional; one or multiple backup servers can be specified.
Example:
-dataserver:remote:http://host:8723/rtvdata,http://host:8080/rtvdata_backup |
name=Name;connect=primary,backup1 Specify
primary and backup named data server(s).
The name is the Name specified when this
data server was configured and connect is either
host:port
or, for servlet,
http://host:port/rtvdata.
Designation of a backup server is optional; one or multiple backup servers can
be specified.
Example:
-dataserver:name=MyDataServer;connect=localhost:56789,host:8080
-dataserver:name=London;connect=https://londonServer:8080/rtvdata,http://host:8080/rtvdata_backup |
-dataserver: |
(filename)
Read data from Data Server output file
instead of directly from data sources .If no file name is specified, default
output file (rtvdata.xml) will be used. If necessary, include local
directory path or http URL.
Example:
-dataserver:rtvdata.xml |
remote:primary,backup1 Read data from Data
Server instead of directly from data sources. Specify primary and backup servers. If no host is specified, local host
will be used. If no port is specified, default port (3278) will
be used. Multiple backup servers can be specified.
Example:
-dataserver:remote:host:8723,host:8080 |
remote:http://host:port/rtvdata,http://host:port/rtvdata_backup1
Read data from Data Server via servlet instead of
directly from data sources. Specify primary and backup servers. The host is web server hosting
the servlet. The port is port used by the web server. Multiple backup
servers can be specified.
Example:
-dataserver:remote:http://host:8723/rtvdata,http://host:8080/rtvdata_backup |
name=Name;connect=primary,backup1 Specify
primary and backup named data server(s).
The name is the Name specified when this
data server was configured and connect is either
host:port
or, for servlet,
http://host:port/rtvdata.
Example:
-dataserver:name=MyDataServer;connect=localhost:56789,host:8080
-dataserver:name=London;connect=https://londonServer:8080/rtvdata,http://host:8080/rtvdata_backup |
-dataserver: |
(filename)
Read data from Data Server output file
instead of directly from data sources.If no file name is specified, default
output file (rtvdata.xml) will be used. If necessary, include local
directory path or http URL.
Example:
-dataserver:rtvdata.xml |
//(host:port)
Read data from Data Server via socket
instead of directly from data sources. If no host is specified, local host
will be used. If no port is specified, default port (3278) will
be used.
Example:
-dataserver://remotehost:8723 |
remote:http://host:port/rtvdata
Read data from Data Server via servlet
instead of directly from socket. The host is web server hosting
the servlet. The port is port used by the web server.
Example:
-dataserver:remote:http://host:port/rtvdata |
name;connect Specify named data server(s).
The name is the Name specified when this data server was configured and
connect is either host:port
or
http://host:port/rtvdata.
Example:
-dataserver:name=MyDataServer;connect=localhost:56789
-dataserver:name=London;connect=https://londonServer:8080/rtvdata |
-dsenable:(dskey) |
Enable data source(s) for data
attachments and defined commands that have been configured to bypass data being
redirected through the specified data server(s).
The
dskey is the abbreviation for the data source as listed in the Attach to
Data and Define Command drop down menus, but in all lower case.
Example:
-dsenable:sql |
-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
|
-standby:warm |
Run a
backup Display Server without the overhead of maintaining the Alert and Cache data
sources.
The following actions will be delayed
until the backup server has become the
primary:
- Loading definition files (i.e. Global, Alert,
Cache)
- Preloading display files specified in
initialization (.ini) files or on the command line
NOTE: Although the -standby:warm option
reduces overhead because data sources do not provide data until a failover, it
is important to note that Alert and Cache data definitions will not start
collecting data until the first client connects. Therefore, any previous alert
state or cached data from the primary server will not be available to the
backup.
Example:
-standby:warm
|
-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)
|
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 |