Maintaining the monitoring environment

As the administrator, you continually scrutinize the general monitoring environment, searching for ways to improve its efficiency and avoid future problems. IBM® Business Monitor provides several tools and approaches to help you with this effort.

Handling exceptions
Three types of exceptions can occur in IBM Business Monitor: soft exceptions, hard exceptions, and in-doubt exceptions.
Maintaining the IBM Business Monitor server
This section provides topics with suggestions for maintaining your IBM Business Monitor server.
Using logging and tracing
You can manage the logging and tracing feature in IBM Business Monitor using the WebSphere Application Server administrative console. Tasks include enabling the logging and tracing for the application server on which the IBM Business Monitor components are deployed and setting the logging and tracing levels for each of the IBM Business Monitor components.
Avoiding locked event or in-doubt status when shutting down and restarting servers
To avoid a locked event or transaction in doubt status when shutting down IBM Business Monitor servers, you must shut down and restart the servers and clusters in the correct order. The shutdown and restart steps are required in a multi-clustered IBM Business Monitor environment.
Adding or removing date dimension values
The MONITOR database includes a date dimension table containing dates in the range January 1, 2008 through December 31, 2022. You can manually add or remove dates in this table using database scripts provided by IBM Business Monitor.
Managing clusters
You can start or stop servers in a single action if they are members of the same cluster. To first stop and then restart each member of a cluster automatically, you can use the ripplestart option, unless you are starting the cluster just after the IBM Cognos® Business Intelligence service was installed.

Parent topic: Administering your monitoring environment