Prepare a remote Web server when portal is installed on Windows in a clustered environment
- Prerequisites
- Prepare the Windows operating system in a clustered environment
- Prepare the primary node on Windows
- Create and augment a new dmgr profile on Windows
Configure the Web server
- Install and configure the Web server;
- 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.
- 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.
- Stop the Web server.
- 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.
- 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.
- 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.
- 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.
- Enable PUT and DELETE requests.
- Start the Web server.
- To use the Web application bridge feature:
- Log on to the WAS admin console and select...
Applications | Application Types | WebSphere enterprise applications | wp.vwat.servlet.ear | Web Module Properties | Context Root For Web Modules
...and change the context root to /.
- Save your change, then restart wp.vwat.servlet.ear.
- To access WCM content through an external web server:
- Log on to the dmgr console and select...
Environment | WebSphere Variables
- From the Scope drop-down menu, select...
Node=nodename, Server=servername
- Update the WCM_HOST variable with the fully qualified host name used to access the portal server through the web server or On Demand Router.
- Update the WCM_PORT variable with the port number used to access the portal server through the web server or On Demand Router.
- Update the WCM_HOST and WCM_PORT variable for each additional portal server that already exists in the cluster.
- Synchronize the node with the dmgr:
System Administration | Nodes | node | Full Resynchronize
- Log off of the dmgr console.
- If you have a dynamic cluster and we are using a web server to connect to the On Demand Router (ODR), configure the web server as a trusted proxy on the ODR.
We can also configure the ODR to dynamically update the web server configuration when changes occur.
Parent: Set up a cluster on Windows
Previous: Prepare to create the cluster on Windows
Next: Configure WebSphere Portal to use a user registry on Windows in a clustered environment
Related reference:
Switch for tunneling of HTTP methods