IBM Support

Step-by-Step directions for applying CR2, CR3, CR4, or CR5 for Connections 4.5 with Connections Content Manager

Preventive Service Planning


Abstract

This document contains the steps to upgrade Connections with Connections Content Manager (CCM) and its dependencies, like FileNet, to the IBM Connections 4.5 CR2, CR3, or CR4 level.

Content

Before you start, please review the "Information on updating FileNet 5.2.0 for use with IBM Connection Content Manager (CCM)" document for the list of compatible FileNet versions needed for each 4.5 CR, and to download the necessary FileNet files.

We also recommend that you review the "Update strategy for IBM Connections 4.5" document for information on installing IBM Connections 4.5 CRs, including important notes and requirements for each Connections CR.

Sections:
Section 1 - Upgrade FileNet Content Engine Server
Section 2 - Upgrade FileNet Content Platform Engine Client and FileNet Collaboration Services (FNCS)
Section 3 - Apply Connections 4.5 CR
Section 4 - Update CCM
Section 5 - Applying Cognos fixes for 4.5 CRs

Steps:

Section 1 - Upgrade FileNet Content Engine Server



In this section you will upgrade FileNet Content Engine, if necessary. Refer to this table to determine if you need to upgrade FNCE:

Starting IBM Connections version Upgrading to IBM Connections CR2 Upgrading to IBM Connections CR3 or above
4.5 with no CRs Install 5.2.0 FP1 for FileNet Content Engine Server Install 5.2.0 FP2 for FileNet Content Engine Server
4.5 CR1 No update required to FileNet Content Engine Server No update required to FileNet Content Engine Server, but 5.2.0 FP2 is recommended.
4.5 CR2 or CR3 Not applicable. No update required to FileNet Content Engine Server, but 5.2.0 FP2 is recommended.
4.5 CR4 Not applicable. No update required to FileNet Content Engine Server, but 5.2.0 FP3 is recommended.

To verify the version of Content Engine, go to
https://<FILENET_HOSTNAME>/FileNet/Engine

For example, FP1 will show build version dap520.001.052.

In this step you install the FileNet Content Platform Engine (CE). On a Windows install it will connect to the existing server, so you want to leave the servers running. On Linux or AIX you want to shut all systems down.

The install is done on the DMGR server in a multi node environment.
minimum required. Latest fixpack is recommended.

Files needed during this section
·

    FileNet Content Engine Server FP1 (e.g. 5.2.0.1-P8CE-WIN-FP001) is the minimum required
or
    FileNet Content Engine Server FP3 (e.g. 5.2.0.3-P8CPE-WIN-FP003) is the latest recommended fixpack

Please ensure to use the necessary version, according to the table included at the beginning of this section.


1.1. Install CE updates interactively

Extract the Content Engine Server to a location on the DMGR server (I used C:\downloads\ic45CR1\FileNet\CE) and run C:\downloads\ic45CR1\FileNet\CE\ 5.2.0.1-P8CE-WIN-FP001.exe

2.

3.

4.
NOTE: This is the location of the install when installing CCM during the Connections 4.5 install

5. The next screen is asking for the URL to the Content Engine. The best way to determine the url you want to use is to try to access it via a browser (NOTE: you will need to start the servers if on Linux or AIX) the URL to use is

If using an http server in front of connections: http://httpserver.domain.com/wsi/FNCEWS40MTOM/

If you are not using an http server: http://FileNetserver.domain.com:wasport/wsi/FNCEWS40MTOM/

NOTE: If you are not using an http server, and are unsure of the port . . . Go to the WAS console, find the default_host port for the appserver hosting the FileNetEngine app

Then test the url in a browser. In my environment I have an http server, so the url is http://server.swg.usma.ibm.com/wsi/FNCEWS40MTOM/


So update the url to the one for your environment

6.

7.


1.2. Verify the CE server upgrade

1. Go to C:\IBM\Connections\addons\ccm\ContentEngine and open ce_version.txt. Note the version number, you will need it later in the install


1.3. Remove the currently deployed FileNet Content Engine

Make sure the DMGR and nodeagent are running (on my windows machine the connections nodes were running as well)

