Tips for Installing Cognos Analytics

February 15, 2018

Cognos Analytics (v11)

Configuring and Installing the Server

We review the latest steps for installing and upgrading your Cognos environment. Our Cognos installation and upgrade expert, Todd Schuman, describes the installation and configuration steps on the server side of Cognos Analytics.

Among the highlights:

  • Install options
  • Gateway and IIS setup
  • Database drivers
  • Release upgrade strategy
  • Schedule migration tips

Learn more about Cognos Analytics from the IBM product team who is responsible for v11 updates in this webinar recording, Cognos Analytics Release 8 Enhancements


IBM Cognos Analytics


BI Power Users (Developers, Support Staff), BI Managers, IT Managers, Program or Project Managers


Todd Schuman
Practice Lead – Installations, Upgrades and Performance Tuning
Senturus, Inc.

Todd has over 16 years of business analytics experience across multiple industries. Todd also regularly connects with the IBM product development team and has been in the forefront of the Cognos Analytics upgrade and installation process since it debuted. Plus, he presented Considerations When Upgrading to IBM Cognos Analytics alongside IBM product managers at the 2016 World of Watson conference.

You might also be interested in reading Todd's blog Windows vs Linux: What’s Best with Cognos Analytics? in which he discusses the  pros and cons of each to help you assess the best fit for your organization.

  • Installation options
    • Cognos Analytics – server software
    • Cognos tools – lifecycle manager
    • Easy vs custom
    • First install vs connect and install
    • Selecting components
      • Content repository
      • Application services
      • Optional? gateway
      • Samples

Multi server environments

  • Adding Servers
    • Need at least one running content repository
    • Namespace
    • Need an account with system admin rights
    • Need content manager URI

Gateway/webserver configuration

  • IIS steps
    • Stay on top of documentation – frequent changes
    • ARR 3.0
    • Application request routing
    • URL rewrite
    • App pools
    • MIME types
    • Rewrite rules
    • Server farms
    • SSO
  • ISS cheat code
    • Automate everything with a command line, batch file!
    • Plug in:
      • IIS website name (Default)
      • App pool name (ICAPool)
      • Alias (ibmcognos)
      • Install path
      • Dispatcher list (0-X)
      • Enable SSO
      • Web farm name
    • Updated frequently – 1.9.18 most recent
  • Apache
    • As of 11.0.5+
    • Included as part of install gateway_component_install_location/cgi-bin/templates
  • Database drivers
    • JDBC drivers – must have fro Cognos Analytics
      • [install Dir]\drivers and dashboard
      • Data modules require JDBC
    • Install DB software on servers that require database access
      • App tier/dispatchers
      • Content repository
    • SQL native client
    • Oracle client
  • JDBC – SQL Server
  • JDBC – Oracle

Releases upgrade strategy

  • Preserve custom folders
    • New releases overwrite all folders
    • Always backup before
    • [Install Dir]\analytics\configuration\preserve – preserve.txt
    • # specify files or folders to preserve – [folder name] and [folder name]\image.jpg
    • Preserve
      • Images/logos
      • JS files
      • WAR files
      • Certs
  • Installing releases
    • On top installation
    • Backup/archive content store before
    • Export Cognos configuration to external location
    • Check supported software and prerequisites
    • Download and install new samples

Schedule migration tips

  • Prevent schedules from running
    • Batch, delivery, job services
  • Separate Enabled/Disabled Schedules
    • Most schedules default to priority 3
    • Find a priority number with nothing set to it (#1 or #5)
    • Filter on all enabled schedules
    • Select all and set priority to number from step #2
    • Disable all schedules
  • Schedule migration
    • You can now turn batch, job, delivery services back on to test capabilities without accidently sending emails
    • When you are ready to go-live, filter on the priority you used to isolate, select all and enable the schedules to restore back to current production