Plan to install Web server plug-ins
Before you begin
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.
Overview
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.
Web server plug-in installation for stand-alone application server environments
- 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.
Web server plug-in installation for distributed environments (cells)
- Recommended 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.
Set up a remote Web server installation.
Step Machine Task 1 A Install your WAS product. 2 A Create an 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/bin5 B 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 the directory... plug-ins_install_root/bin/crossPlatformScripts6 A Paste the configureWeb_servername script from Machine B to the directory... was_install_root/bin...on Machine A.
7 A 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 Run...
cd plug-ins_install_root/setupPluginCfg.sh...for a Domino Web Server before starting a Domino Web server. Otherwise, start the 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_serverThe 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 the directory...
profiles/config/cells/cell/nodes/Web_servername_node/servers/web_server...on Machine A. Paste the file into the directory...
plug-ins_install_root/config/web_server...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
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. Otherwise, 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 the directory...
profiles/profile/config/cells/cell/nodes/Web_servername_node/servers/web_serverThe generation occurs when the Web server definition is created.
The local file does not require propagation.
Set up a remote Web server installation in a cell.
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
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/ profile/bin/startManager.sh4 B Install WAS Network Deployment. 5 B Create an application server profile. 6 B Federate the node... cd ./Profiles/profile/bin/
addNode.sh dmgrhost 8879 -includeapps7 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...
plug-ins_install_root/bin9 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 the directory...
plug-ins_install_root/bin/crossPlatformScripts10 A Paste the configureWeb_servername script from Machine C to the directory... was_install_root/bin...on Machine A.
11 A Run the script from a command line after verifying that the deployment manager is running. 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...
plug-ins_install_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
During the installation of the plug-ins, the temporary plugin-cfg.xml file is installed on Machine C in the directory...
plug-ins_install_root/config/web_serverThe 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 the directory...
profiles/profile/config/cells/cell/ nodes/ node/ servers/ web_server...on Machine A to...
plug-ins_install_root/config/web_server...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
Table 1. Installation and configuration Step Machine Task 1 A Install WAS Network Deployment. 2 A Create a deployment manager profile. 3 A Start the deployment manager... cd profiles/profile/bin/
startManager.sh4 B Install WAS Network Deployment. 5 B Create an application server profile. 6 B Federate the node... cd ./profiles/profile/bin
addNode.sh dmgrhost 8879 -includeapps7 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...
plug-ins_install_root/bin11 B After verifying that the deployment manager is running on Machine A, run the configureWeb_servername script from a command line in the directory... plug-ins_install_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 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...
plug-ins_install_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.
The plugin-cfg.xml file is generated into the directory...
profiles/profile/config/cells/cell/nodes/node/servers/web_server...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
- Configuration behavior of the Plug-ins installation wizard
- Editing Web server configuration files
- Installing Web server plug-ins
- Web server plug-ins
- Web server plug-in properties settings