Set up a Web server with WebSphere Portal
Set up the Web server to communicate with WebSphere Portal by installing and configuring the Web server plug-in provided by WAS.
- Ensure that the Web server is installed and configured.
- For Microsoft IIS update the value of the UrlSegmentMaxLength key in the registry...
- Open the Registry Editor...
Start | Run | regedit
- Locate the key...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
- Create a value named UrlSegmentMaxLength, with a type of DWORD and a value of 0 to indicate an unbounded length.
- Exit the Registry Editor by clicking...
File | Exit...and then restart Windows.
- For IBM Lotus Domino users, edit the NOTES.INI file on the Web server machine, and ensure that the HTTPEnableConnectorHeaders parameter is set.
HTTPEnableConnectorHeaders=1
- After the Web server is successfully installed and running, stop the Web server.
If you are prompted to install the plugin, say no.
If you installed as a service, to stop, you might need to go into...
Control Panel | Administrative Tools | Services
- Use the Plug-ins installation wizard provided with the WebSphere Application Server install media to install and configure the Web server plug-in on the machine where the Web server is located.
The Plug-ins installation wizard installs the plug-in module, configures the Web server for communication with the application server, and creates a Web server configuration definition in the application server.
To use Lotus Domino V7.0 with WAS, install the Web server plug-in for Domino Server V6.
To use HTTP Server Version 2.0.47.1 with WAS, install the Web server plug-in for HTTP Server V6.
Windows and UNIX only: The Web server instructions provided in the WAS documentation typically act on the default profile. If the WebSphere Portal application server is not the default application server, follow the instructions for a non-default profile.
If the Web server definition is not displaying in the console, cycle the application server. It should show up once the appserver restarts.
If the Web server definition is not automatically created during the plug-in installation, create this definition manually by running the script...
configureweb_servername...on the WAS system or, for a clustered environment, the deployment manager system. The script creates the Web server definitions and changes the target mappings of all enterprise applications deployed in the cell. Synchronize and restart the cluster when running script on a deployment manager system.
Because security is enabled, update the configureweb_servername script file before running the script, and ensure that specify user ID and password used for authentication in the file.
- Restart the Web server.
- Verify that WebSphere Portal is operational with the new Web server configuration
- Configure access to WebSphere Portal through another HTTP port
Web Content Management note
If users need to access content created by Web Content Management through a portal server that is configured to use an HTTP port other than the default internal HTTP port (for example, with a Web server), ensure that required substitution variables are set in the configuration for WAS.
- Log in to the administrative console for WAS. If you are using the Web server in a clustered environment, open the administrative console for the deployment manager machine.
- Select...
Environment | WebSphere Variables | Browse Nodes (Scope field) | NodeName | OK- Select
Environment | WebSphere Variables | Browse Servers (Scope field) | WebSphere_Portal | OK | Apply
- Update the value of the WCM_HOST variable with the fully qualified host name of the Web server.
- Update the value of the WCM_PORT variable with the port number used to access the Web server.
- Restart the portal server.
Parent topic:
Configure Web servers
Related concepts
Web servers and WebSphere Portal