Deploying a Cognos cluster

Only complete this procedure if you plan to set up a Cognos cluster, otherwise skip to the next topic.

Before you begin

When installing IBM Connections including the Metrics application, be sure to select do later in the Cognos configuration panel.

Set up a share folder as the power cube folder to be used by all BI nodes as follows:

On Linux/AIX:

On the server where you want to share out the local folder:
  1. Create a folder to be the power cube folder, such as /opt/IBM/Cognos/PowerCube.
  2. Run vi /etc/export.
  3. Add content such as: /opt/IBM/Cognos/PowerCube *(rw,sync,no_root_squash) .
  4. Run nfs start. If you cannot find the command, perform this action through the interface.
On the server where you want to use the shared folder:
  1. Create the same power cube folder as previously described.
  2. Run mount -t nfs [server_homename]:/opt/IBM/Cognos/PowerCubes /opt/IBM/Cognos/PowerCubes.

On Windows

On the server where you want to share out the local folder:
  1. Create a folder to be the power cube folder, such as C:\IBM\Cognos\PowerCube.
  2. Make a network share on this folder.
On the server where you want to use the shared folder:
  1. Map a network drive to the shared power cube folder you just created. Or use the network path to access the shared folder, such as \\[sharing_server_host]\PowerCube.
  2. Store the user and password for the connection.
Note: Always enter the same power cube path during the installation of the primary BI node, all secondary nodes, and Transformers. On Windows, always use the network driver or network path of the power cube folder, even on the server sharing the folder.
Note: If you have a transformer installed on a separate system that has no BI installed, you also need to use the shared power cube folder in the same path.


  1. Use the Cognos installation wizard to install the primary Business Intelligence (BI) Node and Transformer.
  2. Use the Cognos installation wizard to install the secondary BI node.
  3. Configure BI server Content Manager after installing the secondary BI node as follows:
    1. Check the Content Manager URL from the cogstartup.xml file and add the secondary BI server Content Manager URL to the cogstartup.xml of the primary BI server. The cogstartup.xml can be found in [CognosBI]\configuration\ folder.
    2. Add the primary BI server Content Manager URL to the secondary BI server. Keep the same sequence, which means the primary BI server Content Manager URL will be listed as the first node, then the first Secondary BI Server Content Manager URL next, followed by each secondary BI server. Perform this task after the installation of each secondary BI server.
    3. You need to restart the Cognos server after changing the cogstartup.xml, for example:
    <crn:parameter name="contentManagers" opaque="true">
         <crn:value xsi:type="cfg:array">
           <crn:item xsi:type="xsd:anyURI"></crn:item>
           <crn:item xsi:type="xsd:anyURI"></crn:item>
  4. Install IBM HTTP Server as follows:
    1. Download the four zip files from the Supplements Images (CZM91ML, CZM94ML, CZM95ML and CZXR9ML), and then extract all their content into one folder.
      Note: You must do this during extract; posting a copy does not work.
    2. Use Installation Manager 1.7.1 to install the IBM HTTP Server
    3. Choose HTTP Server, Plugins for WebSphere Application Server, and Toolbox to be installed.
    4. After installation, select WebSphere Customization Toolbox to start.
    5. Select Web Server Plug-ins Configuration tool in the WebSphere Customization Toolbox.
    6. Add Web Server Plug-in Runtime Locations.
    7. Create Web Server Plug-in Configuration, select IBM HTTP Server V8, and complete the rest of steps.
      Note: Make note of the name you specified as the Web Server Definition Name. You must use this name for the web server name when you create it in the Deployment Manager console. The default name is webserver1
  5. Define IBM HTTP Server in the Deployment Manager console.
  6. Configure IBM HTTP Server for SSL.
  7. Add certificates to the WebSphere trust store.
  8. Check the plugin-cfg.xml to see if all Connections applications, including Metrics, have been mapped in the plug-in file.
    If the generated plugin-cfg.xml contains only a partial list of Connections applications, you need to map the missing applications manually, including the Cognos application, to HTTP Server. Refer to Mapping applications to IBM HTTP server.
  9. Update web addresses in IBM HTTP Server.
  10. Configure Cognos BI Server to use HTTP.
    • Perform this step on all BI nodes.
    • When disabling BI anonymous access, do so on all BI nodes.
  11. Configure Cognos Transformer to use HTTP.
  12. Even if you have installed more than one transformer, only use one of them at one period. Disable the daily and weekly cube refresh scheduler jobs on all other Transformer servers that will not be used currently.
    Note: When you need to switch the Transformer server, copy all the .mdl files in the [Transformer]/metricsmodel folder from the previous Transformer server to the new server.
  13. Verify the cluster as follows:
    1. Start only one BI node, either primary or secondary.
    2. Running the build-all on all transformers should be successful every time.
    3. Visit Global Metrics where you should see Cognos reports in the Metrics interface.
    4. Stop the running BI node, and then start another one.
    5. Running the build-all on all transformers again should be successful.
    6. Within the same browser used in step c, refresh the page. You still should be able to see the Cognos reports.