Shared library reference and mapping settings

Use the Shared library references and Shared library mapping pages to associate defined shared libraries with an application or web module. A shared library is an external JAR file used by one or more applications. Using shared libraries enables multiple applications deployed on a server to use a single library, rather than use multiple copies of the same library. After you associate shared libraries with an application or module, the application or module class loader loads classes represented by the shared libraries and makes those classes available to the application or module.

To view the Shared library references console page, click Applications > Application Types > WebSphere enterprise applications > application_name > Shared library references. To view the Shared library mapping page, click Reference shared libraries on the Shared library references page. These pages are the same as the Map shared libraries and Map shared libraries to an entire application or module pages in the application installation and update wizards.

On the Shared library references page, the first element listed is the application. The other elements are modules in the application.

To associate shared libraries with the application or module:

  1. Select an application or module.

  2. Click Reference shared libraries.

  3. On the Shared library mapping page, select one or more shared libraries that the application or modules uses in the Available list, click >> to add them to the Selected list, and click OK.

A defined shared library for a file that the application or module uses must exist to associate the application or module to the library.

If no shared libraries are defined and the application is installed already, on the Shared library mapping page, click New and define a shared library.

We can otherwise define a shared library as follows:

  1. Click Environment > Shared libraries.

  2. Specify whether the shared library is visible at the cell, node or server level.

  3. Click New.

  4. On the settings page for the new shared library, specify a name and one or more class paths. If the libraries are platform-specific files such as .dll, .so, or *SRVPGM objects, also specify a native library path. Then, click Apply.

  5. Save the administrative configuration.

If any value is modified on this page, all of the metadata files related to the application are refreshed in the configuration repository.


Name of the application that you are installing or selecteded on the Enterprise applications page.


Name of the module associated with the shared libraries.


Location of the module relative to the root of the application EAR file.

Shared libraries

Name of the shared library files associated with the application or module.

Related tasks

  • Install enterprise application files with the console
  • Manage shared libraries
  • Associate shared libraries with applications or modules
  • Configure enterprise application files

    Enterprise application settings

  • Shared library relationship and mapping settings
  • Shared library settings
  • Library reference collection
  • Library reference settings