Customer has a working Controller 10.2.1.x application server. Customer would like to patch this 10.2.1 server to a later version of 10.2.1. How do they do this?
For reference, here are the version numbers of Controller 10.2.1 which this Technote relates to:
- 10.2.1 RTM = 10.2.5100.95
- 10.2.1 IF1 = 10.2.5100.104
- 10.2.1 IF2 = 10.2.5100.105
- 10.2.1 Fix Pack 1 (FP1) original release = 10.2.5110.82
- NOTE: Do not use this version on a Citrix/Terminal server environment.
- 10.2.1 Fix Pack 1 (FP1) updated version = 10.2.5110.85
- 10.2.1 FP1 IF1 = 10.2.5110.91
- 10.2.1 FP1 IF1 GA (publicly/generally available) = 10.2.5110.95
- 10.2.1 FP2 = 10.2.5120.72
- 10.2.1 FP2 IF1 GA (publicly/generally available) = 10.2.5120.73
- 10.2.1 FP2 IF2 GA (publicly/generally available) = 10.2.5120.82
- 10.2.1 FP3 = 10.2.5130.56
- 10.2.1 FP4 = 10.2.5140.12
- 10.2.1 FP4 IF1 GA = 10.2.5140.13
- 10.2.1 FP4 IF1 = 10.2.5140.14
- 10.2.1 FP4 IF2 = 10.2.5140.17
- 10.2.1 FP4 IF3 = 10.2.5140.18
- 10.2.1 FP4 IF4 = 10.2.5140.20
- 10.2.1 FP4 IF2 GA = 10.2.5140.21
- 10.2.1 FP4 IF5 = 10.2.5140.22
- 10.2.1 FP4 IF6 = 10.2.5140.24
- 10.2.1 FP4 IF7 = 10.2.5140.24
- 10.2.1 FP4 IF8 = 10.2.5140.26
- 10.2.1 FP4 IF9 GA = 10.2.5140.30
- 10.2.1 FP4 IF10 = 10.2.5140.32
- 10.2.1 FP4 IF11 GA = 10.2.5140.36
- 10.2.1 FP4 IF12 = 10.2.5140.39
- 10.2.1 FP4 IF13 GA = 10.2.5140.40
- 10.2.1 FP4 IF14 = 10.2.5140.42
- 10.2.1 FP4 IF15 = 10.2.5140.45
- 10.2.1 FP4 IF16 GA = 10.2.5140.45
- 10.2.1 FP4 IF17 GA = 10.2.5140.45 (also!)
- 10.2.1 FP4 IF18 = 10.2.5140.47
- 10.2.1 FP4 IF19 = 10.2.5140.49
- 10.2.1 FP4 IF20 GA = 10.2.5140.49 (also!)
This Technote describes the process of how to upgrade from any version listed above, to any later version also displayed above.
- For example, a customer may want to upgrade from Controller 10.2.5140.12 (also known as 10.2.1 Fix Pack 4) to 10.2.5140.39 (also known as 10.2.1 FP4 Interim Fix 12).
It is possible to patch an existing 10.2.1 Controller application server *without* having to perform a full uninstall/re-install of the Controller application server software. However, care needs to be taken (during the patching process) to ensure that all Controller-related services/systems/components are stopped.
IMPORTANT: All patches are cumulative.
Therefore, there is no need to apply/install any other patches (apart from the one that you wish you upgrade your system to).
- Example: If you wish to upgrade from Controller 10.2.1 RTM (10.2.5100.95) to 10.2.1 IF2 (10.2.5100.105), then there is no need to also install Controller 10.2.1 IF1 (10.2.5100.104) in between.
Customer's environment currently running any version of Controller 10.2.1 (for example 10.2.5100.95) and would like to patch it to a later 10.2.1 version (for example 10.2.5130.56).
Diagnosing The Problem
To check which version of Controller you are currently using, click "Help - System Info" (inside the Controller client) and check the value of the first/top line.
Resolving The Problem
IMPORTANT: In an ideal world, you should get an experienced IBM Technical Consultant onsite to help you perform these tasks.
- However, assuming they have actioned all the precautions listed in the document, then a customer may feel confident to perform these tasks themselves (without any outside assistance).
To upgrade the Controller application server, perform the following tasks:
1. Download a copy of the patch (either a Fix Pack or Interim Fix).
- Fix Packs (FP) are freely available from IBM Fix Central (link below). Therefore you do not need to log a support call (PMR) to obtain these.
- However, to obtain a copy of most interim fix (IF) patches you must log a support call with IBM Support
- The exceptions are any 'GA' (generally available) patches. These are freely available from IBM Fix Central (link below) - there is no need to log a support call (PMR) to download 10.2.1 IF1.
2. Obtain downtime (no users on system)
3. As a precaution, perform the following tasks:
- (a) Backup all Controller-related databases (application repositories, ContentStore and FAP)
- As an extra precaution, you could also perform a 'full deployment export' of the content store. For instructions on how to do this, see separate IBM Technote #1985447.
(b) Launch "Cognos Configuration" and create a backup of all the settings
- Typically this means click "File - Export As" and save the settings as an XML file (in a safe place)
- As an extra precaution, you could also create a Word document with printscreens of all the current settings
(c) Launch "Controller Configuration" and create a backup of all the settings
- e.g. create a Word document with printscreens of all the current settings
- In other words, ask your ESX administrator to create a virtual snapshot backup of any server (for example Controller application server) before you make any changes.
4. VITAL: Shut down all Controller-related Windows services (running on the application server(s))
- Specifically, stop the following Windows services:
- IBM Cognos
- IBM Cognos Controller Batch Service
- IBM Cognos Controller Consolidation
- IBM Cognos Controller Java Proxy
- IBM Cognos Controller User Manager
- IBM Cognos FAP Service
5. VITAL: Shut down other Controller-related subsystems (running on the application server(s))
- Launch the "Internet Information Services (IIS) Manager" tool
- Highlight the Default Web Site.
- Click "Stop":
6. As a precaution, now take a backup copy of the entire ccr_64 folder (e.g. compress inside a backup ZIP file):
[This process helps make it easier to revert back to the older version of Controller if necessary later].
7. If the Controller application server has a Controller client installed, then uninstall the Controller client first before proceeding:
8. Install patch onto the application server(s) by doing the following:
- Extract the compressed patch file
- Double-click on installer file issetup.exe (inside subfolder winx64h)
- Navigate through the installation wizard (in general by accepting all the default options).
- TIP: Ensure that you choose the installation folder to be the same folder as the current installed version
- If you have multiple Controller application servers, apply the patch for all remaining Controller application servers.
9. After the patch has finished installing, launch "IBM Cognos Configuration". Click the buttons (near the top-left corner of the screen) to:
- Save the current configuration
- Start the IBM Cognos service:
10. Afterwards, launch "Controller Configuration" and open the section 'Database Connections'. Click on each database connection, and click on the green 'play' button.
- Check to see if the 'Current Version' is set to be the same as the 'Upgrade to' version:
Sometimes (depending on the old/new versions of Controller) the "Upgrade to" will have increased (because of the patch). If so, then you must press 'Upgrade' to upgrade your Controller application databases (to the latest version).
11. Inside Controller Configuration, check that all the other settings look *exactly* the same as before the upgrade. Most importantly (in particular) check the following two sections:
- Report Server:
- COM+ Server:
TIP: Refer to the printscreens that you took earlier (in step 3 - before the upgrade) to make sure that the settings look the same as before.
12. If you used "ISAPI" before the upgrade, then:
- change "Report Server" to mention cognosisapi.dll instead of cognos.cgi
- modify the files "default.htm" and "index.html" (located in webcontent folder) to refer to cognosisapi.dll instead of cognos.cgi
13. Check the Windows service "IBM Cognos Controller Java Proxy". Ensure that it is configured to 'Log On As' using the correct Windows user (typically the Cognos Controller system user e.g. <domain>\Controller_system).
14. Inside the IIS Manager, highlight the "Default Web Site" and click "Start"
15. Afterwards, reboot Controller 10.2.1 application server(s) (to automatically start relevant services and ensure that the registry key change takes effect)
16. Upgrade client software on each-and-every end-user's client device (see below).
Simplified instructions for how to upgrade *Client* software on each-and-every end-user's client device:
1. Logon to the client device as the SAME Windows administrator which originally installed the Controller client.
2. Launch "Add/Remove Programs" and remove the Controller client (for example "IBM Cognos Controller Local Client"):
3. Download the new version of the Controller client from the application server
TIP: You can download it from: http://SERVERNAME/ibmcognos/controllerbin/ccrlocalclient.msi
- There are three different versions of the client - see Technote#1371088. For most customers, CCRLocalClient.MSI is the best version to use.
4. Double-click on the client installation file (for example "ccrlocalclient.msi")
5. Follow the installation wizard
- TIP: Below is an example of a completed WSS and Help Url section:
6. If the client device does not have access to the internet (e.g. most Citrix/Terminal servers) then modify the file "ccr.exe.config" (inside C:\Program Files (x86)\ibm\IBM Cognos Controller) as per separate Technote #1441779.
TIP: If unsure what values to use (for example WSSUrl) then open the file %APPDATA%\Cognos\CCR\ccr.config inside NOTEPAD and read the values from there.
Was this topic helpful?
28 June 2019