ClassLoader Viewer
WebSphere Technology Preview
NOTE: This
is a preview for the WebSphere Application Server. This
technology may be incorporated into a future release of WebSphere.
You should be aware that the technology may, if incorporated, appear in
a different form
Contents
Overview
The WebSphere ClassLoaderViewer provides the ability
to view and search the classloader information in real-time.
Downloading
& Installation
- Download the classloaderviewer.zip file
- Unzip it in the directory of your
choice. Note: It will create a top level ClassLoaderViewer directory
- Example: unzip classloaderviewer.zip -d /home/gissel
- Cd into the <CLASSLOADERVIWER_DIR>/bindirctory
- Example: cd /opt/WebSphere/ClassLoaderViewer/bin
- Update the install_ClassLoaderViewer.{bat|sh} file as
follows:
- set the WAS_HOME variable to
refer to your WebSphere R5.0 installation
- Run install_ClassLoaderViewer.{bat|sh}
- Example: ./install_ClassLoaderViewer.sh
Getting
Started
- Start WebSphere
- run <WAS_HOME>/bin/start{Manager|Node|Server}.{bat|sh}
- Example: /opt/WebSphere/AppServer/bin/startServer.sh
server1
- Open the WebSphere Administrative Conosole
- Example: mozilla http://localhost:9090/admin
- Login to the Adminstrative Console
- Navigate to the ClassLoader Viewer
- expand the "Troubleshooting" Tree
- Click on the "ClassLoader Viewer" link
- Navigate the "WebSphere Topology" tree and select the module from
which to view the ClassLoader Information
Example
Tasks
- View ClassLoader Delegation
Hierarchy
- Click on the ClassLoader
Delegation Hierarchy link
- View the ClassLoader Attributes
- Click on the ClassLoader Attributes
link
- Display all known ClassLoader
information for selected module
- Click on ClassLoader
Display link
- Search for Classes,
JAR/Directories, package names, and ClassLoaders *
- Click ClassLoader
Search link
- Select the the search type desired, class, JAR/Directory, or
ClassLoader
- Enter query
* The search is case-sensitive and greedy. For
instance, if a search is made for classes containing "com" any class
whose name or package contains the string "com" will be returned
therefore this query would most likley return many results. Conversley,
if the same search was performed using with mixed-case instead of
all lower-case letters, such as "CoM, " there will probably not be
any results returned because most class and package names are not
formated in this way.