Chapter 1 Jaguar Configuration

Using File Viewer and the Runtime Monitor

The File Viewer and the Runtime Monitor allow you to track a Jaguar server's performance and statistics.

File Viewer

The File Viewer allows you to monitor:

REQUESTLOG - the httprequest.log file described in "HTTP logging and statistics".
SRVLOG - the srv.log file tracks server events and any configured tracing events. See "Log/Trace" for information regarding configuration of the log file and trace flags.
ERRORLOG - the httperror.log file tracks HTTP errors, such as a request for an HTML file that does not exist. If you define additional servers, the name of the log file is prepended with the server name. For example, if you create a server named Test_server, then HTTP error messsages for that server are directed to the Test_serverhttperror.log file.

Before you bring up File Viewer, make sure that a listener is configured with a protocol of TDS and a port number of 7878. See "Preconfigured listeners" for more information.

To bring up File Viewer:

Double-click the server for which you want to view files.
Highlight the File Viewer icon.
Select File | File Viewer Display.

When the File Viewer appears, configure the following items:

File - select the file you want to view from the File drop-down list.
Start/Stop - the Start/Stop button allows you to start and stop real-time viewing.
Refresh - select the frequency of the refresh rate from the drop-down list.
Previous/Next - allows you to scroll through the current file if it is too large to view or if you have selected a start position that does not start at the beginning of the file.
File Size - this field displays the current file size in bytes.
Start Position - select the start position of the file you are viewing. Your options are:
- Tail - display as much of the end of the file as fits on the screen.
- End - clear the file display. When you click Start, only the new entries into the file will display.
- Top - display the file starting from the top.
- Specify Position - allows you to select a starting position by positioning a slider. Choose the incremental position from the beginning of the file.

Runtime Monitor

The Runtime Monitor allows you to monitor server events and statistics, which may help you anticipate and prevent server problems.

To start the Runtime Monitor:

Double-click the Servers icon.
Double-click the server you want to monitor.

The Runtime Monitor can connect to other Jaguar servers via an IIOP listener. The server configuration identifies the host and port number to which the Runtime Monitor attempts to connect.
Click the Runtime Monitor icon.

The Runtime Monitor displays the folders listed below. For each of the top-level groups, there are subgroup folders. Click the subgroup folder whose statistics you want to view.

Packages - monitor events and statistics for a specific package, or for all packages on the server.
Connection caches - monitor a specific connection cache or statistics for all caches.
Network - monitor protocol-specific session information.

When viewing a subgroup's counters, you can change the view by selecting any of these options from the File menu:

Refresh - refresh the display to obtain the latest counters.
Per-Second - display the per-second values.
Counter - display the accumulated value.
View Values... - view the values in a separate dialog that automatically refreshes according to the refresh rate, which you can select from a drop-down list. If the group contains subgroups, expand those subgroups until you see the values.

If the subgroup contains counters, the current values of the counters display on the right side of the window.

There are two types of counters:

Snapshot counters - represent values at a particular point in time that are likely to either increase or decrease. For example, number of sessions, number of instances active, number of active connections, and so on. Snapshot counters do not display information when set at the per-second rate; instead they display "N/A."
Cumulative counters - represent values that always increment and never decrement. For example, number of invocations, number of connections opened, number of network requests, bytes read and written, and so on. Cumulative counters display both per-second and counter information.