Use this page to specify deployment targets where you want to install the modules that are 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 page, click Map modules to servers page on the application installation and update wizards.
. This page is the similar to theOn this page, each Module must map to one or more 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 product generates the plug-in configuration file, plugin-cfg.xml, for that web server based on the applications which are routed through it.
If you accessed this Manage modules page from a console enterprise application page for an already installed application, you can also use this page 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, select 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.
From this list, select only appropriate deployment targets for a module. You must install an application, enterprise bean (EJB) module, Session Initiation Protocol (SIP) archive (SAR), web module, or client module on a Version 8.x target under any of the following conditions:
You must install an application, EJB, SAR, or web module on a Version 8.x or 7.x target under any of the following conditions:
If a module supports J2EE 1.4, then you must install the module on a Version 6.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.
You can install an application or module developed for a Version 5.x product on any 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 page 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 list and click Apply. The new mapping replaces the previous mapping.