Mapping modules to servers

 

Mapping modules to servers

Each module of a deployed application must be mapped to one or more target servers. The target server can be an application server, cluster of application servers or Web server.

You can map modules of an application or standalone Web module to one or more target servers during or after application installation using the console. This article assumes that the module is already installed on a server and that you want to change the mappings.

Before you change a mapping, check the deployment targets. You must specify an appropriate deployment target for a module. Modules that use Version 6.x features cannot be installed onto a Version 5.x target server.

During application installation, different deployment targets might have been specified.

You use the Map modules to servers panel of the administrative console to view and change mappings. This panel is displayed during application installation using the console and, after the application is installed, can be accessed from the settings page for an enterprise application.

On the Map modules to servers panel, specify target servers where you want to install the modules contained in your application. Modules can be installed on the same application server or dispersed among several application servers. Also, specify the Web servers as targets that will serve as routers for requests to your application. The plug-in configuration file plugin-cfg.xml for each Web server is generated based on the applications which are routed through it.

  1. Click Applications > Enterprise Applications > application_name > Map modules to servers in the console navigation tree. The Selecting servers - Map modules to servers panel is displayed.

  2. Examine the list of mappings. Ensure that each Module entry is mapped to the desired target(s), identified under Server .

  3. Change a mapping as needed.

    1. Select each module that you want mapped to the same target(s). In the list of mappings, place a check mark in the Select check boxes beside the modules.

    2. From the Clusters and Servers drop-down list, select one or more targets. Use the Ctrl key to select multiple targets. For example, to have a Web server serve your application, use the Ctrl key to select an application server or cluster and the Web server together in order to have the plug-in configuration file plugin-cfg.xml for that Web server generated based on the applications which are routed through it.

    3. Click Apply .

  4. Repeat steps 2 and 3 until each module maps to the desired target(s).

  5. Click OK .

ResultThe application or module configurations are changed. The application or standalone Web module is restarted so the changes take effect.

 

What to do next

Save changes to your administrative configuration.

In the Network Deployment product, the application binaries are transferred to nodes when the configuration changes on the deployment manager synchronize with configurations for individual nodes on which the application will run.

If the application or module is deployed on a cluster and you 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.

Related concepts
Installable module versions

Related tasks
Configuring an application