Set up a remote Web server installation. The
remote Web server configuration is recommended for production environments.
The
remote installation installs the Web server plug-in on the Web server
machine when the application server is on a separate machine, such
as shown in the following graphic:

Remote
installation scenario
Table 1. Installation and configuration. Remote installation scenario
Step |
Machine |
Task |
1 |
A |
Install your WebSphere Application
Server product. Read the "Installing the product and additional software"
topic. |
2 |
B |
Install IBM® HTTP Server or another supported
Web server. See Installing IBM HTTP Server. |
3 |
B |
Install the binary plug-in module using the
Plug-ins installation wizard. See Configuring a Web server and an application server on separate machines (remote). The script for creating and configuring the
Web server is created under the plugins_root/
bin directory.
|
4 |
B |
Copy the configureweb_server_name script
to Machine A. If one machine is running under an operating system
such as AIX® or Linux® and
the other machine is running under Windows®,
copy the script from the plugins_root/bin/crossPlatformScripts directory. See Configuring a Web server and an application server on separate machines (remote) for information about cross-platform scripts and
file encoding differences.
|
5 |
A |
Paste the configureweb_server_name script
from Machine B to the app_server_root/bin directory
on Machine A. |
6 |
A |
Start the application server, then run the script
from a command line. |
7 |
A |
Verify that the application server is running.
Open the administrative console and save the changed configuration. |
8 |
B |
Source
the plugins_root/setupPluginCfg.sh script
for a Domino® Web Server before starting a Domino Web
server.
Start the Web server.
|
9 |
B |
Run the snoop servlet. Access the following
URL in your browser: http://host_name_of_machine_B:http_transport_port/snoop
To
verify with your own application, regenerate and propagate the plugin-cfg.xml file
after installing the application.
|
Regeneration of the plugin-cfg.xml file
The
Web server plug-in configuration service regenerates the plugin-cfg.xml file
automatically.
During the installation of the plug-ins,
the temporary plugin-cfg.xml file is installed
on Machine B in the plugins_root/config/
web_server_name directory. To use the actual plugin-cfg.xml file
from the application server, propagate the plugin-cfg.xml file
as described in the next section.
Propagation of the plugin-cfg.xml file
The Web server
plug-in configuration service propagates the plugin-cfg.xml file
automatically for IBM HTTP Server Version 6.0 or later.
For all other Web servers, propagate the plug-in configuration file
manually. Copy the plugin-cfg.xml file from the profile_root/
config/cells/cell_name/nodes/web_server_name_node/servers/web_server_name directory
on Machine A. Paste the file into the plugins_root/config/web_server_name directory
on Machine B.
Set up a local Web server configuration. The
local Web server configuration is recommended for a development or
test environment.
A local installation includes the Web server
plug-in, the Web server, and the Application Server on the same machine:

Local installation scenario
Table 2. Installation and configuration. Local installation
scenario
Step |
Machine |
Task |
1 |
A |
Install your WebSphere Application
Server product. Read the "Installing the product and additional software"
topic. |
2 |
A |
Install IBM HTTP Server or another supported
Web server. See Installing IBM HTTP Server. |
3 |
A |
Install the binary plug-in module using the
Plug-ins installation wizard. See Configuring a Web server and an application server profile on the same machine. The Web server
definition is automatically created and configured during the installation
of the plug-ins.
|
4 |
A |
Verify that the application server is running.
Open the administrative console and save the changed configuration. |
5 |
A |
Run the plugins_root/setupPluginCfg.sh script
for a Domino Web Server before starting a Domino Web
server.
Otherwise, start the Web server. |
6 |
A |
Run the snoop servlet. Access the following
URL in your browser: http://host_name_of_machine_A:http_transport_port/snoop
To
verify with your own application, regenerate and propagate the plugin-cfg.xml file
after installing the application.
|
Regeneration of the plugin-cfg.xml file
The
Web server plug-in configuration service regenerates the plugin-cfg.xml file
automatically.
The plugin-cfg.xml file
is generated in the profile_root/config/cells/cell_name/nodes/web_server_name_node/servers/web_server_name directory.
The generation occurs when the Web server definition is created.
Propagation
of the plugin-cfg.xml file
The local file does not require
propagation.