There are three steps to installing and deploying Cognos to a system that has already been installed with IBM Business Monitor:
1) Install Cognos binaries
There are two ways to install the binaries for Cognos:
Use Installation Manager
Use the native installer contained within the repository shipped with Monitor
The Installation Manager repository for Cognos contains the native installer for Cognos. For example for the Windows 64 bit installer is in the following zip file
<root of install>\repository\COGNOS_64\native\cognos-win64_10.1.1.zip
Unzip this file to a directory and launch
<root of unzipped>\winx64h \issetup.exe
Take all the default except the location of Cognos. YOU MUST put Cognos in the <WAS root>/cognos directory. All other install tools assume that Cognos has been installed here.
This manual step is not documented.
2) Create the Cognos Application EAR
The easiest way to create the application EAR is to run an "ant" script that is run during profile creation.
From the WebSphere bin directory run the "generateCognosEar.ant" script. This script will copy files from Monitor to Cognos and then run the Cognos build script to create the application EAR. You will have to provide WebSphere's root, profile root of the Deployment Manager or standalone server, the profile name, and the location of the ant script ... for example:
ws_ant.bat -DWAS_HOME C:\WAS80 -DprofilePath C:\WAS80\profiles\Dmgr01 -DprofileName Dmgr01 -f C:\WAS80\profileTemplates\wbmonitor\actions\generateCognosEar.ant
The actions of the ant script can be done in pieces as documented on the following pages on copying files and running the Cognos build (not all steps discussed on these pages need to be done):
3) Deploy the Cognos service
There are three ways to deploy Cognos once it has been installed and the EAR generated; option 2 is the easiest.
Using Deployment Environments, however if this has already been run then it is not possible to add in just Cognos later
Using the Monitor Configuration Wizard
This method can be run at anytime. This WebSphere Admin wizard will check to see if the "IBM Cognos" ear is installed and if not installed will show a page that allows the user to deploy Cognos
The following page describes how to run the wizard, only focus on step 7a: Configuring the environment using the configuration wizard
Using the Monitor WebSphere command line
The following page describes what the options are for the wbmDeployCognosService command. The easiest way to run this command is just to use the -interactive parameter and it will ask you for each parameter. This is the same command that is run by the DE process and the Monitor Configuration Wizard under the covers from options 1 and 2 above: IBM Cognos BI service
Some other post install items:
Verify that Monitor Model has published the Cognos cubes
If you have deployed a Monitor Model to your IBM Business Monitor before IBM Cognos was installed then you have to manually publish the cubes: Publishing IBM Cognos BI cubes
Verify that Business Space is able to get to Cognos so that reports can be created and viewed on the published cubes
It might be necessary to also configure Bspace and Cognos so that each knows about the other. You might want to log into Business Space and add the Report Designer and Report Viewer to a page. Using the Report Designer you should be able to select a model that has had it's cubes published to Cognos. Once the model has been selected and a report saved, you should be able to select the report on the Report Viewer.
The following page describes a number of steps to have Business Space know where Cognos is located and to be sure that Cognos is allowing traffic to the domains (see the next section to know where your Cognos is located): Configuring IBM Business Monitor and Business Space to use an existing IBM Cognos BI service
Where is the Cognos runtime
Only one Cognos runtime can use a Cognos install directory, therefore Monitor has to create a new copy of Cognos for every cluster member. The Cognos that is installed under WebSphere root is used as a master source copy for all cluster members. The Monitor server startup task will make a copy from the master to the profile on the first startup of the Cognos server. Cognos service fixes will be applied to the master copy and the Monitor server startup task will check on every server start if there is a change to the service level. If there is a change, the Monitor startup task will copy the new code to the profile, thus keeping them synchronized. All the cluster member's Cognos runtime configuration files, log files, and binaries will be in the following directory:
<profile root>/cognos/<server name>
IMPORTANT: If a configuration change is needed, you must run it from each Cognos cluster member's bin or bin64 directory (do not run the Cognos master configuration program as this will not be used by the cluster members ).
title image (modified) credit: (cc) Some rights reserved by warszawianka