Custom queries reduce network traffic, processing at the agent and Tivoli Enterprise™ Monitoring Server, and memory usage at the Tivoli Enterprise Portal Server and Tivoli Enterprise Portal client. Custom queries accomplish this by limiting the number of rows and columns passed from the Tivoli Enterprise Monitoring Agent to the Tivoli Enterprise Monitoring Server.
Most of the predefined, predefined queries request all columns and all rows of an attribute group, of which only a few may be of interest to you. Removing the unwanted columns (attributes) will reduce the amount of data transferred from monitoring agent to Tivoli Enterprise Monitoring client via the portal server, hub monitoring server and remote monitoring server. Additionally, in the case of OMEGAMON® monitoring agents that are located on z/OS®, you will also reduce the amount of EBCDIC/ASCII conversion required when data is passed between mainframe and distributed platforms.
It is recommended to tune any queries servicing workspaces that are frequently executed or return large quantities of data. Query execution always requires resources and intermittent extremely large reports will cause a spike in memory requirements and network resources.
You may be using view filters inappropriately. View filters work only on the current page returned from the query. For example, if page size is 100 lines and the filter reduces it to five lines on page 1 and similarly on subsequent pages, the row set cannot be seen on one page. Do not increase the workspace page size to see everything on one page. Increased page size actually increases portal client memory requirements.
Instead, avoid this condition by creating a custom query that filters the data at query execution time.
It may be that you want this query to be applied to only certain managed systems and so distribution to all managed systems is an unneccessary waste of resource. Modify MSLs to reduce the distribution of the query. Also remove the MSLs for queries that are of no interest to the user. Even if you are not viewing the results of the query, there may be a use of system resources that can be avoided by restricting the distribution of the unneeded queries.
[ Top of Page | Previous Page | Next Page | Contents | Index ]