+

Search Tips   |   Advanced Search

Windows stand-alone: Prepare a remote Web server



Configure the Web server

  1. Install and configure the Web server;

  2. If using Microsoft Internet Information Server, we recommend updating the UrlSegmentMaxLength Registry key to a value of 0 to eliminate potential problems in a WebSphere Portal environment with the default IIS limitation on the length of URL path segments. We also recommend updating the AllowRestrictedChars Registry key to a value of 1 to accept hex-escaped characters in request URLs that decode to the U+0000 - U+001F and U+007F - U+009F ranges.

    Refer to Http.sys registry settings for IIS for information.

  3. For Lotus Domino...

    • Edit notes.ini on the Web server
    • Set HTTPEnableConnectorHeaders and HTTPAllowDecodedUrlPercent to 1

    If we are using WebDav, enable it in the Lotus Domino Webserver Administrative Console.

  4. For IHS or Apache Server, edit httpd.conf. Set AllowEncodedSlashes to On; the directive should be added at the root level as a global directive.

    HTTP server type Documentation link
    HTTP Server IBM HTTP Server
    Apache Server AllowEncodedSlashes directives

  5. Stop the Web server.

  6. Install and configure the Web server plug-in

    If using WebDAV with mashups: After installing the Web server plug-in, edit plugin-cfg.xml and set AcceptAllContent to true.

    You may need to adjust the ServerIOTimeout value, which defines how long the plug-in should wait for a response from the application. The recommended minimum value is 60. Adjust higher if we are retrieving data from a database. To update, edit plugin-cfg.xml and set ServerIOTimeout . See Common questions about the Web server plug-in.

  7. If we are using a Oracle iPlanet Web Server, some portlets require disabling the unix-uri-clean or nt-uri-clean directives to operate properly. We can enable/disable these directives by editing obj.conf.

    If we are using Oracle iPlanet Web Server v7, disable uri-clean.

  8. If we are using Oracle iPlanet Web Server v7 update 8, read Technote 1448262 and complete the steps to resolve the HTTP 408/409 error.

  9. Some features, such as portal mashups and change layout for pages with the Page Builder theme using an IIS web server, require an enabled PUT and DELETE method. If the Web server has these methods disabled:

    • 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.

    • Enable PUT and DELETE requests.

  10. Start the Web server.

  11. To use the Web application bridge feature:

    1. Log on to the WAS admin console.

    2. Go to Applications > Application Types > WebSphere enterprise applications.

    3. Find and click wp.vwat.servlet.ear link.

    4. Under the Web Module Properties heading, click Context Root For Web Modules.

    5. Change the context root to /.

    6. Click OK.

    7. Click Save to save the changes to the master configuration.

    8. Stop and restart wp.vwat.servlet.ear.


Parent: Set up a stand-alone production server on Windows
Previous: Windows stand-alone: Configure the portal to use a database
Next: Windows stand-alone: Configure Portal to use a user registry
Related reference:
Switch for tunneling of HTTP methods