Running
the Data Server
You
can run the Data Server as an application with a graphical user interface
or as a daemon process. Running the Data Server as a daemon process will
allow you to run without a display.
NOTE:
The first time you run the Data Server you must run it as an application
to configure the initial settings.
On
Windows
You
can start the Data Server from either the Windows Start Menu or the Command
Prompt window.
From the Windows Start Menu:
|
Select
Start-->Programs-->Enterprise
RTView Data Server |
NOTE: When you start the Data Server
from the Windows Start menu, it runs from the demos directory. The Data Server
will try to read initialization (.ini) files and resolve XML sources containing
relative paths from that directory. To start the Data Server in another
directory, you must run Enterprise RTView from a command window. NOTE: It is
possible to
specify a directory for your
initialization files. From
a Command Prompt Window:
In
an initialized command window:
On
UNIX
In
an initialized terminal window:
To run the
Data Server as a daemon process, you must run it from a Windows Command Prompt
or UNIX terminal window and the -daemon parameter
must be the first command line argument given.
Several command line options are
supported for the Data Server, see
Appendix C for more information. Java options specified in
RTV_JAVAOPTS
will be used by the
run_dataserver scripts. NOTE: These options
will not be used when the Data Server is started from the Windows Start
menu.
Data source specific options are read in from
initialization files created in the Display Builder. For information on creating
initialization files or command line options for your data source, refer to
Application Options or Command Line Options under the Data Sources
section of this documentation.
Configuration
When
running as an application, the Configuration tab allows you to specify
settings for the Data Server. Click Save Configuration to save these
settings. If you select the Show Data in Console check box, the
Data Server Console will output a line for each piece of data that is served.
When running as a daemon process, this information will be output to the
command window in which the daemon process was started.
To
begin serving data, click Start Serving Data. Click Stop Serving
Data to end this process. If you configure the Data Server to output
to an XML file, when you start serving data information will be added to
the output XML file each time new data is received for each attachment
in all of the specified data configuration files. If you configure the
Data Server to output data via socket, when you start serving data the
Data Server will receive data requests from Enterprise RTView clients (Display
Builder, Display Viewer Application, Display Viewer Applet) indicating
what data is needed for currently running displays.
Server
Modes
This
information must correspond with information entered in the Application
Options - Data Server dialog. NOTE: By default, the Data Server
starts in File Mode. If you change the Server Mode, then you must save
the configuration and restart the Data Server.
File
Data
redirected from configuration files will be output to an XML file. NOTE:
The XML data source is never redirected through the Data Server when you
output data to a file. When
you start serving data, information will be added to the output XML file
each time new data is received for each data attachment in all of the specified
data configuration files.
Output
File Name - Name of file output by the Data Server containing data
from specified configuration files. Default output file name is rtvdata.xml.
Data
Configuration Files
Specify
which data configuration (.rtv) file(s) will be used to generate the output
XML file. Data configuration files are display (.rtv) files created in
the Display Builder that contain attachments to data you want to redirect
through the Data Server.
|
Add
- Add a data configuration file to the list. If a data configuration file
is added while the Data Server is serving data, it will start serving data
for attachments in that file as soon as new information becomes available. |
|
Remove
- Remove the selected data configuration (.rtv) file from the list. If
the Data Server is serving data when a file is removed, it will stop serving
data for that file immediately. |
Socket
Data
requested by Enterprise RTView clients will be output via socket. When
you start serving data, the Data Server will receive data requests from
Enterprise RTView clients indicating what data is needed for currently
running displays. NOTE: By default the Enterprise RTView client will connect
directly to the XML data source, while all other data sources are redirected
through the Data Server. For information
on redirecting the XML data source, see Application
Options - Data Server.
Port
- Specify the port over which the Data Server will communicate with
Enterprise RTView. You do not need to specify a port if you are using the
default: 3278.
Use
Secure Sockets - If selected, a secure socket layer (SSL) will be used.
Enterprise RTView clients may connect directly via socket or through the
intermediary Data Servlet using HTTP or HTTPS requests
to receive data. NOTE: Using the servlet requires a separate installation
process, see the Data Servlet
section for details.
Use
Client Credentials for Database Login -
Pass Enterprise
RTView login information into all data sources that have the Use Client
Credentials option enabled. NOTE:
Use
Client Credentials for Database Login only works in Socket mode.
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.
Send Changed Data Only
- If selected, data will be sent only when it has changed. If you want
to continuously plot data that has not changed in the trend graph, deselect
the Send Changed Data Only checkbox to send all the data
regardless of whether or not it has changed. NOTE: Sending all data can
lead to performance issues given the amount of information that will be
sent over the socket.
Preload Data for
Configuration Files
You
may specify configuration files for data that you want the Data Server
to preload so it will be immediately available to any clients that request
it.
Data
Configuration Files
Specify
which data configuration (.rtv) file(s) will be preloaded by the Data Server.
This data will be immediately available to any clients that request it
later, and will be updated during Data Server updates. Data configuration
files are display (.rtv) files created in the Display Builder that contain
attachments to data you want to redirect through the Data Server. Enabled
if the Preload Data for Configuration Files flag is selected.
|
Add
- Add a data configuration file to the list. |
|
Remove
- Remove the selected data configuration (.rtv) file from the list. |
Console Options
| Show
Data in Console - If selected, the Data Server Console will print out
a line for each piece of data that is being served. |
General Options
| Start/Stop
Serving Data - Start or stop serving data. |
| Save
Configuration - Save settings to an initialization file (DATASERVER.ini), which will be used next time you run the Data Server. NOTE: Unless you
specify a directory for your initialization files,
you must run the Data Server from the same directory in which the initialization
(.ini) file
was saved. |
| About - Click on
to read about Enterprise RTView. |
| Exit
- Exit the Data Server, stop serving data and close the Data Server window. |
Console
The
Console tab records errors and information. If you select the Show Data
in Console check box on the Configuration tab, the console will
also display a line for each piece of data that is being served. Click
the Clear button to purge all data from the console.
Clients
The
Clients tab appears when you start the Data Server in Socket mode. NOTE:
By default, the Data Server starts in File Mode. If you change the Server
Mode, then you must save the configuration and restart the Data Server.
Connections
This
table displays one row for each client that is connected via socket to
the Data Server. When clients are connected through the Data Servlet, one
connection is shown for the servlet and separate connections are displayed
for each HTTP/HTTPS client. If an HTTP/HTTPS client exits under abnormal
circumstances, it may not be removed from the table for several minutes.
For each
client connection, the table contains the following columns.
| Client
ID - A unique number assigned by the Data Server to this client connection.
The first client connection is assigned an ID of 1, the second is assigned
an ID of 2, etc. The ID for an HTTP/HTTPS client will contain extra digits,
starting with the ID of the Data Servlet's connection. For example, if
the servlet is assigned a client ID of 1, then the first HTTP/HTTPS client
will be assigned an ID of 10001, the next will be 10002, etc. ID numbers
will not be reused during a Data Server session. |
| Address
- IP address of the client. Clients running on the same host as the Data
Server will display the IP address 127.0.0.1. |
| Host
- Name of the host on which the client is running. Clients running
on the same host as the Data Server will display the host name
localhost.
If a client's host cannot be determined, the IP address will be shown instead. |
| Duration
- Time elapsed in this client's session with the Data Server. |
| Last
Data Sent - Number of characters of XML data contained in this client's
most recent update. |
| Total
Data Sent - Number of characters of XML data contained in all updates
during this client's session with the Data Server. |
Number
of Clients
This
trend graph displays the number of clients (direct socket, servlet, HTTP/HTTPS)
connected to the Data Server over the past hour.
|
