Metering Applications in WebSphere Application Server
owenc 1000003T00 Visits (3653)
I was asked on how one could know the current number of users logged into a WebSphere and IBM BPM environment.
There is a desire to be able to meter the applications deployed to get metrics on how much of the WebSphere is being used by each application.
Prior to WebSphere Application Server V6.x, it was easy to know the concurrent number of users connected to WebSphere because a one-to-one mapping existed between the number of concurrent client connections and the threads in the Web container (Used when requests come in over HTTP) thread pool. In other words, if 40 clients were accessing an application, 40 threads were needed to service the requests.
Since WebSphere Application Server V6.0, Native IO (NIO) and Asynchronous IO (AIO) were introduced, providing the ability to scale to thousands of client connections using a relatively small number of threads.
It is still important to know how the web container thread pool is operating. The WebSphere PMI data most useful for the Web container thread pool analysis is:
Counting URL Accesses
AWStats is a free powerful and featureful tool that generates advanced web, streaming, ftp or mail server statistics, graphically. This log analyzer works as a CGI or from command line and shows you all possible information your log contains, in few graphical web pages. It uses a partial information file to
AWStats Top Ten URL Pages Report
The issue here is that every user logging into the shared IBM BPM system, logs into the BPM process Portal which is the same URL for everyone. So there is no way to differentiate between users logging to "application1" and those logging into "application2".
To do that, a unique pseudo URL could be defined in the DNS for each application, for example,
Then, we could use the mod_rewrite feature (in the IHA web server):
I tested the Apache HTTP Server mod_rewrite module to use to convert application specific URLs to the BPM process Portal URL. Basically, we have to add some URL re-writing rules in the IHS httpd.conf configuration file:
LoadModule rewrite_module modu
Now, if I enter this URL in the browser:
I will be redirected to:
The rewrite rules can use full regular expressions which means that I can rewrite a portion of a URL (and not do just a full substitution as shown above).
In conclusion, you can count the number of accesses to unique URLs with AWStats.