Use this page to configure the location and distribution of application binary files.
To view this administrative console page, click Applications > Enterprise Applications > application_name > Application binaries.
Specifies the directory to which the application EAR file is installed. This Location setting is the same as the Directory to install application field on the application installation and update wizards.
By default, an 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, the default value 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, 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 specified for Directory to install application when installing the application. For example, if you installed 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, 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.
A pathmap variable 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 console page, accessed by clicking .
Data type | String |
Units | Full path name |
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.
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 configuration information in binary setting is the same as the Use binary configuration field on the application installation and update wizards. 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.
Data type | Boolean |
Default | false |
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 installations, the binaries are deleted when you uninstall and save changes to the configuration.
On multiple-server installations, 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 Enable binary distribution, expansion and cleanup post uninstallation setting is the same as the Distribute application field on the application installation and update wizards.
Data type | Boolean |
Default | true |
Specifies access permissions for application binaries for installed applications that are expanded to the directory specified.
The Enable binary distribution, expansion and cleanup post uninstallation option must be enabled to specify file permissions.
You can specify file permissions in the text field. You can also set some of the commonly used file permissions by selecting them from the multiple-selection list. List selections overwrite file permissions set in the text field.
You can set one or more of the following file permission strings in the list. Selecting multiple options combines the file permission strings.
Multiple-selection list option | File permission string set |
---|---|
Allow all files to be read but not written to | .*=755 |
Allow executables to execute | .*\.dll=755#.*\.so=755#.*\.a=755#.*\.sl=755 |
Allow HTML and image files to be read by everyone | .*\.htm=755#.*\.html=755#.*\.gif=755#.*\.jpg=755 |
Instead of using the multiple-selection list to specify file permissions, you can specify a file permission string in the text field. File permissions use a string that has the following format:
file_name_pattern=permission#file_name_pattern=permission
where file_name_pattern is a regular expression file name filter (for example, .*\\.jsp for all JSP files), permission provides the file access control lists (ACLs), and # is the separator between multiple entries of file_name_pattern and permission. If # is a character in a file_name_pattern string, use \# instead.
If multiple file name patterns and file permissions in the string match a uniform resource identifier (URI) within the application, then the product uses the most stringent applicable file permission for the file. For example, if the file permission string is .*\\.jsp=775#a.*\\.jsp=754, then the abc.jsp file has file permission 754.
1 | /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war |
2 | /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/MyJsp.jsp |
3 | /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/META-INF/MANIFEST.MF |
4 | /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/WEB-INF/classes/MyClass.class |
5 | /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/mydir/MyClass2.class |
6 | /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/META-INF |
The file pattern matching results are:
/opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/MyJsp.jspand you specify the following file pattern string:
.*MyApp.ear$=755#.*\.jsp=644The file pattern matching results are:
You cannot unset read permission on a file on Windows
platforms. With POSIX style permission bits, the bit for denoting readable on
a file is 4, writable is 2, and executable is 1. Thus, permission
of a file on a Windows platform is either 5 or 7. Also, in POSIX style there
are user, group and world permissions. You can
only set the user permission for a file on Windows platforms. The group and world permission
bits are ignored.
Access permissions specified here are at the application level. You can also specify access permissions for application binaries in the node level configuration. The node level file permissions specify the maximum (most lenient) permissions that can be given to application binaries. Access permissions specified here at application level can only be the same as or more restrictive than those specified at the node level.
This setting is the same as the File permission field on the application installation and update wizards.
Data type | String |
Specifies an uneditable string that identifies the build version of the application.
Data type | String |