29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4.6 Planning for monitoring<br />

As most <strong>WebSphere</strong>-based applications are internet-based applications, a 24×7<br />

availability is a must. The tolerance of internet users for unavailable sites is low<br />

and users usually navigate to the next site if your site is not operable. This means<br />

you just lost a potential customer. It is required then, to track and monitor the<br />

availability of your site so that you recognize when things are going wrong and<br />

you can react in a timely manner.<br />

An efficient monitoring, combined with a sophisticated alerting and problem<br />

handling procedure, can increase the availability of your service significantly.<br />

That is why you must plan for monitoring and problem handling. Do not wait until<br />

your environment becomes unproductive.<br />

4.6.1 Environment analysis for monitoring<br />

Careful planning for monitoring is essential and must start with a detailed<br />

analysis of the environment to be monitored. It is important to ensure that the full<br />

environment is monitored and no single component is overseen.<br />

To analyze the monitoring requirements for your environment consider the<br />

following factors to give you an overview of what needs to be done:<br />

Components to be monitored<br />

It is essential that each component required to run your service is monitored. For<br />

each component you identify, answer the following questions:<br />

► What are the possible states of the component and how can you retrieve them?<br />

► What is the impact of each of the possible states the component can have?<br />

► What specific attributes of the component can be monitored?<br />

► For each attribute you can monitor, define the following values:<br />

– Which attribute values (or range of attribute values) show a normal status<br />

of the component?<br />

– Which attribute values (or range of attribute values) show a situation which<br />

requires attention of the administrator (warning level)?<br />

– Which attribute values (or range of attribute values) show a critical<br />

condition for the component and require immediate administrator action<br />

(alert)?<br />

Prioritize each of the components monitoring results and define actions to be<br />

taken.<br />

114 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!