After you start and log in to TIBCO StreamBase^® Runtime Administrator, you see an overview screen that displays the Cluster Browser in the left-hand pane and the Manage Nodes display in the right-hand pane, as shown in Figure 1.2, “TIBCO StreamBase® Runtime Administrator”. The left-hand pane contains these areas:

	You can use the refresh button in the Cluster Browser to update the displayed information.

Figure 1.2. TIBCO StreamBase^® Runtime Administrator

When you select an application node, information about the node is displayed in the right-hand pane, as shown in Figure 1.3, “Application node display”.

Figure 1.3. Application node display

Recall the managed element hierarchy shown in TIBCO StreamBase^® Runtime Architects Guide -- you can see that most elements are contained within a node. To access these elements in TIBCO StreamBase^® Runtime Administrator, you must be logged into the node (usually this happens automatically when you log into a cluster). When you are logged into a node a set of tabs tabs appear as shown in Figure 1.3, “Application node display”. These tabs provide detailed displays and control of the individual managed elements. The tabs for a node are:

Nodes generate log messages for normal and exceptional conditions. These log messages are available in:

No matter where log messages are viewed, they have the same content:

In addition, log messages displayed in the log message monitor also contain the node name that generated the log message. Here is an example log message displayed in thelog mesasge event monitor:

Node Name = A
Date Time = 2008-09-10 12:57:38 
Event Topic = kabira.kts.security 
Event Identifier = switchadmin::EventIdentifiers::OperatorActionSucceeded 
Event Originator = switchadmin::PluginServiceImpl:1 (344579:8358104:7100:1 offset 67017096) 
Message = Administrator command [display] on target [security] executed by principal [guest] succeeded.

Log message monitor

The log message monitor provides asynchronous notification of log messages reported by all managed nodes. Figure 1.4, “Log message monitor” shows the running message monitor.

Figure 1.4. Log message monitor

Figure 1.5, “Accessing the log messages monitor” shows how to access the log messages monitor.

Figure 1.5. Accessing the log messages monitor

TIBCO StreamBase^® Runtime Administrator provides the following monitors:

The CPU and shared memory monitors are available on any running node. Figure 1.6, “CPU monitor” shows the CPU monitor and Figure 1.7, “Shared memory monitor” shows the shared memory monitor.

Figure 1.6. CPU monitor

Figure 1.7. Shared memory monitor

The transaction monitor is available per node and across the cluster. Starting the transaction monitor on the cluster displays an aggregate transaction rate for all nodes in the cluster. Two different displays are available from the transaction monitor:

Figure 1.8. Transaction count

Figure 1.9. Transaction latency

TIBCO StreamBase^® Runtime Administrator provides a way to perform most management tasks. However, sometimes solution specific administrative commands may be introduced that are not integrated with TIBCO StreamBase^® Runtime Administrator. The console tab provides a way to issue arbitrary epadmin commands from within TIBCO StreamBase^® Runtime Administrator. Every management function is available from the command line, so the Console tab provides a way to access any features that TIBCO StreamBase^® Runtime Administrator does not already address. Click on the Console tab as shown in Figure 1.10, “Console”.

Figure 1.10. Console

The fields under the Console tab correspond to the elements of the epadmin command line interface. the section called “Command line interface” explains this interface and what these fields mean.