SERVER OVERVIEW Page

In Manager, you access TDV server overview information by choosing Server Overview from the MONITORING menu. The SERVER OVERVIEW page is displayed, providing a consolidated overview of the system, and the overall status of all of the other system components.

The SERVER OVERVIEW page displays statistics about the server that are grouped into four areas: server status information, sessions and requests information, cache information, and server status indicators. In addition, two server overview buttons are provided at the bottom of the page.

The upper left section of the SERVER OVERVIEW page displays server status information. Each item listed is described in this section. Where appropriate, the related configuration parameter in Studio is also described.

Status reports the presence and count of errors and warnings from all pages under the MONITORING tab.

In Studio Manager, more status information is available: Server is running, Server is stopping, Server stopped, Server is starting, Server failed, or Unknown server status (which is shown if the Monitor is not running.) See Server Overview Panel for more information.

Percentage of total available Java Heap Memory (RAM) currently in use. Java Heap Memory is a TDV configuration setting that requires restart to change. Total memory is further divided into Managed and Reserved memory with a built in margin to prevent Out of Memory (OOM) errors.

Maximum number of events that can be viewed from the Events console in the Manager.

In Studio, you can set this number using the Configuration dialog setting for Maximum Viewable Entries under Memory:

This number also controls the maximum number of rows of information displayed in the table in each console. Additional entries can be viewed in the log files.

Maximum number of events to be stored in the TDV repository. When the number of events reaches this threshold the oldest events are discarded in FIFO (first in, first out) order. The log files are generally configured to retain a more expansive archive of event entries.

In Studio, you can change the Maximum Event Entries using the Configuration window setting for Maximum Log Entries in Database Logger:

The SERVER OVERVIEW page also displays summary information about sessions and requests.

The number of currently connected user sessions, and the total number of sessions started since the server started to run, including closed sessions.

Active requests, started but not completed, and the total number of incoming requests made to the server. Includes the requests that have been completed.

Active data source requests sent to other resources versus the total number of outgoing requests that the server has made on other resources. The total is the resource cache storing resource metadata number of resources loaded on the server.includes all requests completed or otherwise.

Summary cache information on the SERVER OVERVIEW page displays usage of TDV system caches for security privileges on defined data resources, user privileges, and data source metadata repository stores. These system caches are not to be confused with the data source caches which store materialized views specifically configured at the data source level.

For more information on caching, see the TDV User Guide.

The system caches store data such as user session values of privileges, recently introspected data source metadata, and execution plans.

Access (Hits/ Accesses), the first column in the sub-section, displays a percentage that for all three rows should be relatively high, as it is a fair indicator of enhanced performance obtained by system cache usage.

Access is any request to access an object in the repository, and Hits are inquiries sent to the cache or successful cache usages.

A "miss" is an access attempt that was required to look beyond the cache for a particular entity, meaning a disk access, LDAP or data source query.

A high percentage of hits to total access attempts is one indicator of enhanced performance. It would indicate that most of the entity access attempts are hitting the cache without requirement of disk or source data retrieval.

The second column in the sub-section is the Capacity (Entries/Max) which shows the amount of repository usage by each of the system caches. Each of the system cache sizes is configurable.

Privilege cache refers to repository storage of explicit privileges for resources. In Studio, you can change privilege cache capacity setting in the Configuration window at Privilege Cache Size (On Server Restart).

Current user cache data stored in the repository. In Studio, you can change the user cache capacity setting in the Configuration window at User Cache Size (On Server Restart).

Repository cache is a resource metadata store enabling quick use of configured resources. In Studio, you can change the repository cache capacity setting in the Configuration window at Metadata Cache Size (On Server Restart).

The SERVER STATUS summary box at right of the SERVER OVERVIEW page displays a summary status for other Manager pages, which are all available for display from the MONITORING and LOGGING tabs. The red, green, and yellow indicate the status of key system components. You can click on any of the links to go to the related page for detailed information.

You can start and stop a server or clear the repository cache for the server by clicking these buttons:

Stops TDV after acknowledgment of a verification prompt. Actually stopping TDV requires the Modify All Status right. The button is visible, but grayed out and inactive for other users who can have access to the Manager.

Immediately empties the repository cache. Clearing the repository cache requires the Modify All Status right. The button is visible, but grayed out for any other users who can have access to the Manager.