Running multiple versions or instances of IBM Cognos Analytics on the same computer

To have multiple versions or instances of IBM® Cognos® Analytics on the same computer, you must change the configuration to ensure that the versions do not share port numbers or other resources.

Required configuration changes for running multiple versions on the same computer

To run multiple versions of IBM Cognos Analytics on the same computer, ensure that each installation is distinct. The versions or instances must be installed in different directories. The configuration settings for each version must use different settings for the following configuration properties.

Ports and URI settings

If you are using the default application server, you must use different port numbers than 9300 to avoid port conflicts. IBM Cognos Analytics reserves a range of port number, so you must ensure that you use an offset of at least 100 for the port number. For example, if you are using the default port number, 9300, for one instance of IBM Cognos Analytics. For a second installation on the same computer, you must change the port number to at least 9400. Do not use the same port numbers for both installations.

Change the following ports.

  • Dispatcher URIs for gateway
  • External dispatcher URI
  • Internal dispatcher URI
  • Dispatcher URI for external applications
  • Content Manager URIs
  • Local log server port number

If you are installing the product on an application server other than the one provided with IBM Cognos Analytics, ensure that you install the new version to a new application server profile or a separate instance than your existing version.

Content store
Use a different content store or schema for each installation. You cannot revert the content after it is upgraded. You can use a restored copy of your existing content store as the content store for the newer version of IBM Cognos Analytics. The newer version of the product upgrades the content store when you start the services.
Optional web server virtual directories

To view static content for IBM Cognos Analytics, the virtual directories for the web server must be different for each version. Ensure that you update the Gateway URI in Cognos Configuration to reflect the names of the virtual directories.

For example, the default virtual directory is http://servername/ibmcognos. If you have two gateways that are installed on the same computer, you must change the ibmcognos virtual directory for one of the gateways.

Application pools (Microsoft IIS web server)
If you use cognosisap.dll, each gateway must use a separate application pool.
User account that starts the service (optional)
Changing the user account might be helpful when you are troubleshooting. For example, you can troubleshoot Java™ processes by owner.

Configuration settings that are the same for multiple versions on the same server

Multiple instances or versions of IBM Cognos Analytics running on the same computer use the same resources, such as memory, network, and disk space.

Multiple versions of IBM Cognos can use the same authentication source for both versions. You can configure identical properties for the namespace.

Customized configuration files

If you manually edited any configuration files, you must reapply the changes. Keep a record of any customizations to ensure that they can be reapplied after you upgrade. Also, back up these files so that the original version can be restored if necessary.

The IBM Cognos Analytics presentation service supports automatic upgrade of some system.xml files. If you made many customization changes to system.xml files, you can use this automatic upgrade feature instead of reapplying the changes manually after you upgrade. By replacing the system.xml files with files from your earlier version of the product, the files can be upgraded by the new version of the product. The automatic upgrade is applied when you start the IBM Cognos service.

The system.xml files for which automatic upgrade is supported are in the following directories:

  • install_location/templates/ps
  • install_location/templates/ps/portal
  • install_location/templates/ps/qs