JMS Module: Overview
Configuration Options Related Tasks Related Topics
Use this page to configure a new application or view the configuration of an application that has already been deployed.
Name Description Name
The name of this application deployment.
The path to the source of the deployable unit on the Administration Server.
If the source path is relative, it is resolved relative to InstallDir/app if InstallDir is not null; Otherwise, it is resolved relative to domain root.
Use AbsoluteSourcePath to get a fully resolved value.
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.
The path to the deployment plan document on Administration Server.
If the plan path is a relative path, it is resolved relative to PlanDir if PlanDir is not null; otherwise, it is resolved relative to domain root.
Use AbsolutePlanPath to get a fully resolved value.
If there is no plan, this returns no plan specified.
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.
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.
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 specified, then the anonymous principal will be used.
- Modify JMS application modules
- Update (redeploy) stand-alone JMS modules
- Install stand-alone JMS modules