1. Open the WebSphere Integrated solutions console and go to Applications -> Application Types -> WebSphere enterprise applications and select "FileNetEngine" . Then click the "Uninstall" button .

Note: This deletes the Engine-ws.ear from the WAS Server .

2.

3.

4. The FileNetEngine application should be removed. Check the nodeagent logs (C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent\SystemOut.log) for the following line:

ADMA7021I: Distribution of application FileNetEngine completed successfully.

5. Stop Connections node, nodeagent and dmgr by running:

a. Stop Connections node: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopserver.bat lccluster_server1 -username localadmin -password password

b. Stop nodeagent: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopNode.bat -username localadmin -password password

c. Stop DMGR: c:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\stopManager.bat -username localadmin -password password

6. Delete temp directories on all nodes by removing the FileNetEngine folder in C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\SERVERNode01\lccluster_server1

7. If it exists delete the FileNetEngine.ear folder from C:\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\SERVERCell01

Restart the Connections dmgr, nodeagent and nodes by running
a. Start DMGR: c:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\startManager.bat
b. Start nodeagent: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startNode.bat
c. Start Connections node: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startserver.bat lccluster_server1

8. Any browser that has been used to access the Content Engine administration tool (/acce) delete all the temp internet files


1.4. Upgrade the Content Engine profile

1. Start the FileNet Configuration Manager for Content Platform Engine by running C:\IBM\Connections\addons\ccm\ContentEngine\tools\configure\ configmgr.exe

2. In the configuration manager go to File -> Upgrade Profile

3.

4.

5.

6.

7.

8. Close the Welcome Screen if it's open to see the Content Platform Engine tab



9. Double Click on the task "Configure Bootstrap and Text Extraction"

10. Make sure the Bootstrap operations shows "Upgrade" .
Verify the path in the field "Bootstrapped EAR file" .
Click "Save" .

11. Once Saved, click Run Task

12.

13. Now double click on Deploy Application

14. Verify the path in the field "Bootstrapped EAR file" .
Click "Save" .

15. Once Saved, click Run Task

16. Once you see "Finished running Deploy Application" you can close the Configuration Manager

17. Check the nodeagent log file in C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent for
AppBinaryProc I ADMA7021I: Distribution of application FileNetEngine completed successfully.


1.4.1. Add FileNetEngine back to the HTTP server

Note, this step only needs to be completed if you have configured in HTTP Server in front of the connections environment


