Select a Web server topology diagram and roadmap

Select a Web server topology diagram and roadmap

+
Search Tips | Advanced Search

Overview

Install and configure Web server plug-ins for WAS to allow the appserver to communicate with the Web server.
The primary production configuration for a Web server is an appserver on one machine and a Web server on a separate machine. This configuration is referred to as a remote configuration.
The Plug-ins installation wizard can be launched from the launchpad...

The 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 appserver machine.
The wizard processes the creation of the Web server definition differently depending on the scenario:
Stand-alone appserver environments

Recommended remote stand-alone appserver installation:
Creates a configuration script that you run on the appserver machine. Install the Web server and its plug-in on a different machine than the appserver. This configuration is recommended for a production environment.

Local stand-alone appserver installation:
Detects the default profile on a local appserver machine and creates the Web server definition for it directly. Install the Web server and its plug-in on the same machine with the appserver. This configuration is for development and test environments.

Distributed environments (cells)

Recommended remote distributed installation:
Creates a configuration script that you run on the appserver 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.

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 appserver 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 the WAS ND product.
2 A Configure a stand-alone appserver 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...
plugins_root/bin

5 B Copy the configureweb_server_name script to Machine A.
6 A Paste the configureweb_server_name script from Machine B to the app_server_root/bin directory on Machine A.
7 A Start the appserver, then run the script from a command line.
8 A Verify that the appserver is running. Open the console and save the changed configuration.
9 B
Source...
plugins_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

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...
plugins_root/config/web_server_name

To use the actual plugin-cfg.xml file from the appserver, propagate the plugin-cfg.xml file.

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...
profile_root/config/cells/cell_name/nodes/web_server_name_node/servers/web_server_name

...on Machine A. Paste the file into...
plugins_root/config/web_server_name

...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 WAS product.
2 A Create an appserver 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 appserver is running. Open the console and save the changed configuration.
6 B
Run...
plugins_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...
profile_root/config/cells/cell_name/nodes/web_server_name_node/servers/web_server_name
The generation occurs when the Web server definition is created.
The local file does not require propagation.

Remote Web server configuration

The remote distributed installation installs the Web server plug-in on the Web server machine when the appserver is on a separate machine, such as shown in the following graphic:

Remote distributed installation scenario

Table 3. Installation and configuration

Step Machine Task

1 A Install WAS ND.
2 A Create a deployment manager profile.
3 A Start the deployment manager with...
profile_root/bin/startManager.sh

...or its Windows equivalent.
4 B Install WAS ND.
5 B Create an appserver profile.
6 B Federate the node with...
profile_root/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...
plugins_root/bin

9 C 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...
plugins_root/bin/crossPlatformScripts

10 A Paste the configureweb_server_name script from Machine C to...
app_server_root/bin

... 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 console of the deployment manager on Machine A to start the appserver on Machine B. Wait for synchronization to occur and save the new configuration.
13 C
Run...
plugins_root/setupPluginCfg.sh

...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
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 C in...
plugins_root/config/web_server_name

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...
profile_root/config/cells/cell_name/nodes/node_name/servers/web_server_name

...on Machine A to...
plugins_root/config/web_server_name

...on Machine C.

Local Web server

A local distributed installation includes the Web server plug-in, the Web server, and the managed appserver on the same machine:

Local distributed installation scenario

Table 4. Installation and configuration

Step Machine Task

1 A Install WAS ND.
2 A Create a deployment manager profile
3 A Start the deployment manager with...
profile_root/bin/startManager.sh

4 B Install WAS ND.
5 B Create an appserver profile.
6 B Federate the node with...
profile_root/bin/addNode.sh dmgrhost 8879 -includeapps
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...
plugins_root/bin

11 B After verifying that the deployment manager and the node agent are running on Machine A, run the configureweb_server_name script from a command line in...
plugins_root/bin

...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 console of the deployment manager on Machine A to start the appserver on Machine B. Wait for synchronization to occur and save the new configuration.
13 B
Run...
plugins_root/setupPluginCfg.sh
...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.
During the installation of the plug-ins, the temporary plugin-cfg.xml file is installed on Machine C in...
plugins_root/config/web_server_name

The plugin-cfg.xml file is generated at...
profile_root/config/cells/cell_name/nodes/node_name/servers/webServerName

...when the Web server definition is created.
Regenerate the plugin-cfg.xml file in the Web server definition in the appserver 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, you 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 appserver, and the deployment manager on the same machine:

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.

What to do next

Web server configuration
Plug-ins configuration
Edit Web server configuration files
Installing Web server plug-ins

Web server plug-in properties
Web server plug-ins
Installing Web server plug-ins

Step	Machine	Task
1	A	Install the WAS ND product.
2	A	Configure a stand-alone appserver 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... plugins_root/bin
5	B	Copy the configureweb_server_name script to Machine A.
6	A	Paste the configureweb_server_name script from Machine B to the app_server_root/bin directory on Machine A.
7	A	Start the appserver, then run the script from a command line.
8	A	Verify that the appserver is running. Open the console and save the changed configuration.
9	B	Source... plugins_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 appserver 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 appserver is running. Open the console and save the changed configuration.
6	B	Run... plugins_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 ND.
2	A	Create a deployment manager profile.
3	A	Start the deployment manager with... profile_root/bin/startManager.sh ...or its Windows equivalent.
4	B	Install WAS ND.
5	B	Create an appserver profile.
6	B	Federate the node with... profile_root/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... plugins_root/bin
9	C	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... plugins_root/bin/crossPlatformScripts
10	A	Paste the configureweb_server_name script from Machine C to... app_server_root/bin ... 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 console of the deployment manager on Machine A to start the appserver on Machine B. Wait for synchronization to occur and save the new configuration.
13	C	Run... plugins_root/setupPluginCfg.sh ...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 ND.
2	A	Create a deployment manager profile
3	A	Start the deployment manager with... profile_root/bin/startManager.sh
4	B	Install WAS ND.
5	B	Create an appserver profile.
6	B	Federate the node with... profile_root/bin/addNode.sh dmgrhost 8879 -includeapps 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... plugins_root/bin
11	B	After verifying that the deployment manager and the node agent are running on Machine A, run the configureweb_server_name script from a command line in... plugins_root/bin ...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 console of the deployment manager on Machine A to start the appserver on Machine B. Wait for synchronization to occur and save the new configuration.
13	B	Run... plugins_root/setupPluginCfg.sh ...for a Domino Web Server before starting a Domino Web server. Otherwise, start the Web server.
14	B	Run the Snoop servlet.