Tasks
Local to a federated appserver (managed node)
In this scenario, the Web server is installed on a system that also has a managed node. This scenario would be the same if the dmgr was also installed on system A.
![]()
Assume that the appserver is already installed, configured, and federated to the dmgr cell. Perform the following tasks:
- Install the Web server on system A.
- Install the Web server plug-in on system A by performing the following steps:
- Select Local installation.
- Enter a name for the Web server definition. The default is webserver1.
- Select the location for the plug-in configuration file. By default, the file is placed in the directory that contains the server's configuration. For example, when the name specified for the Web server definition in the previous step is webserver1, the default location for the plug-in file is as follows:
<profile_root>/config/cells/<cell_name>/nodes/<AppSrv_node>/servers/webserver1/plugin-cfg.xml
During the installation, the following tasks are performed:
- The plug-in configuration file is created and placed in the location specified.
- The Web server configuration file is updated with the plug-in configuration, including the location of the plug-in configuration file.
- A script is generated to define the Web server and an unmanaged node to WAS. The script is located in the following location:
<plugin_root>/Plugins/bin/configure<web_server_name>- At the end of the plug-in installation, we need to execute the script to define the Web server from the location in which the wizard stored it on system A. Make sure that the dmgr is running on system B. The dmgr configuration is updated and propagated back to system A at node synchronization.
The plug-in configuration file is generated automatically and propagated at the next node synchronization.
For security reasons we do not suggest installing managed Web servers in the DMZ.