Java – How to find out the URL of EJBs on WebSphere Application Server

There are a lot of metrics you could monitor.

Some general metrics are:

• Heap Usage + Perm Gen Usage
• CPU Usage per Process
• Number of Full GCs for a given time
• Ratio between JVM uptime and GC times

These metrics give you a good hint about how the application works and how memory efficient it is. These metrics only make sense for your customers when each application has its own process. But they are definitely very valuable for you.

More application specific:

• Number of accesses
• Number of available and busy threads
• Number of available and busy DB (or other backend) connections

I graph part of these numbers with pnp4nagios in our monitoring system. It is not designed for reporting, but you could also use the graphs for reporting

This is not possible without a third-party servlet filter -- the only settings in WAS in this neighborhood that show up misleadingly in searches are related to very specific jax-ws webservices responses.