| |
Java EE Library: Overview
Configuration Options Related Tasks Related Topics
Use this page to view, and sometimes change, general configuration information about the Java EE 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 Java EE library feature provides an easy way to share one or more types of Java EE modules among multiple Enterprise Applications.
In particular, a Java EE library is a stand-alone 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 Java EE 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 Java EE library modules.
The name of the Java EE library is always followed by a version number of the form
( Specification@ Implementation), whereSpecificationidentifies the version number of the specificaiton (for example, the Java EE specification number) to which a library or package conforms andImplementationidentifies the version number of the actual actual code implementation for the library or package. This versioning of Java EE 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 Java EE library.
Implementation Version The implementation version, from the manifest or overridden during deployment.
Specification Version The specification version, from the manifest or overridden during deployment.
Application Name The name of this Java EE library.
Module Name The name of this module.
Path MBean Attribute:
AppDeploymentMBean.PathChanges 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.SourcePathChanges 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.InstallDirChanges 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 An integer value that indicates when this unit is deployed, relative to other deployable units on a server, during startup.
Units with lower values are deployed before those with higher values.
MBean Attribute:
AppDeploymentMBean.DeploymentOrderChanges take effect after you redeploy the module or restart the server.
Deployment Principal Name A string value that indicates what principal should be used when deploying the file or archive during startup and shutdown. This principal will be used to set the current subject when calling out into application code for interfaces such as ApplicationLifecycleListener. If no principal name is specifed, then the anonymous principal will be used.
MBean Attribute:
BasicDeploymentMBean.DeploymentPrincipalNameChanges take effect after you redeploy the module or restart the server.
|
