-
Name
- Specifies a logical name for the application. Application names
must be unique within a cell and cannot contain characters that are not allowed
in object names.
-
Starting Weight
- Specifies the order in which applications are started when the
server starts. The application with the lowest starting weight is started
first.
| Data type |
Integer |
| Default |
1 |
| Range |
0 to 100 |
-
Application Binaries
- Specifies the directory to which the application EAR file will
be installed. The default value is the value of APP_INSTALL_ROOT/cell_name,
where the APP_INSTALL_ROOT variable is install_root/installedApps;
for example, C:\WebSphere\AppServer\installedApps\cell_name.
You can specify an absolute path or use a pathmap variable such as ${MY_APPS}.
You can use a pathmap variable in any installation. A WebSphere Application Server
variable ${CELL} that denotes the current cell name can also be in the pathmap
variable; for example, ${MY_APP}/${CELL}.
You can define WebSphere Application Server variables on the WebSphere
Variables page of the administrative console, accessed by clicking Environment
> Manage WebSphere Variables.
| Data type |
String |
| Units |
Full path name |
-
Use Metadata From Binaries
- Specifies whether the application server uses the binding, extensions,
and deployment descriptors located with the application deployment document,
the deployment.xml file (default), or those located in the enterprise
application resource (EAR) file.
| Data type |
Boolean |
| Default |
false |
-
Enable Distribution
- Specifies whether WebSphere Application Server expands or deletes
application binaries in the installation destination. The default is to enable
application distribution. Application binaries for installed applications
are expanded to the directory specified. The binaries are also deleted when
you uninstall and save changes to the configuration. If you disable this
option, then you must ensure that the application binaries are expanded appropriately
in the destination directories of all nodes where the application runs.
| Data type |
Boolean |
| Default |
true |
-
Classloader Mode
- Specifies whether the class loader searches in the parent class
loader or in the application class loader first to load a class. The standard
for JDK class loaders and WebSphere Application Server class loaders is PARENT_FIRST.
By specifying PARENT_LAST, your application can override classes contained
in the parent class loader, but this action can potentially result in ClassCastException
or LinkageErrors if you have mixed use of overridden classes and non-overridden
classes.
The options are PARENT_FIRST and PARENT_LAST. The default is to search
in the parent class loader before searching in the application class loader
to load a class.
| Data type |
String |
| Default |
PARENT_FIRST |
-
WAR Classloader Policy
- Specifies whether to use a single class loader to load all WAR
files of this application or to use a different class loader for each WAR
file.
The options are APPLICATION and MODULE. The default is to use a separate
class loader to load each WAR file.
| Data type |
String |
| Default |
MODULE |
-
Create MBeans for Resources
- Specifies whether to create MBean files for various resources (such
as servlets or JSP files) within an application.
| Data type |
Boolean |
| Default |
true |
-
Reload Enabled
- Specifies whether to enable class reloading when application files
are updated.
For EJB modules or any non-Web modules, setting Reload Enabled to true sets
reloadEnabled to true in the deployment.xml file for the
application. If an application's class definition changes, the application
server run time stops and starts the application to reload application classes.
For Web modules such as servlets and JavaServer page (JSP) files, a Web
container reloads a Web module only when the IBM extension reloadingEnabled
in the ibm-web-ext.xmi file is set to true. You can set
reloadingEnabled to true when editing your Web module's extended
deployment descriptors in an assembly tool.
To enable reloading of a Web module, where you also want reloading of EJB
and non-Web modules enabled:
- Set the IBM extension reloadingEnabled in the ibm-web-ext.xmi file
to true.
- Set this Reload Enabled property to true.
- Set the Reload Interval property to a value greater than zero (for
example, 1 to 2147483647).
To enable reloading of a Web module only, and not enable reloading of EJB
or non-Web modules:
- Set the IBM extension reloadingEnabled in the ibm-web-ext.xmi file
to true.
- Set the IBM extension reload interval attribute in the ibm-web-ext.xmi file
to a value greater than zero (for example, 1 to 2147483647).
- Set this Reload Enabled property to false.
To disable reloading of a Web module, set the IBM extension reloadingEnabled
in the ibm-web-ext.xmi file to false. Or, if the Web module
has the IBM extension reloadingEnabled in the ibm-web-ext.xmi file
set to true, to disable reloading using the administrative console:
- Set this Reload Enabled property to true.
- Set the Reload Interval property to zero (0).
| Data type |
Boolean |
| Default |
false |
-
Reload Interval
- Specifies the number of seconds to scan the application's file
system for updated files. The default is the value of the reload interval
attribute in the IBM extension (META-INF/ibm-application-ext.xmi)
file of the EAR file.
To enable reloading, specify a value greater than zero (for example, 1
to 2147483647). To disable reloading, specify zero (0).
The reload interval specified here overrides the value specified in the
IBM extensions for each non-Web module in the EAR file (which in turn overrides
the reload interval specified in the IBM extensions for the application in
the EAR file). The reload interval attribute takes effect only if class reloading
is enabled.
The range is from 0 to 2147483647.
| Data type |
Integer |
| Units |
Seconds |