J2EE Library: Overview

Use this page to view, and sometimes change, general configuration information about the J2EE library, such as its name, path to the source of the application, and staging mode. Use the Deployment Order field to change the order that the library is deployed at server startup, relative to other deployments.

The J2EE library feature in WebLogic Server 9.0 provides an easy way to share one or more types of J2EE modules among multiple Enterprise Applications.

In particular, 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 registered, you can deploy Enterprise Applications that reference the library. Each referencing application receives a reference to the required library module(s) on deployment, and can use those modules as if they were packaged as part of the referencing application itself. The shared library classes are added to the classpath of the referencing application, and the referencing application's deployment descriptors are merged (in memory) with those of the J2EE library modules.

The name of the J2EE library is always followed by a version number of the form (Specification@Implementation), where Specification identifies the version number of the specificaiton (for example, the J2EE specification number) to which a library or package conforms and Implementation identifies the version number of the actual actual code implementation for the library or package. This versioning of J2EE libraries enables referencing applications to specify a required minimum version of the library to use, or an exact, required version.

Configuration Options

Name	Description
Name	The name of this J2EE library.
Application Name	The name of this J2EE library.
Module Name	The name of this module.
Path	MBean Attribute: `AppDeploymentMBean.Path` Changes take effect after you redeploy the module or restart the server.
Path	The path to the source of the deployable unit on the Administration Server. Rules: If InstallDir is null, the source path must be an absolute path. If the source path is relative, it is resolved relative to InstallDir/app. Use AbsoluteSourcePath to get a fully resolved value. MBean Attribute: `AppDeploymentMBean.SourcePath` Changes take effect after you redeploy the module or restart the server.
Install Directory	The path to application's install-root directory, relative to the domain/config/deployments directory. When the Install Directory is specified, SourcePath, PlanDir, and PlanPath are derived from this path, and need not be specified. Default value for this is the name of the deployment. MBean Attribute: `AppDeploymentMBean.InstallDir` Changes take effect after you redeploy the module or restart the server.
Staging Mode	The mode that specifies whether an application's files are copied from a source on the Administration Server to the Managed Server's staging area during application preparation.
Deployment Order	A numerical value that indicates when this unit is deployed, relative to other DeployableUnits on a server, during startup. Units with lower Load Order values are deployed before those with higher values. MBean Attribute: `AppDeploymentMBean.DeploymentOrder` Changes take effect after you redeploy the module or restart the server.