WebLogic Server Configuration Reference
An application represents a J2EE application contained in an EAR file or EAR directory. The EAR file contains a set of components such as WAR, EJB, and RAR connector components, each of which can be deployed on one or more Targets. A target is a server or a cluster. If the application is provided as a standalone module, then this MBean is a synthetic wrapper application only.
DeploymentType=( "EAR" | "EXPLODED EAR" | "COMPONENT" | "EXPLODED COMPONENT" )
StagingMode=( "nostage" | "stage" | "external_stage" )
TwoPhase=( "true" | "false" )
Milliseconds granted for a cluster deployment task on this application. If any deployment tasks remain active for longer, the task will be cancelled. The default is ~60 minutes. Note that the server only checks for timed out deployments about once a minute.
The location of the original source application files on the Admin Server. Relative paths are based on the root of the Admin Server installation directory. It is highly recommended that you use absolute paths to minimize possible issues when upgrading the server.
The path to an Enterprise application (EAR) is the location of the EAR file or the root of the EAR if it is unarchived. e.g. Path="myapps/app.ear" is valid. If the application is a standalone module, then the path is the parent directory of the module. For example, if the module is located at myapps/webapp/webapp.war, the Path="myapps/webapp" is correct, whereas Path="myapps/webapp/webapp.war" is incorrect.
Indicates whether this application is being staged. Staging involves distributing the application files from the admin server to the targeted managed servers staging directory. This attribute is used to override the managed server's StagingMode attribute.
Indicates whether this application is deployed using the 2 phase deployment protocol weblogic.management.runtime.DeployerRuntimeMBean. If true, then the application's components may only be targeted to release 7.0 and later servers. If false, then the application may be deployed to all releases supporting the release 6 deployment protocol, which is deprecated in release 7. If unspecified in the configuration, false is assumed.