|
Problem(Abstract) |
How to configure a shared library for an installed IBM®
WebSphere® Application Server V5 Enterprise application. |
|
|
|
Cause |
When you want to share a JAR file among multiple
applications, your can:
- Package it within each EAR file. Changes to this dependency JAR file
require redeploying all applications.
- Use the application extensions classloader, inherited from V4.0. The
role of this classloader is to load any JAR file placed in the
install_root/lib/app directory.
- Use shared libraries. This is a cleaner and more manageable way to
share libraries than the previous two options.
|
|
|
Resolving the
problem |
- Define a shared library
- Expand Environment and choose Shared Libraries.
- Select the appropriate scope level.
- Click New, then fill in the correct information, specifying a
unique name.
- Click OK and save the configuration.
- Map the Shared Library to an Enterprise application.
- Expand Applications and select Enterprise Applications.
- Pick the Enterprise application you want to modify, then select
Libraries in Additional Properties.
- Click Add, find the name for the correct library, then click
OK.
Make sure you save and synchronize the settings before testing. Depending
on the Enterprise application and Application Server visibility settings,
the shared libraries will load before the WebSphere Application Server
classloader and IBM® Java™ SDK classloader.
For more comprehensive information about using shared libraries, refer to:
WebSphere Application Server V5: Using Shared Library
Support |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|