Chapter 12. Configuring and managing web servers 425
– Web Server Plug-ins for IBM WebSphere Application Server
Click Next.
6. Read and accept the license agreement. Click Next.
7. Select the installation directory for each package. You can keep the default paths or
update them to suit your environment. Click Next.
8. On the Features window, verify the selected packages, and click Next.
9. Configure a port number for the IBM HTTP Server to communicate. Keep the default port
80 or modify to a port number that is not in use. Click Next.
10.Review the settings on the Summary window, and click Install.
11.When the installation is complete, review the summary, and click Finish. It is also a best
practice to view the log file to verify that the installation was successful.
After installation of the web server and web server plug-in, you need to configure the web
server plug-in. To configure the plug-in, the stand-alone WebSphere Customization Toolbox
offering must be installed. You can find more information about the stand-alone WebSphere
Customization Toolbox offering in 2.6.1, “WebSphere Customization Toolbox” on page 52.
12.3 Web server configuration using the WebSphere
Customization Toolbox
After installing the web server plug-in, you must configure it. A new tool in WebSphere
Application Server V8.5 is the Web Server Plug-in Configuration Tool in the WebSphere
Customization Toolbox (WCT), which is used for configuring web server plug-ins. The Web
Server Plug-in Configuration Tool creates one or more configurations for the web server
plug-ins that can direct requests from a web client through the web server and then interact
with applications running on an application server. The Web Server Plug-in Configuration Tool
edits the configuration file or files for a web server by creating directives that point to the
location of the binary plug-in module and the plug-in configuration file.
Before configuring the plug-in, determine the topology set up. The options for defining and
managing web servers depend on your chosen web server topology and your WebSphere
Application Server package. Decisions to make include whether to collocate the web server
with other WebSphere Application Server processes and whether to make the web server
managed or unmanaged.
The following examples outline the process required to create each sample topology. Note
that each example assumes that only the WebSphere processes shown in the diagrams are
installed on each system and that the profile for the process is the default profile.
This section is not a substitute for using the product documentation but is intended to help
you understand the process. For detailed information about how to complete a local or remote
installation scenario, see the Web Server Plug-in Installation Roadmaps for WebSphere
Application Server Network Deployment Version 8.0 guide that comes with the plug-in. You
can also find this information at the following website:
http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%2Fcom.ibm.webspher
e.nd.multiplatform.doc%2Fae%2Ftins_road_plugins.html