Prepare a remote Web server when portal is installed on Windows in a clustered environment

Install and configure the Web server plug-in, provided by IBM WebSphere Application Server, to set up Web server to communicate with IBM WebSphere Portal.

Prerequisites

Prepare the Windows OS
Prepare the primary node on Windows

To install and configure Web server:

1. Install and configure the Web server; refer to the Web server documentation for information.

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. If using IBM Lotus Domino®, edit the NOTES.INI file on the Web server. Set the HTTPEnableConnectorHeaders and HTTPAllowDecodedUrlPercent parameters to 1. If you are using WebDav, enable it in the Lotus Domino Webserver Administrative Console.

4. Stop the Web server.

5. Install and configure the Web server plug-in on the system where the Web server is located using the Plug-ins installation wizard provided with WAS. Refer to Select a Web server topology diagram and roadmap for information.
   For Domino and Oracle iPlanet Web servers: If you plan to use the Page Builder Theme to change page layout, enable WebDAV on Web server side. Please consult with vendor and/or vendor's documentation for more information about how to complete this action. If using WebDAV with mashups or Page Builder: After successfully installing the Web server plug-in, edit plugin-cfg.xml file 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 but you may need to adjust this value higher if you are retrieving data from a database. To update this value, edit plugin-cfg.xml file See Common questions about the Web server plug-in.

6. If you are using a Oracle iPlanet Web Server, some portlets require that you disable the unix-uri-clean or nt-uri-clean directives to operate properly. You can enable/disable these directives by editing obj.conf.
   If you are using Oracle iPlanet Web Server v7. disable uri-clean.

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

8. 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 Web server has these methods disabled, perform 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 below for information.

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

9. Start the Web server.

10. Access the Web Content Manager content through an external Web server:

    1. Log on to the dmgr console.

    2. Select Environment -> WebSphere Variables.

    3. From the Scope drop-down menu, select the Node=nodename, Server=servername option to narrow the scope of the listed variables, where Node=nodename is the node that contains the application server.

    4. Update the WCM_HOST variable with the fully qualified host name used to access the WebSphere Portal server through the Web server or On Demand Router.

    5. Update the WCM_PORT variable with the port number used to access the WebSphere Portal server through the Web server or On Demand Router.

    6. To synchronize the node with the dmgr:

       1. Select System Administration -> Nodes.

       2. Select the node that you want to synchronize from the list.

       3. Click Full Resynchronize.

    7. Log off of the dmgr console.

11. If you have a dynamic cluster and you are using a Web server to connect to the On Demand Router (ODR), configure the web server as a trusted proxy on the ODR. Refer to Configure a Web server as a trusted proxy server for instructions.
    You can also configure the ODR to dynamically update the Web server configuration when changes occur. Refer to Configure an on demand router to dynamically update the Web server plug-in configuration for instructions.

Parent

Set up a cluster on Windows

Previous

Prepare to create the cluster on Windows

Next topic

Configure WebSphere Portal to use a user registry on Windows in a clustered environment
Switch for tunneling of HTTP methods

+

Search Tips   |   Advanced Search