Use this panel to specify options for the installation of an application onto a WebSphere® Application Server deployment target. Default values for the options are used if you do not specify a value. After application installation, you can specify values for many of these options from an enterprise application settings page.
To view this administrative console panel, click Applications > Install New Application and then specify values as needed for your application on the Preparing for application installation pages.
The Select installation options panel is the same for the application installation and update wizards.
Specify whether to precompile JavaServer Pages (JSP) files as a part of installation. The default is not to precompile JSP files.
For this option, install only onto a 6.0.x deployment target.
If you select Pre-compile JSP and try installing your application onto an earlier deployment target such as version 5.x, the installation is rejected. You can deploy applications to only those targets that have same WebSphere version as the product. If applications are targeted to servers that have an earlier version than the product, then you cannot deploy to those targets.
Data type | Boolean |
Default | false |
Specifies the directory to which the enterprise archive (EAR) file will be installed.
By default, the EAR file is installed in the profile_root/installedApps/cell_name/application_name.ear directory.
Setting options include the following:
If you do not specify a directory for Directory to install application, the default value of is used. The default value is ${APP_INSTALL_ROOT}/cell_name, where the ${APP_INSTALL_ROOT} variable is profile_root/installedApps. A directory having the EAR file name of the application being installed is appended to ${APP_INSTALL_ROOT}/cell_name. Thus, if you do not specify a directory, the EAR file is installed in the profile_root/installedApps/cell_name/application_name.ear directory.
If you specify a directory for Directory to install application, the application is installed in specified_path/application_name.ear directory. A directory having the EAR file name of the application being installed is appended to the path that you specify for Directory to install application. For example, if you are installing Clock.ear and specify C:/myapps on Windows machines, the application is installed in the myapps/Clock.ear directory. The ${APP_INSTALL_ROOT} variable is set to the specified path.
If you intend to export the application from one cell and later install the exported application on a different cell, specify the $(CELL) variable for the initial installation of the application. For example, specify ${APP_INSTALL_ROOT}/${CELL} for this setting. Exporting the application creates an enhanced EAR file that has the application and its deployment configuration. The deployment configuration retains the cell name of the initial installation in the destination directory unless you specify the ${CELL} variable. Specifying the ${CELL} variable ensures that the destination directory has the current cell name, and not the original cell name.
The exported EAR file is an enhanced EAR file that has the application and its deployment configuration. The deployment configuration retains the value for Directory to install application that was used for the previous installation of the application. Unless you specify a different value for Directory to install application for this installation, the enhanced EAR file will be installed to the same directory as for the previous installation.
If you did not specify the ${CELL} variable during the initial installation, the deployment configuration uses the cell name of the initial installation in the destination directory. If you are installing on a different cell, specify ${APP_INSTALL_ROOT}/cell_name/application_name.ear, where cell_name is the name of the cell to which you want to install the enhanced EAR file. If you do not designate the current cell name, cell_name will be the original cell name even though you are installing the enhanced EAR file on a cell that has a different 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.
This Directory to install application field is the same as the Application binaries setting on an Enterprise Application settings page.
Data type | String |
Units | Full path name |
Specifies whether the product expands application binaries in the installation location during installation and deletes application binaries during uninstallation. The default is to enable application distribution. Application binaries for installed applications are expanded to the directory specified.
On single-server products, the binaries are deleted when you uninstall and save changes to the configuration.
On multiple-server products, the binaries are deleted when you uninstall and save changes to the configuration and synchronize changes.
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.
This Distribute application field is the same as the Enable distribution setting on an Enterprise Application settings page.
Data type | Boolean |
Default | true |
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. Select this setting for applications installed on 6.x deployment targets only. This setting is not valid for applications installed on 5.x deployment targets.
The default (false) is to use the binding, extensions, and deployment descriptors located in deployment.xml. To use the binding, extensions, and deployment descriptors located in the EAR file, enable this setting (true).
This Use binary configuration field is the same as the Use metadata from binaries setting on an Enterprise Application settings page.
Data type | Boolean |
Default | false |
Specifies whether the EJBDeploy tool runs during application installation.
For this option, install only onto a 6.0.x deployment target.
If you select Deploy enterprise beans and try installing your application onto an earlier deployment target such as version 5.x, the installation is rejected. You can deploy applications to only those targets that have same WebSphere version as the product. If applications are targeted to servers that have an earlier version than the product, then you cannot deploy to those targets.
Also, if you select Deploy enterprise beans and specify a database type on the Provide options to perform the EJB Deploy panel, previously defined backend IDs for all of the EJB modules are overwritten by the chosen database type. To enable backend IDs for individual EJB modules, set the database type to "" (null) on the Provide options to perform the EJB Deploy panel.
The default database type is DB2UDB_V81.
Enabling this setting might cause the installation program to run for several minutes.
Data type | Boolean |
Default | true |
Specifies a logical name for the application. An application name must be unique within a cell and cannot contain an unallowed character.
An application name cannot begin with a period (.), cannot contain leading or trailing spaces, and cannot contain any of the following characters:
Unallowed characters | ||
---|---|---|
⁄ forward slash | $ dollar sign | ' single quote mark |
\ backslash | = equal sign | " double quote mark |
* asterisk | % percent sign | | vertical bar |
, comma | + plus sign | < left angle bracket |
: colon | @ at sign | > right angle bracket |
; semi-colon | # hash mark | & ampersand (and sign) |
? question mark | ]]> No specific name exists for this character combination |
This Application name field is the same as the Name setting on an Enterprise application settings page.
Data type | String |
Specifies whether to create MBeans for resources such as servlets or JSP files within an application when the application starts. The default is to create MBeans.
Data type | Boolean |
Default | true |
Specifies whether to enable class reloading when application files are updated.
The default is not to enable class reloading.
Data type | Boolean |
Default | false |
Specifies the number of seconds to scan the application's file system for updated files. The default is the value of the reloading interval attribute in the IBM extension (META-INF/ibm-application-ext.xmi) file of the EAR file.
The reloading interval attribute takes effect only if class reloading is enabled.
To enable reloading, specify a value greater than zero (for example, 1 to 2147483647). To disable reloading, specify zero (0). The range is from 0 to 2147483647.
This Reload interval in seconds field is the same as the Reloading interval setting on an Enterprise Application settings page.
Data type | Integer |
Units | Seconds |
Default | 3 |
Specifies whether the Web services deploy tool wsdeploy runs during application installation.
The tool generates code needed to run applications using Web services. The default is not to run the wsdeploy tool. You must enable this setting if the EAR file contains modules using Web services and has not previously had the wsdeploy tool run on it, either from the Deploy menu choice of an assembly tool or from a command line.
For this option, install only onto a 6.0.x deployment target.
If you select Deploy Web services and try installing your application onto an earlier deployment target such as version 5.x, the installation is rejected. You can deploy applications to only those targets that have same WebSphere version as the product. If applications are targeted to servers that have an earlier version than the product, then you cannot deploy to those targets.
Data type | Boolean |
Default | false |
Specifies whether WebSphere Application Server examines the application references specified during application installation or updating and, if validation is enabled, warns you of incorrect references or fails the operation.
An application typically refers to resources using data sources for container managed persistence (CMP) beans or using resource references or resource environment references defined in deployment descriptors. The validation checks whether the resource referred to by the application is defined in the scope of the deployment target of that application.
Select off for no resource validation, warn for warning messages about incorrect resource references, or fail to stop operations that fail as a result of incorrect resource references.
This Validate input off/warn/fail field is the same as the Validation setting on an Enterprise Application settings page.
Data type | String |
Default | warn |
Specifies whether the embedded configuration should be processed. An embedded configuration consists of files such as resource.xml and variables.xml. When selected or true, the embedded configuration is loaded to the application scope from the .ear file. If the .ear file does not contain an embedded configuration, the default is false. If the .ear file contains an embedded configuration, the default is true.
Data type | Boolean |
Default | false |