Application --> Configuration --> General

Application --> Configuration --> General

Tasks Related Topics Attributes

Overview

In the Application > Configuration tab, you configure a new Application to be deployed to WebLogic Server or cluster.

Tasks

Configuring and Deploying a New Enterprise Application or Web Service
Viewing Deployed Enterprise Applications
Stopping Deployed Enterprise Applications
Adding or Editing Enterprise Application Deployment Notes
Deleting an Enterprise Application or Application Module
Monitoring Enterprise Applications
Viewing and Updating Run-Time Deployment Descriptors

Related Topics

Enterprise Applications
See Developing WebLogic Server Applications.

Attributes

Attribute Label

Description

Value Constraints
Name The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.MBean: weblogic.management.
configuration.
ApplicationMBeanAttribute: Name

Path The location of the original source application files on the Administration Server. 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.Note: The path displayed in the console may include extra spaces inserted for display purposes. You must remove these spaces if you select and copy this path for use in another context. MBean: weblogic.management.
configuration.
ApplicationMBeanAttribute: Path

Deployment Protocol The deployment protocol to use for this here application.

Staging Mode Indicates whether this application is being staged. 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.MBean: weblogic.management.
configuration.
ApplicationMBeanAttribute: StagingMode

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)MBean: weblogic.management.
configuration.
ApplicationMBeanAttribute: StagingPath

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.MBean: weblogic.management.
configuration.
ApplicationMBeanAttribute: LoadOrder Default: 100

Attribute Label	Description	Value Constraints
Name	The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.MBean: weblogic.management. configuration. ApplicationMBeanAttribute: Name
Path	The location of the original source application files on the Administration Server. 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.Note: The path displayed in the console may include extra spaces inserted for display purposes. You must remove these spaces if you select and copy this path for use in another context. MBean: weblogic.management. configuration. ApplicationMBeanAttribute: Path
Deployment Protocol	The deployment protocol to use for this here application.
Staging Mode	Indicates whether this application is being staged. 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.MBean: weblogic.management. configuration. ApplicationMBeanAttribute: StagingMode
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)MBean: weblogic.management. configuration. ApplicationMBeanAttribute: StagingPath
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.MBean: weblogic.management. configuration. ApplicationMBeanAttribute: LoadOrder	Default: 100