Manage modules settings

WAS v8.5 > Reference > Sets
Manage modules settings page

Use this page to specify deployment targets where to install the modules that are contained in the application. Modules can be installed on the same deployment target or dispersed among several deployment targets.
On single-server products, a deployment target can be an application server or web server.
To view this dmgr console page, click Applications > Application Types > WebSphere enterprise applications > application_name > Manage modules. This page is the similar to the Map modules to servers page on the application installation and update wizards.
On this page, each Module must map to one or more targets, identified under Server. To change a mapping:

In the list of mappings, select each module you want mapped to the same target or targets.

From the Clusters and servers list, select one or more targets. Select only appropriate deployment targets for a module. We cannot install modules that use WebSphere Application Server v8.x features on a v7.x or 6.x target server. Similarly, we cannot install modules that use v7.x features on a v6.x target server.
Use the Ctrl key to select multiple targets. For example, to have a web server serve the application, press the Ctrl key and then select an application server and the web server together. WAS v8.5 generates plugin-cfg.xml, plugin-cfg.xml, for that web server based on the applications which are routed through it.

Click Apply.

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.
If we accessed this Manage modules page from a console enterprise application page for an already installed application, we can also use this page to view and manage modules in the application.
To view the values specified for a module configuration, click the module name in the list. The displayed module settings page shows the values specified. On the settings page, we can change existing configuration values and link to additional console pages that assist you in configuring the module.
To manage a module, select the module name in the list and click a button:
Button descriptions. Use the buttons to manage modules.

Button Resulting action
Remove Removes the selected module from the deployed application. The module is deleted from the application in the configuration repository and also from all of the nodes where the application is installed and running or expected to run.
Update Opens a wizard that helps you update modules in an application. If a module has the same URI as a module already existing in the application, the new module replaces the existing module. If the new module does not exist in the application, it is added to the deployed application.
Remove File Deletes a file from a module of a deployed application.
Export File Accesses the Export a file from an application page, which we use to export a file of an enterprise application or module to a location of your choice.
If the browser does not prompt for a location to store the file, click File > Save as and specify a location to save the file that is shown in the browser.

Clusters and servers

Lists the names of available deployment targets. This list is the same for every application that is installed in the cell.
From this list, select only appropriate deployment targets for a module. You must install an application, EJB module, SIP archive (SAR), web module, or client module on a v8.x target under any of the following conditions:

The module supports Java EE 6.

The module calls an 8.x runtime API.

The module uses an 8.x product feature.

You must install an application, EJB, SAR, or web module on a v8.x or 7.x target under any of the following conditions:

The module supports Java EE 5.

The module calls a 7.x runtime API.

The module uses a 7.x product feature.

If a module supports J2EE 1.4, then install the module on a v6.x, 7.x or 8.x deployment target. Modules that call a 6.1.x API or use a 6.1.x feature can be installed on a 6.1.x, 7.x or 8.x deployment target. Modules that require 6.1.x feature pack functionality can be installed on a 6.1.x deployment target that has been enabled with that feature pack or on a 7.x or 8.x deployment target.
We can install an application or module developed for a v5.x product on any deployment target.

Module

Name of a module in the installed (or deployed) application.

URI

Location of the module relative to the root of the application (EAR file).

Module type

Type of module, for example, a web module or EJB module.
This setting is shown on the Manage modules page accessed from a console enterprise application page.

Server

Name of each deployment target to which the module currently is mapped.
To change the deployment targets for a module, select one or more targets from the Clusters and servers list and click Apply. The new mapping replaces the previous mapping.

Related concepts:

Installable enterprise module versions
Multiple security domains

Related

Map modules to servers
Configure enterprise application files

Reference:

Enterprise application settings

+
Search Tips | Advanced Search

Button	Resulting action
Remove	Removes the selected module from the deployed application. The module is deleted from the application in the configuration repository and also from all of the nodes where the application is installed and running or expected to run.
Update	Opens a wizard that helps you update modules in an application. If a module has the same URI as a module already existing in the application, the new module replaces the existing module. If the new module does not exist in the application, it is added to the deployed application.
Remove File	Deletes a file from a module of a deployed application.
Export File	Accesses the Export a file from an application page, which we use to export a file of an enterprise application or module to a location of your choice. If the browser does not prompt for a location to store the file, click File > Save as and specify a location to save the file that is shown in the browser.