Enterprise application settings

 

Configure an enterprise application.

Applications > Enterprise Applications > application_name.

 

Configuration tab

 

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.

Data type	String

 

Start 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 $WAS_HOME/installedApps; for example:

/opt/WebSphere/AppServer/installedApps/cell_name

One can specify an absolute path or use a pathmap variable such as ${MY_APPS}. One can use a pathmap variable in any installation though it is particularly needed when installing an application on a cluster with members on heterogeneous nodes because, in such cases, there might not be a single way to specify an absolute path. A WAS variable ${CELL} that denotes the current cell name can also be in the pathmap variable; for example, ${MY_APP}/${CELL}.

Data type	String
Units	Full path name

 

Use Metadata From Binaries

Specifies whether the appserver 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 file.

Data type	Boolean
Default	true

 

Enable Distribution

Specifies whether WAS 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 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 WAS 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.

Data type	Boolean
Default	true

 

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. This setting takes effect only if class reloading is enabled.

The reload interval specified here overrides the value specified in the IBM extensions for each 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).

Data type	Integer
Units	Seconds

---

Deploying and managing applications
Administrative console buttons
Administrative console page features
Connector Modules collection
EJB module collection
Library reference collection
Session Management settings
Target mapping collection
Object names

 

---