Skip navigation.

Administration Console Online Help

PreviousNextvertical dots separating previous/next from contents/index/pdfContents

Install a J2EE library

A J2EE library is a standalone EJB or Web Application module, multiple EJB or Web Application modules packaged in an Enterprise Application (EAR), or a single plain JAR file that is registered with the J2EE application container upon deployment. After the library has been installed and started, other deployed modules can reference the library.

Installing a J2EE library refers to making its physical file or directory known to WebLogic Server. A J2EE library can be installed as an archived EAR file or as an exploded directory. After you have installed the J2EE library, you can start it so that other deployed modules can start using it.

To install a J2EE library, follow these steps:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left pane of the Console, click Deployments. A table in the right pane displays the installed applications, modules and J2EE libraries. J2EE libraries are specified with the Library entry in the Type column.
  3. In the right pane, click Install.
  4. Using the Install Application Assistant, locate the archive file or exploded directory that corresponds to the J2EE library you want to install. If you specify an exploded directory, WebLogic Server installs all components it finds in and below the specified directory.

    Note: You can install only the following types of archive files (or their corresponding exploded directories) as J2EE libraries: EJB JARs, Web Application WARs, EAR files that contain EJB JARs or WARs, or plain JAR files that contain compiled classes.

  5. When you have located the archive file to configure, click Next.
  6. Select the Install this deployment as a library option.
  7. Click Next.
  8. Select the servers and/or clusters to which you want to deploy the J2EE library. Be sure you target all the servers and clusters to which modules or applications that reference the J2EE library are deployed.

    Note: If you have not created additional Managed Servers or clusters, you will not see this assistant page

  9. Click Next.
  10. Optionally update settings about the deployment. These settings include:
    • The deployed name of the J2EE library. If the library contains a MANIFEST.MF file in the META-INF directory, the value of the Extension-Name attribute automatically appears in the text field.
    • The security model that is applied to the J2EE library.
    • How the source files (EAR or exploded directory contents) are made available to all targetted Managed Servers and clusters.

    Typically, the default values are adequate.

  11. Click Next.
  12. Review the configuration settings you have chosen, and click Finish to complete the installation.
  13. If you chose to immediately go to the deployment's configuration screen, click on the tabs to set additional configuration settings for the J2EE library. If you chose to change this information later, the Console returns you to the Deployments table, which now includes the newly-installed J2EE library. In the Deployments table, J2EE libraries are specified with the Library entry in the Type column.
  14. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).


Skip navigation bar   Back to Top