Select a Web server topology diagram and roadmap

Select a Web server topology diagram and roadmap

+
Search Tips | Advanced Search

Overview

This topic helps you use the Plug-ins installation wizard to install Web server plug-ins for WAS.
The primary production configuration 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 Plug-ins installation wizard has four main tasks:

Install the binary plug-in module on the Web server machine.
Configure the Web server config file (httpd.conf) on the Web server machine to point to the binary plug-in module and to the XML configuration file for the binary module.
Install a temporary XML configuration file for the binary module (plugin-cfg.xml) on the Web server machine in remote scenarios.
Create 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:

Web server plug-in installation for stand-alone application server environments

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.

Web server plug-in installation for distributed environments (cells)

Remote distributed 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 deployment manager or managed node. This configuration is recommended for a production environment.
Local distributed installation:
Creates a configuration script that you run when the deployment manager is running. Install the Web server and its plug-in on the same machine with the deployment manager or a managed node. This configuration is for development and test environments.

Steps for this task (dependent on configuration)

Set up a remote Web server installation.

The remote installation installs the Web server plug-in on the Web server machine when the application server is on a separate machine...

Remote installation scenario

Step Machine Task
1 A Install the WAS Network Deployment product.
2 A Configure a stand-alone application server profile.
3 B Install IBM HTTP Server or another supported Web server.
4 B Install the binary plug-in module using the Plug-ins installation wizard.
The script for creating and configuring the Web server is created under...
plug-ins_install_root/bin

5 B Copy the configureWeb_servername script to Machine A.
6 A Paste the configureWeb_servername script from Machine B to...
was_install_root/bin

...on Machine A.
7 A Start the application server, then run the script from a command line.
8 A Verify that the application server is running. Open the administrative console and save the changed configuration.
9 B Source...
plug-ins_install_root/setupPluginCfg.sh

...for a Domino Web Server before starting a Domino Web server. Otherwise, start the supported Web server.
10 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

During the installation of the plug-ins, the temporary plugin-cfg.xml file is installed on Machine B in...
plug-ins_install_root/config/web_servername

The Web server plug-in configuration service regenerates the plugin-cfg.xml file automatically.
To use the real 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...
profiles_install_root/config/cells/cell/nodes/Web_servername_node/servers/web_servername

...on Machine A. Paste the file into ...
plug-ins_install_root/config/web_servername

...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

Step Machine Task
1 A Install your WAS product.
2 A Create an application server profile.
3 A Install IBM HTTP Server or another supported Web server.
4 A Install the binary plug-in module using the Plug-ins installation wizard.
The Web server definition is automatically created and configured during the installation of the plug-ins.
5 A Verify that the application server is running. Open the administrative console and save the changed configuration.
6 B
Run...
plug-ins_install_root/setupPluginCfg.sh

...for a Domino Web Server before starting a Domino Web server.
Start the Web server.
7 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.
The plugin-cfg.xml file is generated in...
profiles_install_root/profile/config/cells/cell/nodes/Web_servername_node/servers/web_servername
The generation occurs when the Web server definition is created.
Propagation of the plugin-cfg.xml file
The local file does not require propagation.

Set up a remote Web server installation in a cell.

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

Step Machine Task
1 A Install WAS Network Deployment.
2 A Create a deployment manager profile.
3 A Start the deployment manager using...
./profiles_install_root/profile/bin/startManager.sh

4 B Install WAS Network Deployment.
5 B Create an application server profile.
6 B Federate the node...
cd ./profiles_install_root/profile/bin/
addNode.sh dmgrhost 8879 -includeapps

Federating the node starts the nodeagent process, which is required to be running during this configuration.
7 C Install IBM HTTP Server or another supported Web server.
8 C Install the binary plug-in module using the Plug-ins installation wizard.
The script for creating and configuring the Web server is created under the plug-ins_install_root/bin directory.
9 C Copy the configureWeb_servername script to Machine A.
If one machine is running under Linux or UNIX and the other machine is running under Windows, copy the script from...
plug-ins_install_root bin/crossPlatformScripts

