Download - PMIExplorer

unless you have operating system specific services in place which launch the program after a system
reboot. It is also possible to use high availability software, like Tivoli System Automation, to automatically
relaunch the PMIExplorer program when it has stopped.
Reconnecting to WebSphere
To compensate for temporarily unavailability of the endpoints, which might occur due to
maintenance on the WebSphere environment, PMIExplorer can automatically reconnect to
a WebSphere endpoint. PMIExplorer checks the status every 5 minutes by default, when it
reloads the endpoints to detect new servers and metrics. If an endpoint has become
unavailable then PMIExplorer can attempt to reconnect to the endpoint if the configuration
property pmi.collector.reconnect is set to true and the pmi.collector.reload interval is set
to value greater than zero.
After a successful reconnect the monitoring profiles are also automatically applied again
and monitoring is resumed normally. Depending on your alarm configuration an alert might
be fired in the mean while if you have configured an alarm with an unavailability trigger for
a statistic related to that endpoint.
When an endpoint becomes unavailable PMIExplorer distinguishes between unavailability
due to authorization problems and unavailability due to other reasons. PMIExplorer does
not attempt to reconnect when an authorization error has occurred because subsequent
attempts to reconnect might lock this account.
NOTE:
To detect endpoint failures PMIExplorer recommends to define an alert on the jvmModule for each server
on the endpoint. This alert will notify you when a JVM statistic for a server on the endpoint cannot be
recorded anymore.
Page 79 / 79