1. Open a browser to the IBM Integration Solutions console (http://server.swg.usma.ibm.com:9060/ibm/console) and login



2. Go to Application - Application Types - WebSphere enterprise applications and click on FileNetEngine


3. Click Manage Modules


4. Map all components to both the cluster they are running, and the http server
and click Apply


5. Click OK


6.

7. Go to Servers - Server Types - Web servers and select the http server and click Generate Plug-in


8. Select the http server again and click Propagate Plug-in to copy it to the http server


9.

10. Logout and close the WebSphere Integrated Solutions Console

11. Restart the IBM HTTP Server


12. Restart the Connections application by running
a. c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopserver.bat lccluster_server1 -username localadmin -password password

b. C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startserver.bat lccluster_server1

1.5. Verify the ear file updated correctly

1. Go to C:\IBM\Connections\addons\ccm\ContentEngine and open ce_version.txt. Note the version number.


2. Open a browser to the server /FileNet/Engine (http://server.swg.usma.ibm.com/FileNet/Engine)


3. The build version should match in both places dap520.001.052


1.6. Verify autoUpgradeStatus is Complete


1. Open the browser to http://server_name:port/FileNet/AutomaticUpgradeStatus

Example of upgrade status:

NOTE: If you get to this page, and the Upgrade Status shows Ready, look in the FileNet logs for the following messages:

DomainUpgrade(ICDomain) Completed domain upgrade sequence from version '5.1.1.61' to version '5.2.0.7'...

ObjectStoreUpgrade(ICObjectStore) Completed object store upgrade sequence from phase '18.2.2 InstallUAOs' to phase '18.2.2'...

For additional information on other upgrade status messages, such as "Not Available", please review this document: Checking the automatic upgrade status for Content Engine data

At this point FileNet Content Platform Engine is upgraded and we can move on to upgrade FileNet Content Platform Engine Client and FileNet Collaboration Services.


Section 2 - Upgrade FileNet Content Platform Engine Client and FileNet Collaboration Services (FNCS)

Two components are used to upgrade FNCS, FileNet Collaboration Services and FileNet Content Platform Engine Client. In section we will walk through upgrading and configuring these components.


Refer to this table to determine if you need to upgrade FNCPE and/or FNCS:

Starting IBM Connections version Upgrading to IBM Connections CR2 Upgrading to IBM Connections CR3 or CR4 Upgrading to IBM Connections CR5
4.5 with no CRs Install 5.2.0 FP1 for FileNet Content Platform Engine Client

Install 2.0.0 IF1 for FileNet Collaboration Services
Install 5.2.0 FP2 for FileNet Content Platform Engine Client

Install 2.0.0 IF1 for FileNet Collaboration Services
Install 5.2.0 FP3 for FileNet Content Platform Engine Client

Install 2.0.0 IF2 for FileNet Collaboration Services
4.5 CR1 Install 2.0.0 IF1 for FileNet Collaboration Services No update required to FileNet Content Platform Engine Client, but 5.2.0 FP2 is recommended.

Install 2.0.0 IF1 for FileNet Collaboration Services
Install 5.2.0 FP3 for FileNet Content Platform Engine Client

Install 2.0.0 IF2 for FileNet Collaboration Services
4.5 CR2 or CR3 Not applicable. No update required to FileNet Content Engine Server, but 5.2.0 FP2 is recommended. Install 5.2.0 FP3 for FileNet Content Platform Engine Client

Install 2.0.0 IF2 for FileNet Collaboration Services
4.5 CR4 No update required to FileNet Content Engine Server, but 5.2.0 FP3 is recommended. Install 5.2.0 FP3 for FileNet Content Platform Engine Client

Install 2.0.0 IF2 for FileNet Collaboration Services


2.1. Upgrade FileNet Collaboration Services


2.1.1. Uninstall the current FNCS Application

1. Open a browser to the Integrated Solutions Console and login

2. Go to Applications - Application Types - WebSphere enterprise applications
Select FNCS and click Uninstall

3.

4.

5. Monitor the SystemOut.log on the nodeagent (C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent) for

ADMA7021I: Distribution of application FNCS completed successfully.

6. Stop Connections node, nodeagent and dmgr by running:

a. Stop Connections node: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopserver.bat lccluster_server1 -username localadmin -password password

b. Stop nodeagent: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopNode.bat -username localadmin -password password

c. Stop DMGR: c:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\stopManager.bat -username localadmin -password password

9. Delete temp directories on all nodes by removing the FNCS folder in C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\SERVERNode01\lccluster_server1

10. If it exists delete the FNCS.ear folder from C:\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\SERVERCell01


2.1.2. Uninstall FNCS application binaries


1. Run C:\IBM\Connections\addons\ccm\FNCS\uninstall\fncs-uninstall.exe

2. Backup the C:\IBM\Connections\addons/ccm/FNCS/CE_API directory.

3. Backup the C:\IBM\Connections\addons/ccm/FNCS/configmanager/profiles/fncs-sitePrefs.properties file.

4. Delete the C:\IBM\Connections\addons/ccm/FNCS directory.


2.1.3. Install FileNet Collaboration Services (FNCS)

Files needed for this section:

· FileNet Collaboration Services (FNCS) IF1 (e.g. 2.0.0.1-FNCS-IF001-WIN)

I extracted this file to C:\downloads\ic45CR2\FileNet\FNCS


1. Run C:\downloads\ic45CR2\FileNet\FNCS\2.0.0.1-FNCS-IF001-WIN.exe

2.

3.

4.

5. Update the Installation directory to C:\IBM\Connections\addons\ccm\FNCS and click Next


6.

7.

8. Copy the CE_API directory you backed up earlier to the C:\IBM\Connections\addons/ccm/FNCS directory

9. Copy the fncs-sitePrefs.properties file you backed earlier to the C:\IBM\Connections\addons/ccm/FNCS/configmanager/profiles directory.

10. Finally verify that C:\IBM\Connections\addons\ccm\FNCS\properties\fncs-sitePrefs.properties has the following properties:
anonymousAccessEnabled=true
enablePropertySheetTemplateMinMax=true

Otherwise, add them to the file.


2.2. Upgrade Content Platform Engine Client CEClient interactively

Note: If you are currently running Connections 4.5 CR1 and applying CR2, you can skip this step and move to step 2.3 (Configure FileNet Collaboration Services). If you are running Connections 4.5 CR1 or Connections 4.5 CR2 and applying CR3 or CR4, you may optionally use this section to upgrade to FileNet Content Engine Client FP2. If you are running Connections 4.5 CR3 and applying CR4, no action is necessary. If you are running Connections 4.5 CR1 or above and applying CR5, you may optionally use this section to upgrade to FileNet Content Engine Client FP3.

Files needed for this section:

    FileNet Content Engine Client FP1 (e.g. 5.2.0.1-P8CE-CLIENT-WIN-FP001) is the minimum required

or

    FileNet Content Engine Client FP3 (e.g. 5.2.0.3-P8CE-CLIENT-WIN-FP003) is the latest recommended fixpack

I extracted the downloaded zip to C:\downloads\ic45CR1\FileNet\CECLIENT

Again, all steps below are done on the DMGR machine

Start all Connections by running the following commands:

Start DMGR: C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\startManager.bat

Start nodeagent: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startNode.bat

Start Connections node: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startserver.bat lccluster_server1

1. Run C:\downloads\ic45CR1\FileNet\CECLIENT\5.2.0.1-P8CE-CLIENT-WIN-FP001.exe

2.

3.

4. The next page asks for the host name and port of the Content Platform Engine Server:

This should point to the node:port or http server for the FileNet application we installed earlier. In my environment I have an http server, so I populate this with server.swg.usma.ibm.com and port 80. Again, this is the hostname and port I use to access the http server in front of Connections

5.

6. Select "IBM FileNet Services for Lotus Quickr" In my install, this was already selected and no changes had to be made:

7.

8. Update the FileNet common files directory and click Next:

9.

10.


2.3. Configure FileNet Collaboration Services

Make sure Connections is running.

1. Run C:\IBM\Connections\addons\ccm\FNCS\configmanager\configwizard.bat

2.

3. The next screen asks for the Content Platform Engine URL.

For an environment where FileNet is installed as part of the Connections/CCM install, there is a server jvm argument
(-DFileNet.EJB.ContextProperties=java.naming.provider.url=!)

(NOTE: you can see this by going to Servers - Server types - WebSphere application servers, chose the server FileNet is running on -- go to Server Infrastructure - Java and Process Management - Process Definition, click on Java Virtual Machine and review the Generic JVM arguments)

The jvm argument makes the Content Platform Engine URL unnecessary, but I think it best to still include a valid url for the configuration wizard. To do that either of the 2 options I will discuss below should work. I say should, because for some reason I could only get iiop working on my server:

iiop method:

In a single server FileNet install, we use an iiop connection to FileNet. For this you will need the bootstrap hostname and port. The url will be in the following format:

iiop://FileNet_host.domain.com:port/FileNet/Engine

The hostname is the server FileNet is running on. To determine the port, go to the WebSphere Integrated Solutions Console - Servers - Server types - WebSphere application servers, chose the server FileNet is running on, under Communication - Ports check the BOOTSTRAP_ADDRESS



So for my environment, I would use the url

iiop://server.swg.usma.ibm.com:2811/FileNet/Engine

corbaloc method:

In a clustered environment (i.e. where the FileNet server is federated into a DMGR) like most Connections environments, the url specified should be the following format:

corbaloc::node1_hostname:BOOTSTRAP_ADDRESS,:node2_hostname:BOOTSTRAP_ADDRESS/cell/clusters/your_websphere_cluster_name/FileNet/Engine

Where <cluster name> is the name of the FileNetEngine application server's cluster. For my server that is lccluster (you can find this in the manage modules of the FileNetEngine application

So in my environment the url would be:

corbaloc:rir:/cell/clusters/lccluster/FileNet/Engine

NOTE: this url should work, but for some reason it fails during the connections validation, so I used the iiop url.

Object store symbolic name should be - ICObjectStore

4.

5.

6.

7.

8.

9.

10.

11.

12. I made the application all caps (not sure if that's needed, but it's how it was before the upgrade

13.

14.

15. Once this completes, check the nodeagent SystemOut.log for the following message:
ADMA7021I: Distribution of application FNCS completed successfully.

16. Stop Connections node, nodeagent and dmgr by running:

a. Stop Connections node: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopserver.bat lccluster_server1 -username localadmin -password password

b. Stop nodeagent: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopNode.bat -username localadmin -password password

c. Stop DMGR: c:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\stopManager.bat -username localadmin -password password:

17. Start the Connections dmgr, nodeagent and node by running:
a. Start DMGR:
c:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\startManager.bat
b. Start nodeagent:
c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startNode.bat
c. Start Connections node:
c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startServer.bat lccluster_server1


2.3.1. Validate FNCS was upgraded correctly

1. Open a browser to http://server.swg.usma.ibm.com/dm

2. At the basic login prompt login with the FileNet admin account

3. You should get the following page


2.4. Add Anonymous user back to FNCS RunAs role


1. Log into the WebSphere Application Server administrative console that hosts your FileNet server with the FileNet Collaboration Services application, and log in


2. Click Applications -> Application Types -> WebSphere enterprise applications -> FNCS

3. Click User RunAs roles


4. Select the Anonymous role and enter the username and password of the LDAP user designated for the anonymous access role.
5. Click Apply


6. Click OK to save.


2.5. Install FNCS authentication filter
1. Go to Applications - Application Types - WebSphere Enterprise Applications.
2. Select FNCS and Click Update.


3. For Application update options, select the Replace, add, or delete multiple files option.


4. Select local file system if running the browser on the Deployment Manager node or remote if on another machine and then locate the auth_filter_patch.zip file in the C:/IBM/Connections/ccm/ccm/ccm/auth_filter_patch/auth_filter_patch.zip directory.



5. Click Next and OK to update the application.


6.

7.

FileNet is now upgraded to the necessary level for CR2, CR3, CR4, CR5, and you can proceed to apply the Connections CR.

Section 3 - Apply Connections 4.5 CR

In this step, we will install CR2, CR3, CR4, or CR5. Please review the Update strategy for IBM Connections 4.5 document for the CR fix list, and links to download the installation packages from Fix Central.

Backup the existing update Installer directory (C:\IBM\Connections\updateInstaller)

Extract 4.5.0.0-IC-Multi-UPDI-20131020.zip, and copy the updateInstaller directory to C:\IBM\Connections)

Extract 4.5.0.0-IC-Multi-CR05-LO79880.zip to C:\IBM\Connections\updateInstaller\fixes


3.1. Install

In this step the connections nodes should be stopped:

Run C:\IBM\WebSphere\AppServer\profiles\AppSrv01\

bin\stopserver.bat lccluster_server1 -username localadmin -password password

the DMGR and nodeagents should be running

1. Open a command prompt and run C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\setupCmdLine.bat

2. Run C:\IBM\Connections\updateInstaller\updateWizard.bat

3.

4.

5.

6.

7.

8.

9.

10.


11. Look in the nodeagent's SystemOut.log for the following messages

ADMA7021I: Distribution of application Mobile completed successfully.
ADMA7021I: Distribution of application Forums completed successfully.
ADMA7021I: Distribution of application Activities completed successfully.
ADMA7021I: Distribution of application Profiles completed successfully.
ADMA7021I: Distribution of application News completed successfully.
ADMA7021I: Distribution of application Help completed successfully.
ADMA7021I: Distribution of application Moderation completed successfully.
ADMA7021I: Distribution of application Homepage completed successfully.
ADMA7021I: Distribution of application FNCS completed successfully.
ADMA7021I: Distribution of application Blogs completed successfully.
ADMA7021I: Distribution of application WidgetContainer completed successfully.
ADMA7021I: Distribution of application Mobile Administration completed successfully.
ADMA7021I: Distribution of application Dogear completed successfully.
ADMA7021I: Distribution of application connectionsProxy completed successfully.
ADMA7021I: Distribution of application Metrics completed successfully.
ADMA7021I: Distribution of application Communities completed successfully.
ADMA7021I: Distribution of application Wikis completed successfully.
ADMA7021I: Distribution of application Search completed successfully.
ADMA7021I: Distribution of application Files completed successfully.
ADMA7021I: Distribution of application Common completed successfully.

12. Restart Connections


Section 4 - Update CCM

NOTE: ccmUpdate installs one add-on to the ObjectStore called "5.2.0 FP1 Social Collaboration User Identity Mapping Extensions" If it's already added to the ObjectStore, you don't need to do it again. Therefore, if you have already run the ccmUpdate script when previously updating to CR2 for example, you don't need to run it again when updating to CR3 or CR4. If you do run ccmUpdate again, you will see the following error: FNRCE0043E: E_NOT_UNIQUE: A uniqueness requirement has been violated. Add-on "5.2.0 FP1 Social Collaboration User Identity Mapping Extensions" is currently installed. This error can therefore be ignored. Please proceed with the remaining steps.

1. Go to C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin and delete dminfo.properties

2. Run C:\IBM\Connections\addons\ccm\ccmDomainTool\ccmUpdate.bat

3.

4. Restart environment


Section 5 - Applying Cognos fixes and database updates for 4.5 CRs


Files needed for this step:

4.5 CR2: All files from http://www-01.ibm.com/support/docview.wss?uid=swg21648864

4.5 CR3: http://www-01.ibm.com/support/docview.wss?uid=swg21655480

4.5 CR4: http://www-01.ibm.com/support/docview.wss?uid=swg21666250

4.5 CR5: http://www-01.ibm.com/support/docview.wss?uid=swg21674725

I downloaded all files to C:\downloads\ic45CR2\metrics


5.1. Update the databases

For CR2, only Metrics database needs to be updated.

For CR3, multiple databases need to be updated. Refer to the Updating the IBM Connections 4.5 databases to the required schema versions for Cumulative Refresh 3 (CR3) document for details.

For CR4, multiple databases need to be updated. Refer to the Updating the IBM Connections 4.5 databases to the required schema versions for Cumulative Refresh 4 (CR4) document for details.

For CR5, multiple databases need to be updated. Refer to the Updating the IBM Connections 4.5 databases to the required schema versions for Cumulative Refresh 5 (CR5) document for details.

The following steps and screen shots cover Metrics database updates for database type of DB2. For the other database updates and other database types, refer to the commands outline to the following documents:

In general, the steps follow the same method.

For DB2, use these steps as a guideline:

1. Go to Start - IBM DB2 - DB2COPY1 - Command Window

2. Run C:\IBM\SQLLIB\BIN>db2 -td@ -vf C:\downloads\ic45CR2\metrics\METRICS-db-upgrade-45-45CR2_DB2.sql

3. Run C:\IBM\SQLLIB\BIN>db2 -td@ -vf C:\downloads\ic45CR2\metrics\METRICS-db-reorg-45-45CR2_DB2.sql

4. Run C:\IBM\SQLLIB\BIN>db2 -td@ -vf C:\downloads\ic45CR2\metrics\METRICS-db-updateStats-45-45CR2_DB2.sql

5. Close out of the DB2 command window


5.2. Update the Cognos enterprise application (cognos.ear)

NOTE: If upgrading from CR2 to CR3, this Cognos update is not required, and may be skipped. It is required if upgrading to CR4 or CR5 from CR3 or below.

From you initial install of Connections, you should have a CognosConfig directory used to install Cognos. On my server it's in C:\downloads\ic45\IBM_Connections_4.5_win\IBM_Connections_Install_Windows\Cognos\CognosConfig

If not, get the cognosConfig directory from the Connection installation files and copy it to this server, update the cognos-setup.properties and copy the db2 jdbc libraries (db2jcc.jar and db2jcc_license_cu.jar) to /CognosConfig/BI-Customization/JDBC

step 6 of this document will help you configure the cognos-setup.properties file (http://www-10.lotus.com/ldd/lcwiki.nsf/xpDocViewer.xsp?lookupName=IBM+Connections+4.5+Documentation#action=openDocument&res_title=Installing_Cognos_Business_Intelligence_components_ic45&content=pdcontent )

Copy the files downloaded earlier (in :\downloads\ic45CR2\metrics) to their correct directory

1. Copy configBI.bat to CognosConfig/bin

2. Copy lc.metrics.cognos.install.jar to CognosConfig/lib

3. Copy MetricsPkg.zip to CognosConfig/MetricsPkg

4. Copy lc.metrics.cognos.api.jar to CognosConfig/BI-Customization/JAR

5. Copy MetricsTrxCube.mdl to CognosConfig/models

6. Copy cognos-installation-verify.bat to CognosConfig

7. Run C:\downloads\ic45\IBM_Connections_4.5_win\IBM_Connections_Install_Windows\Cognos\CognosConfig>cognos-setup-update.bat

This creates an update cognos.ear in the Cognos BI server directory (C:\IBM\Cognos\BI) next we will update the existing ear with this new one.

8. Open a browser to the IBM Integrated Solutions Console (http://server.swg.usma.ibm.com:9060/ibm/console) and login

9. Go to Application - Application Types - WebSphere Enterprise Applications, select Cognos and click Update

10. Under Replace the entire application - Browse to C:\IBM\Cognos\BI\cognos.ear and click Open

11. Click Next

12. Click Next

13. Leave all the defaults and click Next

14. I made sure the application was mapped to the cognos_server and the webserver

15. Click Finish

16.

17. Once saved, monitor the nodeagent systemOut.log for the following message
ADMA7021I: Distribution of application IBM Cognos completed successfully.

18. Stop cognos_server

19. Start cognos_server


5.3. Update the Cognos reports

20. Run C:\IBM\Cognos\BI\bin64>cogconfigw.exe

21. Go to Security - Authentication - Cognos and set Allow anonymous access? to True

22.

23. Close the IBM Cognos Configuration tool

24. Stop Cognos by running C:\IBM\WebSphere\AppServer\profiles\AppSrv02\bin\stopserver.bat cognos_server -username localadmin -password password

25. Start Cognos by running: C:\IBM\WebSphere\AppServer\profiles\AppSrv02\bin\startserver.bat cognos_server

26. Run C:\downloads\ic45\IBM_Connections_4.5_win\IBM_Connections_Install_Windows\Cognos\CognosConfig>cognos-configure-update.bat

27. Open a browser to http://server.swg.usma.ibm.com:9083/cognos/servlet/dispatch/ext and login with the cognos administrator

28. Click On IBMConnectionsMetrics - Metrics - community - peopleTheme. You should get a list like this. If the command above failed, this folder would only have 4 reports listed, instead of the longer list below:

29. Go to Launch - Administration

30. Once in the Administration page, click Log On

31. Your name should appear at the top right, Go to Security, and click on Cognos

32. Click the properties link next to IBMConnectionsMetricsAdmin

33. Click the Members tab then select Add..

34.

35. Add anyone to this group that needs the ability to run global metrics, as well as the connections admin account

36.

37.

38. Log off

39. Run C:\IBM\Cognos\BI\bin64>cogconfigw.exe

40. Go to Security - Authentication - Cognos and set Allow anonymous access? to False

41.

42. Close the IBM Cognos Configuration tool

43. Stop Cognos by running C:\IBM\WebSphere\AppServer\profiles\AppSrv02\bin\stopserver.bat cognos_server -username localadmin -password password

44. Start Cognos by running: C:\IBM\WebSphere\AppServer\profiles\AppSrv02\bin\startserver.bat cognos_server

45. Run C:\downloads\ic45\IBM_Connections_4.5_win\IBM_Connections_Install_Windows\Cognos\CognosConfig>cognos-configure-update.bat

46. Finally run C:\IBM\Cognos\Transformer\metricsmodel>build-all.bat


47. Verification

  1. Verify cognos-configure.log and cognos-setup.log files do not have an errors
  2. Verify the following exist in
    http://CognosServer:port/cognos/servlet/dispatch/ext

Document information

More support for: IBM Connections
Content Manager

Software version: 4.5

Operating system(s): AIX, Linux, Windows

Reference #: 1655425

Modified date: 17 August 2014


Translate this page: