Adding a plug-in configuration to a web server

You can configure a web server plug-in to receive an HTTP request for dynamic resources. You can forward the request to the Liberty server, which provides high-availability and workload balancing through the web server plug-in.

Before you begin

  1. Install a supported web server, such as the IBM® HTTP Server that is included with IBM WebSphere® Application Server. See Installing IBM HTTP server . The web server that is provided with IBM i is already installed with product 5761-DG1 for IBM i V6R1 or 5770-DG1 for IBM i V7R1. The IBM i web server is referred to as the IBM HTTP Server for IBM i. The IBM HTTP Server that is provided with WebSphere Application Server does not run on IBM I and is included in WebSphere Application Server for z/OS®, V7 and V8.0. To download the V8.5 HTTP Server, see IBM Ported Tools for z/OS .
  2. Install the web server plug-ins and the WebSphere Customization Toolbox (WCT). To install the web server plug-in, see Installing and configuring web server plug-ins .

    For IBM i platformsFor IBM i, see Installing and configuring web server plug-ins .

    To install the WCT, see Installing and using the WebSphere Customization Toolbox.

    For IBM i platformsFor IBM i and z/OS, install the WCT on your workstation. You do not need to install any of the WCT tools. The Java™ SDK installed with the WCT is used to run the JConsole Java utility in a later step.

About this task

A web server plug-in is used to forward HTTP requests from a supported web server to one or more application servers. The plug-in checks the request against configuration data in the plugin-cfg.xml file. The configuration data maps the URI for the HTTP request to the host name of an application server. The web server plug-in then uses this information to forward the request to the application server.

Procedure

  1. For distributed platformsConfigure the web server plug-in for your chosen web server by using the WCT.
    • When prompted, choose the remote scenario and specify the host name that Liberty is accessible on.
    • Do not copy or run the generated configureWebserver script. This script is not required.
  2. For IBM i platformsConfigure your HTTP server to use the plugin-cfg.xml file.

    Find the location of your current plugin-cfg.xml by finding the value that is specified for the WebSpherePluginConfig directive at the end of the configuration file of the HTTP server. For example, <IHS_ROOT>/conf/httpd.conf.

    Enable the plug-in within the httpd.conf file of the web server by using the LoadModule phrase. Specify the location of plugin-cfg.xml file by using the WebSpherePluginConfig phrase. For example:
    • On Windows systems:For Windows platforms
      LoadModule was_ap22_module "path/to/mod_was_ap22_http.dll"
      WebSpherePluginConfig "C:\Program Files\IBM\HTTPServer\conf\plugin-cfg.xml"
    • On other distributed systems:For AIX platformsFor LINUX platformsFor UNIX platformsFor HP UNIX platformsFor Solaris platforms
      LoadModule was_ap22_module "path/to/mod_was_ap22_http.so"
      WebSpherePluginConfig "/opt/IBM/HTTPServer/conf/plugin-cfg.xml"

    For IBM i platformsFor IBM i and z/OS, see http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=tins_manualWebIHS80 for instructions about enabling the plug-in within the httpd.conf file.

  3. Optional: If you want the web server plug-in to forward HTTP requests to more than one Liberty server, repeat the previous steps for each additional server. Consolidate all the plug-in configurations into one plugin-cfg.xml file.

    To merge plug-in configurations, you can use one of the following tools:


Icon that indicates the type of topic Task topic

File name: twlp_admin_webserver_plugin.html