10 A Paste the configureWeb_servername script from Machine C to the was_install_root/bin directory on Machine A.
11 A Start the node agent and the deployment manager if they are not already running, then run the script from a command line.
If you have enabled security or changed the default JMX connector type, edit the script and include the appropriate parameters on the wsadmin command.
12 A/B Use the administrative console of the deployment manager on Machine A to start the application server on Machine B. Wait for synchronization to occur and save the new configuration.
13 C
Run the plug-ins_install_root/setupPluginCfg.sh script for a Domino Web Server before starting a Domino Web server. Otherwise, start the Web server.
14 C 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

During the installation of the plug-ins, the temporary plugin-cfg.xml file is installed on Machine C in...
plug-ins_install_root/config/web_servername

The Web server plug-in configuration service regenerates the plugin-cfg.xml file automatically.
To use the real 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, by manually copying the plugin-cfg.xml file from...
profiles_install_root/profile/config/cells/cell/nodes/node/servers web_servername

...on Machine A to...
plug-ins_install_root/config/web_servername

...on Machine C.

Set up a local distributed Web server configuration.

The local Web server configuration is recommended for a development or test environment.
A local distributed installation includes the Web server plug-in, the Web server, and the managed application server on the same machine:

Local distributed installation scenario

Step Machine Task
1 A Install WAS Network Deployment.
2 A Create a deployment manager profile.
3 A Start the deployment manager with the command...
profiles_install_root/profile/bin/startManager.sh

4 B Install WAS Network Deployment.
5 B Create an application server profile.
6 B Federate the node...
cd ./profiles_install_root/profile/bin
addNode.sh dmgrhost 8879 -includeapps
equivalent. Federating the node starts the nodeagent process, which is required to be running during this configuration.
7 B Install IBM HTTP Server or another supported Web server.
8 B Install the binary plug-in module using the Plug-ins installation wizard.
The script for creating and configuring the Web server is created in the plug-ins_install_root/bin directory.
11 B After verifying that the deployment manager and the node agent are running on Machine A, run the configureWeb_servername script from a command line in the plug-ins_install_root/bin directory on Machine B.
If you have enabled security or changed the default JMX connector type, edit the script and include the appropriate parameters.
12 A/B Use the administrative console of the deployment manager on Machine A to start the application server on Machine B. Wait for synchronization to occur and save the new configuration.
13 B
Run the plug-ins_install_root/setupPluginCfg.sh script for a Domino Web Server before starting a Domino Web server. Otherwise, start the Web server.
14 B Run the Snoop servlet.

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 at the location...
profiles_install_root/profile/config/cells/cell/nodes/node/servers/web_servername

...when the Web server definition is created.
Regenerate the plugin-cfg.xml file in the Web server definition in the application server whenever the configuration changes. The Web server has immediate access to the file whenever it is regenerated.
When the Web server plug-in configuration service (an administration service) is enabled on Machine A, the plugin-cfg.xml file is automatically generated for all Web servers.

Propagation of the plugin-cfg.xml file

Node synchronization is used to propagate the plugin-cfg.xml file from Machine A to Machine B.
When the Web server plug-in configuration service (an administration service) is enabled on Machine A, the plugin-cfg.xml file is automatically propagated for all Web servers.

Alternate configuration

This procedure describes installing the plug-ins on two machines. However, we can perform this procedure on a single machine as shown in the following graphic. A local distributed installation also includes the Web server plug-in, the Web server, the Application Server, and the deployment manager on the same machine:

Result
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 Also
Web server configuration
Web server plug-ins
Edit Web server configuration files
Web server plug-in properties settings
Configuration behavior of the Plug-ins installation wizard

