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 application server or Web server.
To view this administrative console panel, click Applications > Enterprise Applications > application_name > 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:
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 application server 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.
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). |
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 you 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 and specify a location to save the file that is shown in the browser. |
Lists the names of available deployment targets. This list is the same for every application that is installed in the cell.
If the module supports J2EE 1.4, then you must 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 you must 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.
Specifies the name of a module in the installed (or deployed) application.
Specifies the location of the module relative to the root of the application (EAR file).
Specifies the type 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.
Specifies the 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.