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

Assume that the application server is already installed and configured on system
A. Perform the following tasks:
1. Install the Web server on system B.
2. Install the Web server plug-in on system B by performing the following steps:
a. Select Remote installation.
b. Enter a name for the Web server definition. The default is webserver1.
c. Select the location for the plug-in configuration file. By default, the location
is under the config directory in the plug-in install directory. 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:
/config/webserver1/plugin-cfg.xml
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 to WebSphere
Application Server. The script is located in the following location:
/bin/configure
4. At the end of the plug-in installation, copy the script to the
/bin directory of the application server machine, system A.
Start the application server, 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 Web server
In this scenario, a stand-alone application server exists on system A. The Web
server and Web server plug-in are also installed on system A. This topology is
suited to a development environment or for internal applications. See Figure 6-3
on page 193.
192 WebSphere Application Server V7.0: Concepts, Planning, and Design