Prepare a remote web server
Install and configure the web server plug-in. The IBM WAS provides the plug-in. Configure the web server to communicate with IBM WebSphere Portal.
- Install and configure the web server. Refer to the web server documentation for information.
Dynamic cluster: If we are creating a dynamic cluster environment, install and configure an OnDemand Router (ODR). Go to Create ODRs for information.
- If we are using Microsoft Internet Information Server, update the UrlSegmentMaxLength Registry key. Change it 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. Update 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 Configure Microsoft Internet Information Services (IIS) for information.
Refer to Http.sys registry settings for IIS for information.
- If we are using IBM 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.
- If we are using 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.
HTTP server type Documentation link Read the appropriate HTTP Server documentation IBM HTTP Server Read the appropriate Apache Server documentation AllowEncodedSlashes directives
- Stop the web server.
- Install and configure the web server plug-in on the system where the web server is located. Use the plug-ins installation wizard provided with WAS. Refer to the following topic for information:
- AIX HP-UXIBM i: LinuxSolarisWindows: Select a Web server topology diagram and road map
Depending on how we use the web server, we must adjust the ServerIOTimeout parameter. It defines how long the plug-in must wait for a response from the application. The minimum value is 60 but we must increase this value if we are retrieving data from a database. To update this value, locate and open plugin-cfg.xml and set ServerIOTimeout to an appropriate value.
- For an Oracle iPlanet web server, some portlets require disabling the unix-uri-clean or nt-uri-clean directives. Edit the obj.conf file to enable or disable these directives. Refer to the Oracle iPlanet web server documentation to determine the appropriate setting for the environment.
If we are using Oracle iPlanet web server v7, disable uri-clean.
- Web 2.0 REST features in portal might require an enabled PUT and DELETE method. If the 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 the web server to enable PUT and DELETE requests.
- Start the web server.
- Optional: Use the web application bridge feature:
- Log on to the WAS console.
- Go to Applications > Application Types > WebSphere enterprise applications.
- Find and click the wp.vwat.servlet.ear application link.
- Under the Web Module Properties heading, click Context Root For Web Modules.
- Change the context root to /. This step can create name conflicts. Add a rewrite rule to avoid these conflicts. For more information read Apache Module mod_rewrite and Provide short vanity URLs.
- Click OK.
- Click Save to save the changes to the master configuration.
- Stop and restart the wp.vwat.servlet.ear application.
- Optional: If we want to use the short version of vanity URLs, add a rewrite rule to the web server. For more information, read Provide short vanity URLs.