+

Search Tips   |   Advanced Search

Application binary settings

Use this page to configure the location and distribution of application binary files.

To view this console page, click Applications > Enterprise Applications > application > Application binaries.

 

Configuration tab

Location (full path)

Specify 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.

The default value is the value of APP_INSTALL_ROOT/cell, where the APP_INSTALL_ROOT variable is APP_SERVER_ROOT/installedApps; for example, APP_SERVER_ROOT/installedApps/cell.

If an installation directory is not specified when an application is installed on a single-server configuration, the application is installed in APP_INSTALL_ROOT/cell. When the server is made a part of a ND configuration (using the addNode utility), the cell name of the new configuration becomes the cell name of the deployment manager node. If the -includeapps option is used for the addNode utility, then the applications that are installed prior to the addNode operation still use the installation directory APP_INSTALL_ROOT/cell. However, an application that is installed after the server is added to the network configuration uses the default installation directory APP_INSTALL_ROOT/network_cell_name. To move the application to the APP_INSTALL_ROOT/network_cell_name location upon running the addNode operation, explicitly specify the installation directory as ${APP_INSTALL_ROOT}/${CELL) during installation. In such a case, the application files can always be found under APP_INSTALL_ROOT/current_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.

on multiple-server installations, 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 WAS variable ${CELL} that denotes the current cell name can also be in the pathmap variable; for example, ${MY_APP}/${CELL}. You can define WAS variables on the WebSphere Variables console page, accessed by clicking Environment > WebSphere Variables.

Data type String
Units Full path name

Use configuration information in binary

Specify 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 (EAR) file.

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

Enable binary distribution, expansion and cleanup post uninstallation

Specify 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 ensure that the application binaries are expanded appropriately in the destination directories of all nodes where the application runs.

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.

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

File permissions

Specify 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 drop-down list. Drop-down list selections overwrite file permissions set in the text field.

You can set one or more of the following file permission strings in the drop-down list. Selecting multiple options combines the file permission strings.

Drop-down 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 drop-down 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.

Using regular expressions for file matching pattern compares an entire string URI against the specified file permission pattern. You must provide more precise matching patterns using regular expressions as defined by Java programming API. For example, suppose the following directory and file URIs are processed during a file permission operation:

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:

  • MyWarModule.war does not match any of the URIs

  • .*MyWarModule.war.* matches all URIs

  • .*MyWarModule.war$ matches only URI 1

  • .*\\.jsp=755 matches only URI 2

  • .*META-INF.* matches URIs 3 and 6

  • .*MyWarModule.war/.*/.*\.class matches URIs 4 and 5

If you specify a directory name pattern for File permissions, then the directory permission is set based on the value specified. Otherwise, the File permissions value set on the directory is the same as its parent. For example, suppose you have the following file and directory structure: 

/opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/MyJsp.jsp
and you specify the following file pattern string: 

.*MyApp.ear$=755#.*\.jsp=644
The file pattern matching results are:

  • Directory MyApp.ear is set to 755

  • Directory MyWarModule.war is set to 755

  • Directory MyWarModule.war is set to 755

Regardless of the operation system, always use a forward slash (/) as a file path separator in file patterns.

[Windows] 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

Application build level

Specify an uneditable string that identifies the build version of the application.

Data type String



 

Related tasks


Configure J2EE applications
Deploying and administering J2EE applications

 

Related Reference

Enterprise application settings

 

Reference topic