+

Search Tips   |   Advanced Search

Set binary location and use


We can designate where binary files (binaries) used by the application reside, whether WAS distributes binaries for you automatically, and otherwise configure the use of binaries.

This page assumes that the application or module is already deployed on a server.

This page describes how to change the settings of an application or module using the admin console.

If an application is running, changing an application setting causes the application to restart. On stand-alone servers, the application restarts after you save the change. On multiple-server products, the application restarts after you 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.

 

  1. Click Applications > Application Types > WebSphere enterprise apps > application_name > Application binaries The Application binaries page is displayed.

  2. Specify the directory to hold the application binaries.

    The default is ${APP_INSTALL_ROOT}/cell_name, where the ${APP_INSTALL_ROOT} variable is $WP_PROFILE/installedApps. For example:

    PROFILE_HOME\profile_name\installedApps\cell_name
    

    Refer to Application binary settings for a detailed description of the Location (full path) setting.

  3. Specify the bindings, extensions, and deployment descriptors that an appserver uses.

    By default, an appserver uses the bindings, extensions, and deployment descriptors located with the application deployment document, deployment.xml.

    To specify that the appserver use the bindings, extensions, and deployment descriptors located in the EAR file, select Use configuration information in binary. Select this setting for applications installed on 6.x or later deployment targets. This setting is not valid for applications installed on 5.x deployment targets.

  4. Specify whether WAS distributes application binaries automatically to other nodes on the cell.

    By default, Enable binary distribution, expansion and cleanup post uninstallation is selected and binaries are distributed automatically.

    If we disable this option, then verify the application binaries are expanded appropriately in the destination directories of all nodes where the application runs.

    If we 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.

  5. Specify access permissions for binaries.

    1. Verify the Enable binary distribution, expansion and cleanup post uninstallation option is enabled. That option must be enabled to specify access permissions for binaries.

    2. For File permissions, specify a string that defines access permissions for binaries that are expanded in the named location.

      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.

      For details on File permissions, refer to Application binary settings.

  6. Click OK.

 

Results

The application or module configuration is changed. The application or stand-alone Web module is restarted so the changes take effect.

 

Next steps

If the application or module is deployed on a cluster and we have no more configuration changes to make, click Rollout Update on the Enterprise applications page to propagate the changed configuration on all cluster members of the cluster on which the application or module is deployed. Rollout Update sequentially updates the configuration on the nodes that contain cluster members.

Save changes to the admin configuration.

In multiple-server products, the application binaries are transferred to nodes when the configuration changes on the dmgr synchronize with configurations for individual nodes on which the application will run.


Application binary settings

 

Related tasks


Set enterprise application files
Deploy enterprise apps

 

Related


Enterprise application settings