Manage modules settings

Manage modules settings

Use this panel to specify deployment targets where you want to install the modules contained in your 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 appserver or Web server.
On multiple-server products, a deployment target can be an appserver, cluster of appservers, or Web server.
To view this console panel, click Applications > Enterprise Applications > application > Manage modules. This panel is the similar to the Map modules to servers panel on the application installation and update wizards.
On this panel, each Module must map to one or more desired targets, identified under Server. To change a mapping:

In the list of mappings, select the Select check box beside each module that you want mapped to the same target(s).

From the Clusters and Servers drop-down list, select one or more targets. Select only appropriate deployment targets for a module. Modules that use WAS V6.x features cannot be installed onto a V5.x target server.
Use the Ctrl key to select multiple targets. For example, to have a Web server serve your application, press the Ctrl key and then select an appserver and the Web server together. The plug-in configuration file plugin-cfg.xml for that Web server will be generated based on the applications which are routed through it.

Click Apply.

If this Manage modules panel was accessed from a console enterprise application page for an already installed application, you can also use this panel to view and manage modules in your 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, you can change existing configuration values and link to additional console pages that assist you in configuring the module.
To manage a module, enable the Select check box beside the module name in the list and click a button:

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).
On multiple-server products, if the application is running on a node when the module file is deleted from the node as a result of configuration synchronization then the application is stopped, the module file is deleted from the node's file system, and the application is restarted.
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.
On multiple-server products, if the application is running on a node when the module file is updated on the node as a result of configuration synchronization then the application is stopped, the module file is updated on the node's file system, and the application is restarted. If the application is running on a node when the module file is added as a result of configuration synchronization then the newly added module is started without stopping and restarting the running application.
Remove File Deletes a file from a module of a deployed application.
On multiple-server products, the file is also deleted from all the nodes where the module is installed after configuration is synchronized with nodes. If the application is running on a node when the module file is deleted from the node as a result of configuration synchronization then the application is stopped, the module file is deleted from the node's file system, and the application is restarted.

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 can install an application, enterprise bean (EJB) module or Web module developed for a V5.x product on a 5.x or 6.x deployment target, provided the module--

Does not support J2EE 1.4;

Does not call any 6.x runtime APIs; and

Does not use any 6.x product features.

If the module supports J2EE 1.4, then install the module on a 6.x deployment target. If the module calls a 6.1.x API or uses a 6.1.x feature, then install the module on a 6.1.x deployment target. Modules that call a 6.0.x API or use a 6.0.x feature can be installed on a 6.0.x or 6.1.x 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

Timeype of module, for example a Web module or EJB module.
This setting is shown on the Manage modules panel 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 drop-down list and click Apply. The new mapping replaces the previous mapping.

Related concepts

Installable J2EE module versions

Related tasks
Mapping modules to servers Configure J2EE applications

Related Reference

Administrative console buttons
Enterprise application settings

Reference topic

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). On multiple-server products, if the application is running on a node when the module file is deleted from the node as a result of configuration synchronization then the application is stopped, the module file is deleted from the node's file system, and the application is restarted.
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. On multiple-server products, if the application is running on a node when the module file is updated on the node as a result of configuration synchronization then the application is stopped, the module file is updated on the node's file system, and the application is restarted. If the application is running on a node when the module file is added as a result of configuration synchronization then the newly added module is started without stopping and restarting the running application.
Remove File	Deletes a file from a module of a deployed application. On multiple-server products, the file is also deleted from all the nodes where the module is installed after configuration is synchronized with nodes. If the application is running on a node when the module file is deleted from the node as a result of configuration synchronization then the application is stopped, the module file is deleted from the node's file system, and the application is restarted.