Prepare a remote Web server when portal is installed on Linux
Configure the Web server plug-in, bundled with IBM WAS, to set up your Web server to communicate with WebSphere Portal.
Prerequisites
- Prepare the WAS Deployment Manager on Linux
- Prepare prerequisite and corequisite software on Linux
- Prepare the Linux operating system
- Prepare the primary node on Linux
Install your Web server
- Configure the Web server.
- If using Lotus Domino, edit NOTES.INI on the Web server and set...
HTTPEnableConnectorHeaders parameter to 1
- 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.
- Stop the Web server.
- Configure the Web server plug-in on the system where the Web server is located using the WAS Plug-ins installation wizard.
The WAS Web server instructions are for the default profile. You can configure a Web server for a non-default profile.
If using WebDAV, after installing the Web server plug-in, edit plugin-cfg.xml file 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 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 an appropriate value.
- Start the Web server.
Parent topic:
Prepare prerequisite and corequisite software on Linux
Previous topic:
Prepare the WAS Deployment Manager on Linux
Parent topic:
Set up a cluster on Linux
Previous topic:
Choose the type of cluster to create on Linux
Next topic:
Configure WebSphere Portal to use a user registry on Linux in a clustered environment