Install
and configure the Web server plug-in, provided by IBM® WebSphere® Application Server, to set up your
Web server to communicate with IBM WebSphere Portal Express®.
- Prerequisites
- Preparing your IBM i operating system in a stand-alone environment
- Installing WebSphere Portal Express on IBM i
- IBM i stand-alone: Preparing DB2 for IBM i
Complete the following
steps to install and configure your Web server:
- Install and configure the Web server;
refer to the Web server documentation for information.
- If using IBM Lotus® Domino®, edit the NOTES.INI file
on the Web server. Set the HTTPEnableConnectorHeaders and HTTPAllowDecodedUrlPercent parameters
to 1. Also, if you are using WebDav, enable
it in the Lotus Domino Webserver
Administrative Console.
- If using IBM HTTP Server or Apache
Server, edit the httpd.conf file on the Web server.
Set the AllowEncodedSlashes directive to On;
the directive should be added at the root level as a global directive.
Table 1. Links to HTTP and Apache server documentation| HTTP server type |
Documentation link |
|---|
| See the appropriate HTTP Server documentation |
IBM HTTP Server |
| See 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 using the Plug-ins
installation wizard provided with WebSphere Application
Server. Refer to Selecting a Web server topology diagram and road
map for information.
If using WebDAV with mashups: After successfully
installing the Web server plug-in, locate and open your plugin-cfg.xml file
and set AcceptAllContent to true.
Important: Depending on how you use the Web
server, 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, locate and open your
plugin-cfg.xml file
and set
ServerIOTimeout to a value that is appropriate
for your business needs. For additional information, see
Common questions about the Web server plug-in.
- 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
the obj.conf file. Refer to the Oracle iPlanet Web Server documentation
to determine the appropriate setting for your environment.
Note: If
you are using Oracle iPlanet Web Server Version
7, you must disable uri-clean.
- If you are using Oracle iPlanet Web Server Version
7 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 your 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 your Web server to enable PUT
and DELETE requests.
- Start the Web server.
- Optional: Complete the following steps if you
plan to use the Web application bridge integration feature:
- Log on to the WebSphere Integrated Solutions Console.
- Go to .
- 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 /.
- Click OK.
- Click Save to save your changes
to the master configuration.
- Stop and restart the wp.vwat.servlet.ear application.