Load balancing with multiple IBM Controller application servers

To increase the performance of IBM® Controller, you can spread the workload between several Controller application servers.

Before you begin

If you want to use several Controller application servers, where some users use server 1 and others use server 2, then the following diagram shows how to set up these Controller application servers.

Diagram that shows a Controller application primary server, a Controller secondary server, a shared repository, and Controller client systems that are connected.

One application server acts as the primary. The primary server hosts the active user manager. You can have several separate secondary servers. The secondary servers use the user manager that runs on the primary server.

Procedure

  1. On the master system, install the Controller application server.
  2. On the secondary system perform the following tasks:
    1. Install only the Controller server components.
    2. Use the same version of Controller on the primary and secondary system.
    3. Configure the Controller server on the secondary system in the same way as the primary application server. The master and secondary systems must contain the same database connections (same UDL files).
  3. On each secondary system, configure the web.config file by performing the following tasks:
    1. In the ControllerProxyServer folder, open the web.config file.
      The default location of the ControllerProxyServer folder is C:\Program Files\ibm\cognos\ccr_64\ControllerProxyServer.
    2. In the <appSettings> section, add the following entry <add key="ccrRemoteServer" value=" http://PRIMARYSERVER_NAME/ibmcognos/controllerserver" />.
  4. Save the changes and restart all servers.