Each module of a deployed application must be mapped to one or more target servers. The target server can be an application server or web server.
You can map modules of an application or stand-alone Web module to one or more target servers during or after application installation using the console. This topic 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 8.x features cannot be installed onto Version 7.x or 6.x target servers. Similarly, modules that use Version 7.x features cannot be installed onto Version 6.x target servers.
During application installation, different deployment targets might have been specified.
You use the Manage modules page of the administrative console to view and change mappings. This page is displayed during application installation using the console and, after the application is installed, can be accessed from the enterprise application settings page.
On the Manage modules page, 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.
The application or module configurations are changed. The application or stand-alone web module is restarted so the changes take effect.
To install an application that has modules which support Java Platform, Enterprise Edition (Java EE) 5 or 6 to two servers, do the following:
Save changes to your administrative configuration.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |