WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

During the installation, the following tasks are performed:
1. A temporary plug-in configuration file is created and placed in the
location specified.
2. The Web server configuration file is updated with the plug-in
configuration, including the location of the plug-in configuration file.
3. A script is generated to define the Web server and an unmanaged
node to WebSphere Application Server. The script is located in the
following location:
/bin/configure
4. At the end of the plug-in installation, you need to copy the script to the
/bin directory of the deployment manager machine
(system A), start the deployment manager, and execute the script.
When the Web server is defined to WebSphere Application Server, the plug-in
configuration file is generated automatically. For IBM HTTP Server, the new
plug-in file is propagated to the Web server automatically. For other Web server
types, you need to propagate the new plug-in configuration file to the Web server.
Local to a federated application server (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 deployment manager was also
installed on system A. See Figure 6-5.
System A
Web Server
Plug-in
System B
Deployment
Manager
Federate
WebSphere
Application
Server Node
Figure 6-5 Web server installed locally on an application server system
Chapter 6. Installation 195