Home

 

Map multiple profiles to a single IBM HTTP Server


Overview

You can map multiple profiles to one IBM HTTP Server by defining a Web server for each profile, mapping each profile separately, and then merging the resulting configuration files.

Complete this procedure if you installed each Lotus Connections feature to a separate profile, but want to use a single IBM HTTP Server with the product. Do not complete this procedure if you are planning to add the multiple profiles to a node in a network deployment. In that case, you can define a Web server for the node and map the node to the IBM HTTP Server.


Map multiple profiles to a single IBM HTTP Server

  1. Map features to the IBM HTTP Server to map only one of the profiles.

  2. Copy the plugin-cfg.xml file, and then name the copy to associate the file with the profile you just mapped, for example:

      plugin-cfg-Activities.xml

  3. Repeat Steps 1 and 2 for each profile.

  4. Merge the multiple copies of the plugin-cfg.xml file into a single file, name it plugin-cfg.xml and replace the file in the IBM HTTP Server with the edited version you just created.

    To merge the files, capture the following values:

    1. Add the <VirtualHost> elements from each feature profile configuration file into the <VirtualHostGroup Name="default_host"> element block in the merged file. For example, the following set of virtual host values represent the set for a single feature profile. Your port numbers will differ based on your configuration:

        <VirtualHostGroup Name="default_host">
              <VirtualHost Name="*:9084"/>
              <VirtualHost Name="*:80"/>
              <VirtualHost Name="*:9447"/>
              <VirtualHost Name="*:5069"/>
              <VirtualHost Name="*:5068"/>
              <VirtualHost Name="*:443"/>
           </VirtualHostGroup>   
        

    2. Copy the <ServerCluster> element from the configuration file for each feature profile into the merged file. For example:

         <ServerCluster 
           CloneSeparatorChange="false" 
           IgnoreAffinityRequests="true" 
           LoadBalance="Round Robin" 
           Name="server1_Node05_Cluster" 
           PostBufferSize="64" 
           PostSizeLimit="-1" 
           RemoveSpecialHeaders="true" 
           RetryInterval="60">
              <Server 
                 ConnectTimeout="0" 
                 ExtendedHandshake="false" 
                 MaxConnections="-1" 
                 Name="my_server1" 
                 ServerIOTimeout="0" 
                 WaitForContinue="false">
              <Transport 
                 Hostname="example.example.com" 
                 Port="9084" 
                 #Port number is based on your configuration, so may differ
                 Protocol="http"/>	
              <Transport 
                 Hostname="example.example.com" 
                 Port="9447" 
                 #Port number is based on your configuration, so may differ
                 Protocol="https">	
                 <Property 
                    Name="keyring" 
                    Value="C:\IBM\HTTPServer\Plugins/config/webserver1/
                     plugin-key.kdb"/>
                 <Property 
                    Name="stashfile" 
                    Value="C:\IBM\HTTPServer\Plugins/config/webserver1/
                     plugin-key.sth"/>
              </Transport>
           </Server>
        </ServerCluster>  
        

    3. Copy the <UriGroup> element from the configuration file for each feature profile into the merged file. For example:

        <UriGroup 
           Name="default_host_server1_Node05_Cluster_URIs">
           <Uri 
              AffinityCookie="JSESSIONID" 
              AffinityURLIdentifier="jsessionid" 
              Name="/profiles/*"/>	
              #The URI will differ based on your configuration; this example is 
               for Profiles
           <Uri 
              AffinityCookie="JSESSIONID" 
              AffinityURLIdentifier="jsessionid" 
              Name="/ibm_semanticTagServlet/*"/>	
              #The URI will differ based on your configuration; this example is 
               for profiles
           <Uri 
              AffinityCookie="JSESSIONID" 
              AffinityURLIdentifier="jsessionid" 
              Name="/profiles/nav/*"/>	
              #The URI will differ based on your configuration; this example is 
               for profiles
        </UriGroup>  
        

    4. Copy the <Route> element from the configuration file for each feature profile into the merged file. For example:

        <Route 
           ServerCluster="server1_Node05_Cluster" 
           UriGroup="default_host_server1_Node05_Cluster_URIs" 
           VirtualHostGroup="default_host"/>
        

  5. Do not map any more profiles to the IBM HTTP Server, or you will overwrite the file you just edited.

 

Example

This example shows a merged plugin-cfg.xml file for two nodes. Activities is installed on one node and Blogs is installed on the other one.


Map features to IBM HTTP Server

+

Search Tips   |   Advanced Search