Webshpere monitoring on remote server

Dear Reader,

This post I have taken from IBM forum to relate it to the monitoring with Loadrunner.

TO monitor Web application Servers,First we need to configure the servers to allow monitoring by Loadrunner.

Let us see an example from the IBM forum to set up the servers to monitor websphere application server from remote server :

In this topic, a Web application, cviewer, is taken as an example. Before you start monitoring its status, you need to ensure the following:

1. Ensure WASCE is successfully installed on two different machines, for example, serverA and serverB.
2. Start the servers on the two machines. Under a privileged user or root, enter the following command to start up the server: WASCE_HOME/bin/startup(.sh|.bat). Ensure the server is started successfully.

To monitor the status of cviewer on a remote server, take the following steps:

1. Install the cviewer application on serverA. Ensure the cviewer application is started correctly by checking the URL http://\[server ip:port]/cviewer/.
2. Define a monitor for serverA on the serverB:
1. Log in to serverB administrative console with the default account/password "system/manager".
2. Add a server first. Click Server -> Monitoring, and then click Add server, fill in the following fields and click Add.
* Name=serverB
* IP/Hostname=[IP or hostname of serverB]
* Protocol=[default=EJB]
* Port=[default=4201]
* Username=system
* Password=manager
* Password(verify)=manager
3. Start server status query. Click "Enable Query" and ensure Stat.Query column is running.
4. Add the web module "cviewer" to "Statistics Collected". Under WebModule, click + on the line of cviewer. The cviewer will be listed under Live Statistics. The following data is collected:
* Active Session Count - shows the number of active sessions in use currently
* Expired Session Count - shows the number of expired sessions
* Rejected Session Count - shows the number of sessions that were not created because the maximum number of active sessions was reached.
* Processing Time - shows the cumulative processing times of requests by all servlets
* Session Alive Time Count - the count of sessions which are alive in the same time duration
* Session Alive Time MaxTime - the maximum time an expired session ever lived
* Session Alive Time MinTime - always equals -1
* Session Alive Time TotalTime - the total live time of sessions which are alive in the same time duration
* Session Count - the total number of sessions created by this manager
* Startup Time - the time in milliseconds it took to start this context
* TLD Scan Time - the time used to scan the TLD contents of all tag library descriptor files (including those inside the jars that are "accesible" to this Web application) and register any application event listeners found there.
3. To delete the server monitoring, go back to the Monitoring portlet, click Edit in the Actions column, and then click Delete this server.
4. To view serverA's live statistics, click serverA to view the live statistics.
5. To stop the server on serverA, enter the command WASCE_HOME/bin/shutdown.sh
6. Check serverA's status in serverB's console.

In the next Post, Let us relate these concept to configure the server to monitor it from LoadRunner.

Dear Readers,
Hope you enjoy this post and let us know if you have any comments or suggestions on this.