Update web addresses in IBM HTTP Server 

Update the web addresses that IBM HTTP Server uses to access IBM Connections applications.


Before starting


If you installed and configured IBM HTTP Server before installing IBM Connections, your IBM Connections applications are automatically mapped to the web server. However, if you installed and configured IBM HTTP Server after installing IBM Connections, you need to manually map the applications.  Before continuing with this task, map the application modules to IBM HTTP Server. For more information, see the Mapping applications to IBM HTTP Server topic.
If you are using the Files or Wikis applications, configure IBM HTTP Server to handle file downloads from those applications. For more information, see the Configure Files and Wikis downloading topic.

If you choose to let the WAS redirect servlet manage file downloading, configure the server to transfer data synchronously instead of asynchronously. This configuration helps avoid errors caused by using too much memory. See the Excessive native memory use in IBM WAS tech note for instructions.


About this task


If you do not install a web server such as IBM HTTP Server, users must include the correct port number in the web address that they use to access the application. When you use a webserver, users can access the applications without using port numbers.

By default, the web address that you enter to access IBM Connections applications includes the port number for each application. To avoid using port numbers, update the web addresses by editing the LotusConnections-config.xml file. IBM HTTP Server can then redirect requests to the appropriate port for each application.

For more information about editing configuration files, see the Edit configuration files topic.

To update the web addresses to your IBM Connections applications...


Procedure

  1. Stop WAS.

  2. Check out the LotusConnections-config.xml file. The file is stored by default in the following directory:

    • AIX : /usr/IBM/WebSphere/AppServer/profiles/<profile_name>/config/cells/<cell_name>/LotusConnections-config

    • Linux™: /opt/IBM/WebSphere/AppServer/profiles/<profile_name>/config/cells/<cell_name>/LotusConnections-config

    • Windows™: C:\IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\LotusConnections-config

  3. Update the web addresses specified in the href and ssl_href properties for each application:

      <sloc:serviceReference enabled="true"
      serviceName="<application>" ssl_enabled="true"> <sloc:static href="http://<webserver>" ssl_href="https://<webserver>"> <sloc:interService href="https://<webserver>">

      where <webserver> is the address of your IBM HTTP Server and <application> is the name of an IBM Connections application.

      Note:

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

      For example, to update the web address for Activities, edit the file in the following way:

      <sloc:serviceReference enabled="true" 
      person_card_service_name_js_eval= "generalrs.label_personcard_activitieslink" person_card_service_url_pattern= "/service/html/mainpage#dashboard%2Cmyactivities %2Cuserid%3D{userid}%2Cname%3D{displayName}" serviceName="activities" ssl_enabled="true"> <sloc:href> <sloc:hrefPathPrefix>/activities </sloc:hrefPathPrefix> <sloc:static href="http://<webserver>" ssl_href="https://<webserver>"> <sloc:interService href="https://<webserver>"> </sloc:href> </sloc:serviceReference>

      Note: If you plan to use a reverse proxy, the web addresses defined in this file must be updated to reflect the appropriate proxy server URLs. Go to the IBM Connections wiki for more information about deployment scenarios, including how to configure a reverse proxy.

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

  5. Synchronize the nodes.

  6. Log into each application to ensure that the web address links for the applications in the navigation bar have been updated.

Results


You can access each application without needing to specify a port number.


Parent topic

Configure IBM HTTP Server
Previous topic: Determining which files to compress


Related tasks


Configure IBM HTTP Server for SSL
IBM Connections wiki
Edit configuration files

+

Search Tips   |   Advanced Search