Detecting and handling problems with runtime components

We must monitor the status of runtime components to ensure that, once started, they remain operational as needed.

Tasks

1. Regularly examine the status of runtime components.

   Browse messages displayed in the status area for WebSphere Runtime Messages. The runtime event messages, marked with a red X, provide detailed information on event processing.

2. If an application stops running, examine the status of the application If an application stops running when it should be operational, examine the status of the application on an Applications page and try restarting the application. If messages indicate that a server has stopped running, use the Application servers page to try restarting the server. If a cluster of servers stops running, use the Server Cluster page to try to restart the cluster. If the status of an application server is Unavailable, the node agent is not running in that node and we must restart the node agent before we can start the server.

3. If the runtime components do not restart, reexamine the messages and read information on problem determination to help you to restart the components.

Manage application servers