Home

 

Map features to IBM HTTP Server

 

+

Search Tips   |   Advanced Search

Overview

After you install Lotus Connections, create a Web server for each profile or node for which you want to map features. This task updates plugin-cfg.xml on IHS.

By mapping all the features to IHS, you tell it which ports to use to access each feature and it can redirect requests to the appropriate features. Each Lotus Connections feature is made up of one or more modules. You must map each module to IHS.

The Blogs and Dogear features force login credentials to be submitted over a secure channel.

If you are using the Files or Wikis features, configure IHS to handle file downloads from those features.

If you choose to let WAS redirect servlet manage file downloading, to avoid errors caused by using too much memory, configure the server to transfer data synchronously instead of asynchronously


Set up

  1. Install and start IHS

  2. Create a webserver definition in appserver for new IHS instance

  3. To map features to IHS, go to...

      Applications | Enterprise Applications | Lotus_Connections_feature | Manage Modules

    In the Clusters and Servers box select both of the following servers:

    • server_name
    • webserver1

    ..where server_name is the name of the appserver profile on which you installed the feature. Select the check boxes for all the modules and then click Apply and Save.

  4. For multiple features to a single WAS profile, specify a virtual host for the port from which each feature can be accessed. Go to...

      Environment | Virtual Hosts default_host | Host Aliases | New

    ..and add the following values to the fields...

      Host Name: feature_name
      Port: port_number_for_feature

    For port numbers, refer to the serverindex.xml file.

    For example, if you installed all features to a single profile, and Wikis was assigned the port number 9085, specify...

      Host Name: wikis
      Port: 9085

    Click OK, and then click Save.

    Repeat these steps to add a virtual host for each feature in the profile.

  5. From the WAS console, select...

      Servers | Web servers

    ..and select the check box beside webserver1, and then click...

      Generate Plug-in

  6. Select the check box beside your web server again, and then click Propagate Plug-in.

    If you have trouble propagating the plug-in on Linux, restart the IHS ...

      ./adminctl start
      ./apachectl -k stop
      ./apachectl -k start

  7. For Communities only, select...

      Environment | Update global Web Server plug-in configuration | OK

  8. Stop and restart the Web server.

  9. Restart the servers for Lotus Connections features...

    1. From the WAS console, select...

        Applications | Enterprise Applications

    2. Select the check box beside each feature that you want to restart.

    3. Click Stop.

    4. Select the same check boxes again, and then click Start.

  10. Log out of the WAS console.

  11. Test the mappings by accessing each of the features...

      http://hostname/feature_name

    ...where hostname is the host name of the Web server to which you mapped the feature and feature_name is the name of the feature. Do not specify the port number.

  12. Stop WAS.

  13. Edit...

      PROFILE_HOME/profile_name/config/cells/cell_name/LotusConnections-config/LotusConnections-config.xml

  14. Update the Web addresses specified in the href and ssl_href properties for each feature.

    For example, to update the Web address for Activities, edit the file to read as follows

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

    Where webserver is the address of your IBM HTTP Server and feature is the name of a Lotus Connections feature.

    For example, to update the Web address for Activities, you would 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/activities"
             ssl_href="https://hostname/activities"/>
            <sloc:interService href="https://webserver"/>
      
          </sloc:href>
      
      </sloc:serviceReference>
      

    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 Lotus Connections wiki for more information about deployment scenarios, including how to configure a reverse proxy.

  15. If you installed each feature to a separate profile, repeat this step for each feature. There is one LotusConnections-config.xml file associated with each profile, so edit each of them.

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

  17. Restart WAS and then log into each feature to make sure that the Web address links for the features in the navigation bar have been updated.

 

Results

You should now be able to access each feature without needing to specify a port number.


Configure IBM HTTP Server


Previous topic:

Determining which files to compress

 

Related tasks

Map multiple profiles to a single IHS

Configure IBM HTTP Server for SSL
Add certificates to IBM HTTP Server
Instruct Web browsers to cache content
Lotus Connections wiki