Tasks Plan for the HTTP server and plug-in
Web server decisions, such as whether to collocate the Web server with other processes, and whether to make the Web server managed or unmanaged, depend on the chosen topology.
installation process includes...
- Installing a supported Web server and the appropriate Web server plug-in
- Defining the Web server to WAS
When installing the IBM HTTP Server shipped with WAS, we now have the option to install the Web server plug-in at the same time. If we choose this option, we will automatically get a remote installation.
The location for the plug-in configuration file is...
IHS_HOME/Plugins/configThe location for the plug-in configuration script is...
IHS_HOME/Plugins/binThe plug-in installer maps all possible configurations to three scenarios...
- LOCAL_STANDALONE
- LOCAL_DISTRIBUTED
- REMOTE
Local standalone
Default unfederated stand-alone profile that has no existing Web server definition.
The Plug-ins Installation Wizard performs the following tasks in this case:
- Creates a Web server definition for the default stand-alone profile
- Configures the Web server to use the plugin-cfg.xml file
If the stand-alone profile is federated, we need to re-create the Web server definition. We can start the Web server and WAS without any manual steps and access the snoop servlet through the Web server to verify that everything is working.
Local distributed
Has the following characteristics:
- A stand-alone profile federated into a dmgr cell.
- A managed node that is either federated or unfederated in a cell.
- A managed profile found after a default dmgr cell detected.
The Plug-ins installation wizard performs the following tasks in this case:
- Does not create a Web server definition for the default distributed profile.
- Configures the Web server to use the plugin-cfg.xml file in the Web server definition directory that the user needs to create manually. We cannot start the Web server until the manual steps are completed.
If the managed node is still not federated, federate the node first. This will avoid the Web server definition being lost after the federation has occurred.
Run the manual Web server definition creation script. Start the Web server and WAS and run the snoop servlet to verify that everything is working.
Remote
Has the following characteristics:
- A remote install type selected by user at install time.
- A default dmgr profile.
- No default profiles detected in the WAS directory given by user.
- A default, unfederated, stand-alone profile with an existing Web server definition.
The plug-ins installation wizard performs the following tasks in this case:
- Does not create a Web server definition for the default distributed profile.
- Configures the Web server to use...
<plugin_root>/config/<webserver_name>/plugin-cfg.xml
What is next?
If DefaultApplication.ear enterprise application is installed, and <plugin_root>/plugin-cfg.xml exists, you can verify functionality by running...
http://<hostname>:<web_server_port>/snoopTo define Web server definition using the script...
- Copy the configuration script to the WAS machine.
- Run the manual Web server definition creation script.
- Copy the generated Web server definition plugin-cfg.xml file back to the Web server machine into the <plugin_root> directory tree. For IBM HTTP Server, we can use the propagation feature.
- Start the Web server and WAS and select the snoop servlet.