Prepare a remote web server

Install and configure the web server plug-in. The IBM WebSphere Application Server provides the plug-in. Configure the web server to communicate with HCL WebSphere Portal.

1. Install and configure the web server.

   IBM HTTP Server or Apache Server, edit the httpd.conf file on the web server. Set the AllowEncodedSlashes directive to On. Add the directive to the root level as a global directive.

   IIS: For a Microsoft Internet Information Server, set the UrlSegmentMaxLength registry key to 0. This eliminates potential problems HCL WebSphere Portals's limitation on the length of URL path segments. Set the AllowRestrictedChars registry key to 1. This accepts hex-escaped characters in request URLs that decode to the U+0000 - U+001F and U+007F - U+009F ranges.

   HCL Domino: Edit the NOTES.INI file on the web server. Set the HTTPEnableConnectorHeaders and HTTPAllowDecodedUrlPercent parameters to 1. Also, if we are using WebDAV, enable it in the Domino web server administrative console.

   Dynamic cluster: If we are creating a dynamic cluster environment, install and configure an OnDemand Router (ODR).

2. Stop the web server.
3. Install and configure the web server plug-in.

   Set the ServerIOTimeout parameter in plugin-cfg.html. Set to how long the plug-in must wait for a response from the application. The minimum value is 60. Increase if we are retrieving data from a database.

4. Web 2.0 REST features in portal might require an enabled PUT and DELETE method. If your web server has these methods disabled, complete one of the following options:

   • Enable HTTP tunneling to simulate PUT and DELETE requests, which means that POST requests are used instead. See the "Switch for tunneling of HTTP methods" link for information.

   • Follow the instructions for your web server to enable PUT and DELETE requests.

5. Start the web server.
6. To use the Web Application Bridge:

   1. Log on to the WebSphere Integrated Solutions Console and go to...
      Applications > Application Types > WebSphere enterprise applications > wp.vwat.servlet.ear > Web Module Properties heading > Context Root For Web Modules

      ...and set context root to /. This step can create name conflicts. Add a rewrite rule to avoid these conflicts. SeeApache Module mod_rewrite and Providing short vanity URLs.

   2. Click OK.

   3. Click Save to save your changes to the master configuration.

   4. Stop and restart the wp.vwat.servlet.ear application.

7. Optional: To use the short version of vanity URLs, add a rewrite rule to your web server. For more information, read Providing short vanity URLs in our product base documentation here.

See also

1. IBM HTTP Server
2. Apache AllowEncodedSlashes directives

Parent topic: Install the prerequisite software