Install and configure Web server plug-ins for WebSphere Application
Server to allow the application server to communicate with the Web server.
Before you begin
The primary production configuration for a Web server is an application
server on one machine and a Web server on a separate machine. This configuration
is referred to as a remote configuration. Contrast the
remote configuration to the local configuration, where the application server
and the Web server are on the same machine.
About this task
The Plug-ins installation wizard has four main tasks:
- Installs the binary plug-in module on the Web server machine.
- Configures the Web server configuration file on the Web server machine
to point to the binary plug-in module and to the XML configuration file for
the binary module.
- Installs a temporary XML configuration file for the binary module (plugin-cfg.xml)
on the Web server machine in remote scenarios.
- Creates the configuration for a Web server definition on the application
server machine. The wizard processes the creation of the Web server definition
differently depending on the scenario:
- Recommended remote
stand-alone application server installation:
Creates a configuration
script that you run on the application server machine. Install the Web server
and its plug-in on a different machine than the application server. This configuration
is recommended for a production environment.
- Local stand-alone
application server installation:
Detects the default profile on
a local application server machine and creates the Web server definition for
it directly. Install the Web server and its plug-in on the same machine with
the application server. This configuration is for development and test environments.
Select a link to go to the appropriate steps in the following
procedure.
Procedure
- 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
Step |
Machine |
Task |
1 |
A |
Install your WebSphere Application Server product. See Installing the product and additional software. |
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. 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 6.0 only. 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
Step |
Machine |
Task |
1 |
A |
Install your WebSphere Application Server product. See Installing the product and additional software. |
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. 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.
Results
You can set up a remote or local Web server by installing Application
Server, the Web server, and then the Web server plug-ins.