Prepare a remote Web server when portal is installed on Linux in a clustered environment
- Prerequisites
- Prepare the Linux operating system in a clustered environment
- Prepare the primary node on Linux
- Create and augment a new dmgr profile on Linux
Configure the Web server
- Install and configure the Web server;
- 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.
- 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
- 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.
See the "Switch for tunneling of HTTP methods" link for information.
- Enable PUT and DELETE requests.
- Start the Web server.
- To use the Web application bridge feature:
- Log on to the WAS admin console.
- Go to Applications > Application Types > WebSphere enterprise applications.
- Find and click wp.vwat.servlet.ear link.
- Under the Web Module Properties heading, click Context Root For Web Modules.
- Change the context root to /.
- Click OK.
- Click Save to save the changes to the master configuration.
- Stop and restart wp.vwat.servlet.ear.
- To access the WCM content through an external web server:
- Log on to the dmgr console.
- Select Environment > WebSphere Variables.
- From the Scope drop-down menu, select the option...
Node=nodename, Server=servername
...where Node=nodename is the node containing the portal application server.
- 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:
- Select System Administration > Nodes.
- Select the node to synchronize from the list.
- Click 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 Linux
Previous: Prepare to create the cluster on Linux
Next: Configure WebSphere Portal to use a user registry on Linux in a clustered environment
Related reference:
Switch for tunneling of HTTP methods