Step	Machine	Task
1	A	Install the WAS Network Deployment product.
2	A	Configure a stand-alone application server profile.
3	B	Install IBM HTTP Server or another supported Web server.
4	B	Install the binary plug-in module using the Plug-ins installation wizard. The script for creating and configuring the Web server is created under... plug-ins_install_root/bin
5	B	Copy the configureWeb_servername script to Machine A.
6	A	Paste the configureWeb_servername script from Machine B to... was_install_root/bin ...on Machine A.
7	A	Start the application server, then run the script from a command line.
8	A	Verify that the application server is running. Open the administrative console and save the changed configuration.
9	B	Source... plug-ins_install_root/setupPluginCfg.sh ...for a Domino Web Server before starting a Domino Web server. Otherwise, start the supported Web server.
10	B	Run the snoop servlet. To verify with your own application, regenerate and propagate the plugin-cfg.xml file after installing the application.

Step	Machine	Task
1	A	Install your WAS product.
2	A	Create an application server profile.
3	A	Install IBM HTTP Server or another supported Web server.
4	A	Install the binary plug-in module using the Plug-ins installation wizard. The Web server definition is automatically created and configured during the installation of the plug-ins.
5	A	Verify that the application server is running. Open the administrative console and save the changed configuration.
6	B	Run... plug-ins_install_root/setupPluginCfg.sh ...for a Domino Web Server before starting a Domino Web server. Start the Web server.
7	B	Run the Snoop servlet. To verify with your own application, regenerate and propagate the plugin-cfg.xml file after installing the application.

Step	Machine	Task
1	A	Install WAS Network Deployment.
2	A	Create a deployment manager profile.
3	A	Start the deployment manager using... ./profiles_install_root/profile/bin/startManager.sh
4	B	Install WAS Network Deployment.
5	B	Create an application server profile.
6	B	Federate the node... cd ./profiles_install_root/profile/bin/ addNode.sh dmgrhost 8879 -includeapps Federating the node starts the nodeagent process, which is required to be running during this configuration.
7	C	Install IBM HTTP Server or another supported Web server.
8	C	Install the binary plug-in module using the Plug-ins installation wizard. The script for creating and configuring the Web server is created under the plug-ins_install_root/bin directory.
9	C	Copy the configureWeb_servername script to Machine A. If one machine is running under Linux or UNIX and the other machine is running under Windows, copy the script from... plug-ins_install_root bin/crossPlatformScripts
10	A	Paste the configureWeb_servername script from Machine C to the was_install_root/bin directory on Machine A.
11	A	Start the node agent and the deployment manager if they are not already running, then run the script from a command line. If you have enabled security or changed the default JMX connector type, edit the script and include the appropriate parameters on the wsadmin command.
12	A/B	Use the administrative console of the deployment manager on Machine A to start the application server on Machine B. Wait for synchronization to occur and save the new configuration.
13	C	Run the plug-ins_install_root/setupPluginCfg.sh script for a Domino Web Server before starting a Domino Web server. Otherwise, start the Web server.
14	C	Run the Snoop servlet. To verify with your own application, regenerate and propagate the plugin-cfg.xml file after installing the application.

Step	Machine	Task
1	A	Install WAS Network Deployment.
2	A	Create a deployment manager profile.
3	A	Start the deployment manager with the command... profiles_install_root/profile/bin/startManager.sh
4	B	Install WAS Network Deployment.
5	B	Create an application server profile.
6	B	Federate the node... cd ./profiles_install_root/profile/bin addNode.sh dmgrhost 8879 -includeapps equivalent. Federating the node starts the nodeagent process, which is required to be running during this configuration.
7	B	Install IBM HTTP Server or another supported Web server.
8	B	Install the binary plug-in module using the Plug-ins installation wizard. The script for creating and configuring the Web server is created in the plug-ins_install_root/bin directory.
11	B	After verifying that the deployment manager and the node agent are running on Machine A, run the configureWeb_servername script from a command line in the plug-ins_install_root/bin directory on Machine B. If you have enabled security or changed the default JMX connector type, edit the script and include the appropriate parameters.
12	A/B	Use the administrative console of the deployment manager on Machine A to start the application server on Machine B. Wait for synchronization to occur and save the new configuration.
13	B	Run the plug-ins_install_root/setupPluginCfg.sh script for a Domino Web Server before starting a Domino Web server. Otherwise, start the Web server.
14	B	Run the Snoop servlet.