Configuration Options Related Tasks Related Topics
Use this page to view the general configuration of an Enterprise application, such as its name, the physical path to the application files, the associated deployment plan, and so on. The table at the end of the page lists the modules (such as Web applications and EJBs) that are contained in the Enterprise application. Click on the name of the module to view and update its configuration.
Name Description Name
The name of this Enterprise Application.
The archive version, from the manifest or overridden during deployment.
The deployment plan version, specified during 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 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 a deployment's files are copied from a source on the Administration Server to the Managed Server's staging area during application preparation.
Staging mode for an application can only be set the first time the application is deployed. Once staging mode for an application is set, it cannot be changed while the application is configured in the domain. The only way to change staging mode is to undeploy then redeploy the application.
This attribute overrides the server's staging mode.
The security model that is used to secure a deployed module.
To set this value, you can use the
weblogic.Deployercommand-line tool, the Deployment Assistant in the Administration Console, the WebLogic Scripting Tool (WLST), or some other JMX client.
If you deploy a module using one of the previously mentioned tools and you do not specify a security model value, the module is secured with the security realm's default model ( see RealmMBean SecurityDDModel ).
If you deploy a module by modifying the domain's
config.xmlfile and restarting the server, and if you do not specify a security model value for the module in
config.xml, the module is secured with the
DDOnlymodel, which is the default value of this
In summary, the order of precedence for the value of this attribute is as follows:
If you deploy a module using a runtime deployment utility, the order of precedence is:
The value set by the deployment utility.
The value set as the security realm's default security model.
If you deploy a module by modifying
config.xmland restarting the server, the order of precedence is:
The value that you specify for the module in
The default value of this
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.
- Start and stop a deployed Enterprise application
- Configure an Enterprise application
- Create a deployment plan
- Target an Enterprise application to a server
- Test the modules in an Enterprise application