|
Home > Archive > WebSphere Portal Server > May 2005 > Portal performance monitoring
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Portal performance monitoring
|
|
|
| Consider me a novice to Portal land; hence pardon me for any irrelevant or
obvious queries.
My requirement is to monitor the health/performance of WAS Portal and its
components such as Desktops, Entitlements, Content Management, Portlets,
Java Page Flows. This has to be accomplished using Java.
The metrics that I want to capture for each of these components are Response
Time and # of times invoked.
I would also be interested in capturing:
1- portlet performance by transaction and
2- portlet performance by user
3- what server metrics should I be monitoring (ie. cache settings etc..)
Do these metrics make sense (would they be useful)? Are they even possible
to collect?
Inputs on how I can write an application that can retrieve all this
information and also insights to any other metrics, components I should be
considering in order to be able to monitor a Portal Server holistically.
Please provide your inputs.
Raj.
| |
| L D Jones 2005-05-05, 6:04 pm |
| 007 wrote:
> Consider me a novice to Portal land; hence pardon me for any irrelevant or
> obvious queries.
>
> My requirement is to monitor the health/performance of WAS Portal and its
> components such as Desktops, Entitlements, Content Management, Portlets,
> Java Page Flows. This has to be accomplished using Java.
>
> The metrics that I want to capture for each of these components are Response
> Time and # of times invoked.
>
> I would also be interested in capturing:
>
> 1- portlet performance by transaction and
> 2- portlet performance by user
> 3- what server metrics should I be monitoring (ie. cache settings etc..)
>
> Do these metrics make sense (would they be useful)? Are they even possible
> to collect?
>
> Inputs on how I can write an application that can retrieve all this
> information and also insights to any other metrics, components I should be
> considering in order to be able to monitor a Portal Server holistically.
The Tivoli Site Analyser may capture most of these data
|
|
|
|
|