Manage shared libraries
Shared libraries are files used by multiple applications. Using the administrative console, one can define a shared library at the cell, node, or server level. You can then associate the library to an application or server to load the classes represented by the shared library in either a server-wide or application-specific class loader. Using an installed optional package, one can associate a shared library to an application by declaring the dependent library .jar file in the MANIFEST.MF file of the application. Refer to the J2EE 1.4 specification, section 8.2 for an example.
OverviewIf your deployed applications use shared library files, define shared libraries for the library files and associate the libraries with specific applications or with an application server. Associating a shared library file with a server associates the file with all applications on the server. Use the Shared Libraries page to define new shared library files to the system and remove them.
Steps for this task (dependent on configuration)
- Use the administrative console to define a shared library.
- Create a shared library for each library file that your applications need.
- Associate each shared library with an application or a server.
- Associate a shared library with an application that uses the shared library file.
- Associate a shared library with an application server so every application on the server can use the shared library file.
- Use an installed optional package to declare a shared library for an application.
- Remove a shared library.
- Click Environment > Shared Libraries in the console navigation tree to access the Shared Libraries page.
- Select the library to be removed.
- Click Delete.
The list of shared libraries is refreshed. The library file no longer displays in the list.
Creating shared libraries
Shared library collection
Associating shared libraries with applications
Associating shared libraries with servers
Installed optional packages
Using installed optional packages