Update IBM Connections to use the HTTP server

Overview

If we installed IBM HTTP Server after installing IBM Connections,, the Connections applications are automatically mapped to the web server. However, if you installed and configured IHS before installing IBM Connections, manually map the applications.

For the Files, Wikis, or Libraries applications, configure IHS to handle file downloads from those applications.

If we do not install a web server IHS, users must include the correct port number in the web address they use to access the application. When using a web server, users can access the applications without using port numbers.

By default, the web address entered to access Connections applications includes the port number for each application. To avoid using port numbers, update the web addresses by editing LotusConnections-config.xml. IHS can then redirect requests to the appropriate port for each application.

Update the web addresses to the Connections applications

1. Stop WebSphere Application Server.

2. Check out LotusConnections-config.xml

   The file is stored by default in...

   /usr/IBM/WebSphere/AppServer/profiles/profile_name/config/cells/cell/LotusConnections-config

3. For each application, update the web addresses specified in the href and ssl_href properties:

   <sloc:href>
       <sloc:hrefPathPrefix>/application</sloc:hrefPathPrefix> 
       <sloc:static href="http://webserver:port" ssl_href="https://webserver:port"> 
       <sloc:interService href="https://webserver:port"> 
   </sloc:href>
   

   where

   • webserver is the domain name of IHS, such as webhost.myco.com
   • port is the default port number of the application. Remove the port number when we specify a web server.
   • application is the name of a Connections application.

   Each href attribute in LotusConnections-config.xml is case-sensitive and must specify a fully-qualified domain name.

   For example, to update the web address for Communities, add the following specifications to the file:

   <sloc:href> 
       <sloc:hrefPathPrefix>/communities</sloc:hrefPathPrefix> 
       <sloc:static href="http://webhost.myco.com ssl_href="https://webhost.myco.com> 
       <sloc:interService href="https://webhost.myco.com> 
   </sloc:href>
   

   To use a reverse proxy, update the web addresses to match the appropriate proxy server URLs.

4. Save and check in LotusConnections-config.xml.

5. Synchronize the nodes.

6. Log on to each application to ensure the web addresses in the navigation bar are correct.

7. If we have deployed IBM Connections Content Manager, update FileNet Collaboration Services to use the new URL.

Parent topic:
Configure IHS

Previous topic: Determine which files to compress

Related:
Connections wiki
Reconfigure FileNet Collaboration Services to support changes to Connections Content Manager