Setting up a Web server with Lotus QuickrAdded by IBM on June 11, 2010 | Version 1 (Original)
|Set up your Web server to communicate with IBM® Lotus® Quickr™ for WebSphere Portal by installing and configuring the Web server plug-in provided by IBM WebSphere® Application Server.
Set up your Web server to communicate with IBM® Lotus® Quickr™ for WebSphere Portal by installing and configuring the Web server plug-in provided by IBM WebSphere® Application Server.
By default IBM WebSphere Portal uses the internal HTTP transport within IBM WebSphere Application Server to handle requests. However, because WebSphere Application Server also supports the use of an external Web server, you can access WebSphere Portal from your Web server. You can use a local Web server on the same machine as WebSphere Portal or you can use a remote Web server on a different machine. A remote Web server is typical for a production environment or other high-traffic configuration and is also typically placed in demilitarized zones (DMZ) outside a firewall to protect portal ports.
To enable communication between the Web server and WebSphere Application Server, a Web server plug-in is required. The Web server plug-in determines whether a request is handled by the Web server or by the application server. The plug-in can be installed into a Web server that is located either on the same machine as WebSphere Application Server or on a separate machine. The Web server plug-in uses an XML configuration file (plugin-cfg.xml) that contains settings that describe how to handle and pass on requests to the WebSphere Application Server made accessible through the plug-in.
In the WebSphere Application Server administrative console, the Web server is represented as a specific server type, and you can view or modify all of the configuration properties used in the plugin-cfg.xml file for the Web server plug-in from the administrative console.
- Ensure that the Web server is installed and configured. Refer to the Web server documentation for information.
- Microsoft® Internet Information Server users only: Update the value of the UrlSegmentMaxLength key in the registry. Refer to the INF Httpsys Registry Settings for IIS for details on updating Web server settings in the registry.
Incorrectly editing the registry could severely damage your system, requiring you to reinstall your operating system. Before changing the registry, back up any critical data.
- Open the Registry Editor by clicking Start -> Run and then entering 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.
- Ensure that the plugin-cfg.loc file is located in the same directory as the iisWASPlugin_http.dll or IIS cannot use the dynamic link library.
- Exit the Registry Editor by clicking File -> Exit, and restart the Windows® operating system.
- IBM Lotus Domino® users only: Edit the NOTES.INI file on the Web server machine, and ensure that the HTTPEnableConnectorHeaders parameter is set as HTTPEnableConnectorHeaders=1 and the HTTPAllowDecodedUrlPercent parameter is set as HTTPAllowDecodedUrlPercent=1. Add the following parameter: HTTPEnableMethods=PUT,DELETE
- IBM HTTP Server and Apache Server users only: Edit the httpd.conf file on the Web server machine and ensure that the AllowEncodedSlashes directive is set to On. You must explicitly set AllowEncodedSlashes On in every <VirtualHost> container. For Apache with SSL, set AllowEncodedSlashes On in httpd-ssl.conf.
- IBM EdgeProxy server users only: Edit the ibmproxy.conf file. The default location of this file is C:\\Program Files\\IBM\\edge\\cp\\etc\\en_US. Add the following two lines in the section labeled # For Quickr Admin Console.
- Sun Java System Web Server users only: Edit the obj.conf file on the Web server machine and remove or comment out any lines containing either of the following directives: PathCheck fn=unix-uri-clean PathCheck fn=nt-uri-clean.
See the Sun Java System Web Server documentation for more information about the unix-uri-clean
and the nt-uri-clean
Enable HTTP PUT and DELETE:
- Access the Administration Console.
- Select a server from the list of servers and click Manage.
- Click Restrict Access under the Preferences tab.
- Select Edit from the drop-down list and click OK.
- Select The entire server from the method A table and click Edit Access Control.
- Click the access rights (r-x--i) under the Rights column. The access rights table is displayed on the screen.
- Select WRITE.
- Click Update.
- Click Submit.
- Click Apply then click Apply Changes.
- After the Web server is successfully installed and running, stop the Web server.
- Use the plug-ins installation wizard provided with WebSphere Application Server 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. The plug-in is located on the WAS Extras CD in the q850_extras\\plugin directory.
Refer to the WebSphere Application Server information center for detailed instructions to install the plug-in using the wizard and verify that the Web server is working properly with WebSphere Application Server:
- To use Lotus Domino Version 7.0 with WebSphere Application Server, you must install the Web server plug-in for Domino Server Version 6 which is a part of the Web Server plug-in for WebSphere Application Server Version 6.0.2 or later.
- To use HTTP Server with WebSphere Application Server, you must install and upgrade the HTTP Server and plug-in version to Version 22.214.171.124.
- Windows, Linux, and AIX only: The Web server instructions provided in the WebSphere Application Server documentation typically act on the default profile. If the Lotus Quickr application server is not the default application server, you must follow the instructions for a non-default profile: Configuring a Web server for a nondefault profile
- If the Web server definition is not automatically created during the plug-in installation, you must create this definition manually by running the configureweb_server_name script on the WebSphere Application Server system or, for a clustered environment, the deployment manager system. Because the configureweb_server_name script not only creates the Web server definitions but also changes the target mappings of all enterprise applications deployed in the cell, you must synchronize and restart the cluster when running script on a deployment manager system.
Important: Because security is enabled, if you create this definition manually, you must update the configureweb_server_name script file before running the script, and ensure that you specify the user ID and password used for authentication in the file. The user ID you specify cannot have an embedded blank; a user ID containing a blank causes the script to issue an invalid credentials error.
- If using a Lotus Domino server and you receive the following error:
ws_config_parser: handleLogEnd: Failed to open log file:
- create the log file manually and restart the Lotus Domino server. See the following files for additional information:
- Restart the Web server.
- Ensure that the following required substitution variables are set in the configuration for WebSphere Application Server.
- Log in to the administrative console for WebSphere Application Server. If you are using the Web server in a clustered environment, open the administrative console for the deployment manager machine.
- Select Environment -> WebSphere Variables.
- 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 Lotus Quickr server.CC
- Verify that Lotus Quickr is operational with the new Web server configuration.
A default page is available to use when your Lotus Quickr server is down. This page is located in quickr_server_root\Teamspace\teamspace\unavailable. Configure this page on the HTTP server before copying it over to the Lotus Quickr server. For more information, see the documentation for your HTTP server.
The Secure Socket Layer must be configured to work with the web server.
Parent topic: Configuring Web servers: qp85
Setting up SSL: qp85