Application

 

---

Description

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.

 

---

Syntax

<Application
  DeploymentTimeout="number"
  DeploymentType=( "EAR" | "EXPLODED EAR" | "COMPONENT" | "EXPLODED COMPONENT" )
  LoadOrder="number"
  Name="String"
  Notes="String"
  Path="String"
  StagingMode=( "nostage" | "stage" | "external_stage" )
/>

 

---

Parent Elements

• Domain

 

---

Child Elements

• ConnectorComponent

• EJBComponent

• WebServiceComponent

• WebAppComponent

• JDBCPoolComponent

 

---

Attributes

Table 2-1 Application attributes

Attribute	Description	Range of Values and Default
DeploymentTimeout	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. Only cluster deployments can be timed out.	Required: no Default: 3600000
DeploymentType	Specifies category of this application. This attribute will be derived if not specified in the configuration.	Required: no Default: UNKNOWN
LoadOrder	Specifies the order applications are loaded at server startup. Applications with the lowest values are loaded first. Application ordering is only supported for applications deployed with the 2 phase protocol.	Admin Console field label: Load Order Required: no Default: 100
Name	The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.	Admin Console field label: Name Required: no
Notes	Optional information that you can include to describe this configuration.	Admin Console field label: Notes Required: no
Path	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 to use absolute paths to minimize possible issues when upgrading the server. If the application is not being staged (StagingMode==nostage) then the path must be valid on the target 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. e.g. If the module is located at myapps/webapp/webapp.war, the Path="myapps/webapp" is correct, whereas Path="myapps/webapp/webapp.war" is incorrect.	Admin Console field label: Path
StagingMode	Returns the staging mode of this application, which overrides the managed server's StagingMode attribute. Staging involves distributing the application files from the admin server to the targeted managed servers' staging directory. Staging values are: 1. nostage: does not copy application files to another location 2. stage: copies application files to server targeted in deployment 3. external_stage: the user, and not WebLogic Server, copies application files to the server's staging directory	Admin Console field label: Staging Mode Required: no