+

Search Tips   |   Advanced Search


Prepare a remote Web server when portal is installed on Solaris

Configure the Web server plug-in, bundled with IBM WAS, to set up your Web server to communicate with WebSphere Portal.


Prerequisites

Configure databases
Perform the following steps to install your Web server:

  1. Configure the Web server; refer to the Web server documentation.

  2. If using Lotus Domino, edit the NOTES.INI file on the Web server. Set the HTTPEnableConnectorHeaders parameter to 1.

  3. If using IBM HTTP Server or Apache Server, edit httpd.conf on the Web server. For Apache, set the AllowEncodedSlashes directive to On; the directive should be added at the root level as a global directive.

    Option Description
    See the appropriate HTTP Server documentation IBM HTTP Server
    See the appropriate Apache Server documentation AllowEncodedSlashes directives

  4. Stop the Web server.

  5. 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.

    The WAS Web server instructions are for the default profile. If not using the default profile, refer to Configure a Web server for a non-default profile.

    If using WebDAV: After successfully installing the Web server plug-in, edit plugin-cfg.xml file and set AcceptAllContent to true.

    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, edit 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.

  6. Start the Web server.


Parent topic:

Set up a stand-alone server on Solaris


Previous topic:

Configure databases


Next topic:

Configure WebSphere Portal to use a user registry on Solaris