weblogic.management.configuration
Interface ApplicationMBean

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.

Deprecation of MBeanHome and
Type-Safe Interfaces

This is a type-safe interface for a
WebLogic Server MBean, which you can import into your client
classes and access through
weblogic.management.MBeanHome. As of 9.0, the
MBeanHome interface and all type-safe interfaces for
WebLogic Server MBeans are deprecated. Instead, client classes that
interact with WebLogic Server MBeans should use standard JMX design
patterns in which clients use the
javax.management.MBeanServerConnection interface to
discover MBeans, attributes, and attribute types at runtime. For
more information, see "Developing Manageable Applications with JMX"
on http://edocs.bea.com.

getStagingMode()Deprecated. The mode that 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.

DEFAULT_STAGE

Indicates that applications deployed to the Admin Server
will not be staged, and that the Admin Server does not copy
deployment files to Managed Servers. With this staging mode, Managed Servers
are treated as staged, and external application (not the Admin Server) is
resonsible for delivering deployment files to the staging directory.

DEPLOYMENT_TIMEOUT

static final int DEPLOYMENT_TIMEOUT

Deprecated.

Default deployment timeout value for two-phase deployments. Time is in milliseconds.

The default timeout should far exceed our worst case expected deployment
of a large application to a large number of destinations.

getPath

The URI, located on the Administration Server, of the original
source files for this application.

Relative paths are based on the root of the Administration
Server installation directory. It is highly recommended that you
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. 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.

getFullPath

getStagingPath

The directory that a Managed Server uses to prepare and activate
an application.

The directory path is relative to the Managed Server's
Staging Path. It 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 the source path (Path attribute).

Returns:

The stagingPath value

Since:

7.0.0.0

getStagedTargets

List of servers on which this application is known to be staged.
This makes no distinction regarding the version or state of the
staged files, just that they are staged. The array returned
contains the names of the target servers. This list should not
include cluster names.

Returns:

The stagedTargets value

Since:

7.0.0.0

getStagingMode

The mode that 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. 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.

Staging involves distributing the application files from the
Administration Server to the targeted Managed Servers staging
directory. This attribute is used to override the Managed Server's
StagingMode attribute.

setTwoPhase

void setTwoPhase(boolean mode)

Deprecated.Has no effect

Parameters:

mode - The new twoPhase value

Since:

7.0.0.0

getLoadOrder

int getLoadOrder()

Deprecated.

A numerical value that indicates when this module or application
is deployed, relative to other deployable modules and applications.
Modules with lower Load Order values are deployed before those with
higher values. (Requires that you enable the two-phase deployment
protocol.)