Use this page to configure an enterprise application.
To view this administrative console page, click Applications > Enterprise Applications > application_name.
Configuration tab
Data type | String |
Data type | Integer |
Default | 1 |
Range | 0 to 100 |
You can specify an absolute path or use a pathmap variable such as ${MY_APPS}. You 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 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 |
Data type | Boolean |
Default | false |
Note: If you disable this option and you do not copy and expand the application binaries to the nodes, a later saving of the configuration or manual synchronization does not move the application binaries to the nodes for you.
Data type | Boolean |
Default | true |
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 |
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 |
Data type | Boolean |
Default | true |
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. If the ibm-web-ext.xmi file does not define reloadingEnabled, the product assumes reloadingEnabled is set to true.
To enable reloading of a Web module, where you also want reloading of EJB and non-Web modules enabled:
To enable reloading of a Web module only, and not enable reloading of EJB or non-Web modules:
To disable reloading of a Web module, set the IBM extension reloadingEnabled in the ibm-web-ext.xmi file to false.
Data type | Boolean |
Default | false |
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 |