Deployments: JDBC Module: Overview
Configuration Options Related Tasks Related Topics
Use this page to view the configuration of a JDBC module deployed within an enterprise application or as a standalone module.
Note that some fields listed in this page are only available for modules deployed as a standalone module.
Name Description Name
The name of this JDBC module. The name corresponds to the module file name and must be unique within the enterprise application or within all standalone deployed modules.
The path to the source of the module on the Administration Server.
- For standalone modules, the path can be an absolute path or a path relative to the domain directory.
- For modules packaged within an enterprise application, if the installation directory of the application is not set, the path must be an absolute path.
- For packaged modules where the installation directory for the application is set, the path can be relative to the installdir/app directory.
The path to the deployment plan document on the Administration Server.
For modules packaged in an enterprise application, changes to the module are stored in the deployment plan for the enterprise application. Standalone modules have their own deployment plan.
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.
Plan Staging Mode
Specifies whether a deployment plan'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 the principal that 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.