Select a web server topology diagram and roadmap

WAS v8.5 > Set up intermediary services > Implement a web server plug-in > Install and configure web server plug-ins
Select a web server topology diagram and roadmap

Install and configure the Web Server Plug-ins to allow the application server to communicate with the web server.
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.
The Web Server Plug-ins Configuration Tool has three main tasks:

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 Web Server Plug-ins Configuration Tool processes the creation of the web server definition differently depending on the scenario:

As an alternative to using the Web Server Plug-ins Configuration Tool, we can use the pct command-line tool with a response file to configure a web server. Read Configure a web server plug-in using the pct tool for more information.

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
Installation and configuration. Remote installation scenario

Step Machine Task
1 A Install Installation Manager.
2 A Use Installation Manager to install the WebSphere Application Server product.
3 A Create a standalone application server profile.
4 B Install Installation Manager.
5 B Use Installation Manager to install the following:

Web Server Plug-ins for WAS
WebSphere Customization Toolbox

6 B Use Installation Manager to install IBM HTTP Server, or install another supported web server.
7 B Open the WebSphere Customization Toolbox, and launch the Web Server Plug-ins Configuration Tool to configure the web server plug-in.
The script for creating and configuring the web server is created under the plugins_root/bin directory.
8 B Copy the configureweb_server_name script to paste on 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.
9 A Paste the configureweb_server_name script from Machine B to the app_server_root/bin directory on Machine A.
10 A Start the application server.
11 A Run the script from a command line.
12 A Verify the application server is running. Open the dmgr console and save the changed configuration.
13 A Create a secure connection between the web server plug-in and the internal HTTP transport in the application server.
This step is required for the web server to function properly. For detailed instructions on creating the secure connection, read the article on configuring the web server plug-in for Secure Sockets Layer.
14 B Start the web server.
Source the plugins_root/setupPluginCfg.sh script for a Domino Web Server before starting a Domino Web Server.
15 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 our 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 plugin-cfg.xml automatically.
During configuration, 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 plugin-cfg.xml 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 v6.0 or later. For all other web servers, propagate plugin-cfg.xml 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
Installation and configuration. Local installation scenario

Step Machine Task
1 A Install Installation Manager.
2 A Use Installation Manager to install the following:

WAS product
Web Server Plug-ins for WAS
WebSphere Customization Toolbox

3 A Use Installation Manager to install IBM HTTP Server, or install another supported web server.
4 A Create a standalone application server profile.
5 A Open the WebSphere Customization Toolbox, and launch the Web Server Plug-ins Configuration Tool to configure the web server plug-in and create the web server definition.
The web server definition is automatically created and configured during the configuration of the plug-in.
6 A Start the application server.
7 A Verify the application server is running. Open the dmgr console and save the changed configuration.
8 A Create a secure connection between the web server plug-in and the internal HTTP transport in the application server.
This step is required for the web server to function properly. For detailed instructions on creating the secure connection, read the article on configuring the web server plug-in for Secure Sockets Layer.
9 A Start the web server.
Run the plugins_root/setupPluginCfg.sh script for a Domino Web Server before starting a Domino Web Server.
10 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 our 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 plugin-cfg.xml 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
We can set up a remote or local web server by installing Application Server, the web server, and then the Web Server Plug-ins.

See Web server configuration for more information about the files involved in configuring a web server.
See Plug-ins configuration for information about the logic behind the processing scenarios for the Web Server Plug-ins Configuration Tool.
See Edit web server configuration files for information about how the Web Server Plug-ins Configuration Tool configures supported web servers.
See Install and configure web server plug-ins for information about other installation scenarios for installing Web Server Plug-ins.

Related concepts:

Web server plug-ins

Related

Configure a web server plug-in using the pct tool
Install and configure web server plug-ins
Configure the web server plug-in for Secure Sockets Layer

Reference:

Web server plug-in properties

+
Search Tips | Advanced Search

Step	Machine	Task
1	A	Install Installation Manager.
2	A	Use Installation Manager to install the WebSphere Application Server product.
3	A	Create a standalone application server profile.
4	B	Install Installation Manager.
5	B	Use Installation Manager to install the following: Web Server Plug-ins for WAS WebSphere Customization Toolbox
6	B	Use Installation Manager to install IBM HTTP Server, or install another supported web server.
7	B	Open the WebSphere Customization Toolbox, and launch the Web Server Plug-ins Configuration Tool to configure the web server plug-in. The script for creating and configuring the web server is created under the plugins_root/bin directory.
8	B	Copy the configureweb_server_name script to paste on 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.
9	A	Paste the configureweb_server_name script from Machine B to the app_server_root/bin directory on Machine A.
10	A	Start the application server.
11	A	Run the script from a command line.
12	A	Verify the application server is running. Open the dmgr console and save the changed configuration.
13	A	Create a secure connection between the web server plug-in and the internal HTTP transport in the application server. This step is required for the web server to function properly. For detailed instructions on creating the secure connection, read the article on configuring the web server plug-in for Secure Sockets Layer.
14	B	Start the web server. Source the plugins_root/setupPluginCfg.sh script for a Domino Web Server before starting a Domino Web Server.
15	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 our own application, regenerate and propagate the plugin-cfg.xml file after installing the application.