Table 4-1 ApplicationMBean Element Attributes
Attribute
|
Description
|
Range of Values and Default
|
Console Label
|
Deployment-Timeout
|
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 ~10 minutes. Note that the server only checks for timed out deployments about once a minute.
Only cluster deployments can be timed out.
|
Default: 600000
|
Deployment Timeout
|
Deployment-Type
|
Specifies category of this application. This attribute will be derived if not specified in the configuration.
|
Default: TYPE_UNKNOWN
Valid values:
|
Deployment Type
|
Last-Modified
|
The time when this application was last loaded.
|
Default: 0
|
Last Modified
|
Load-Order
|
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.
|
Default: 100
|
Load Order
|
Name
|
The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.
|
|
Name
|
Notes
|
Optional information that you can include to describe this configuration.
|
|
Notes
|
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.
|
|
Path
|
Staging-Mode
|
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.
|
Default: null
Valid values:
|
Staging Mode
|
Staging-Path
|
Identifies the directory path on the managed server relative to the server's StagingDirectoryName. This is the path used to prepare and activate an application on a managed server. This attribute is derived from the Path attribute, and depends on whether the application is being staged. If the Path attribute for application, myapp, is foo.ear, the staging path is set to myapp/foo.ear. If the path is C:\myapp.ear, the staging path is myapp/myapp.ear. If the application is not being staged (StagingMode==nostage), then the staging path is the same as the Path attribute. If this application is not being staged, the staging path is equivalent to source path (Path attribute)
|
|
Staging Path
|