+

Search Tips   |   Advanced Search

Application binary settings

Configure the location and distribution of application binary files.

From the admin console, click...

        Applications > Application Types > WebSphere enterprise applications > application_name > Application binary files.

If any value is modified on this page, all of the metadata files related to the application are refreshed in the configuration repository.

If an application is running, changing an application setting causes the application to restart. On stand-alone servers, the application restarts after we save the change. On multiple-server products, the application restarts after we save the change and files synchronize on the node where the application is installed. To control when synchronization occurs on multiple-server products, deselect Synchronize changes with nodes on the Console preferences page.


Location (full path)

Directory to which the enterprise application archive (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.

Set options include the following:

Information Value
Data type String
Units Full path name


Use configuration information in binary

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 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 or later deployment targets only.

Information Value
Data type Boolean
Default false


Enable binary distribution, expansion and cleanup post uninstallation

Specifies whether the product expands application binary files in the installation location during installation and deletes application binary files during uninstallation. The default is to enable application distribution. Application binary files for installed applications are expanded to the directory specified.

On single-server installations, the binary files are deleted when you uninstall the application and save changes to the configuration.

The Enable binary distribution, expansion and cleanup post uninstallation is not intended to be changed after the application is installed. To change this attribute, uninstall the application and install it with the new value for the attribute.

On multiple-server installations, the binary files are deleted when you uninstall the application and save changes to the configuration and synchronize changes.

If you disable this option, ensure that the application binary files are expanded appropriately in the destination directories of all nodes where the application runs.

If you disable this option and we do not copy and expand the application binary files to the nodes, a later saving of the configuration or manual synchronization does not move the application binary files 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.

Information Value
Data type Boolean
Default true


File permissions

Specifies access permissions for application binary files 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.

We can specify file permissions in the text field. We 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.

We 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, we 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. 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:best-practices

Number Example URI
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:

If we 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 we have the following file and directory structure:

/opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/MyJsp.jsp
and we specify the following file pattern string:
.*MyApp.ear$=755#.*\.jsp=644
The file pattern matching results are:

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

(Windows) We 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. We 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. We can also specify access permissions for application binary files in the node level configuration. The node level file permissions specify the maximum (most lenient) permissions that can be given to application binary files. 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.

Information Value
Data type String


Application build level

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

Information Value
Data type String

  • Configure enterprise application files
  • Deploy and administering enterprise applications
  • Enterprise application settings