This topic helps you use the Plug-ins installation wizard to install Web server plug-ins for WebSphere Application Server. This topic is the information center version of the roadmap that is displayed when you use the Plug-ins installation wizard.
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.Why and when to perform this task
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.
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.
Steps for this task (dependent on configuration)
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 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 plug-ins_install_root/ bin directory. |
4 | B | Copy the configureWeb_server_name 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 plug-ins_install_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 was_install_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 |
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
During the installation of the plug-ins, the temporary plugin-cfg.xml file is installed on Machine B in the plug-ins_install_root/ config/ web_server_name directory.
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 the profiles_install_root/ config/ cells/ cell_name/ nodes/ Web_server_name_node/ servers/ web_server_name directory on Machine A. Paste the file into the plug-ins_install_root/ config/ web_server_name directory on Machine B.
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 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 | B |
|
6 | 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 profiles_install_root/ profile_name/ 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.
Result
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
See Web server configuration for more information about the files involved in configuring a Web server.
See Configuration behavior of the Plug-ins installation wizard for information about the logic behind the processing scenarios for the Plug-ins installation wizard.
See Editing Web server configuration files for information about how the Plug-ins installation wizard configures supported Web servers.
See Installing Web server plug-ins for information about other installation scenarios for installing Web server plug-ins.
Related concepts
Web server plug-ins
Related tasks
Installing Web server plug-ins
Related reference
Web server plug-in properties settings