Vous êtes sur la page 1sur 50

Upgrade to IBM Connections 5.

0 CR4 (with CCM)

Upgrade to IBM
Connections 5.0 CR4 from
IBM Connections 5.0 CR3
With Connections Content
Manager (CCM)

2016-03-10

3/2016 Page 1
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Summary
1 Introduction .............................................................................................................................. 3
2 Part Numbers & Fixes .............................................................................................................. 3
3 Install IBM Connections CR4 .................................................................................................... 5
3.1 Upgrade to the latest version of Installation Manager ................................................... 5
3.1.1 Prepare IM installation package ........................................................................ 5
3.1.2 Install Installation Manager ................................................................................ 5
3.2 Install WebSphere Application Server 8.5.5 FP7 .......................................................... 8
3.2.1 Stop all WAS and HTTP processes ................................................................... 8
3.2.2 Prepare WAS FP4 installation packages TBU ................................................... 8
3.2.3 Apply WebSphere Application Server 8.5.5 FP7 ............................................. 11
3.2.4 Restart Deployment Manager and HTTP processes........................................ 19
3.3 Install IBM Connections 5.0 CR4 ................................................................................ 19
3.3.1 Prepare IBM Connections 5.0 CR4 repository ................................................. 19
3.3.2 Update IBM Connections to CR4..................................................................... 20
3.3.3 Deploy updated applications ........................................................................... 25
3.3.4 Update IBM Connections databases ............................................................... 26
3.3.5 Clean-up temporary folders ............................................................................. 29
3.3.6 Restart IBM Connections ................................................................................ 29
3.3.7 Update the CCM Domain ................................................................................ 30
3.4 Upgrade FileNet components ..................................................................................... 32
3.4.1 Backup DB2 FNOS and FNGCD (Object Store and GCD) .............................. 32
3.4.2 Prepare FileNet installation packages ............................................................. 33
3.4.3 Upgrade Content Engine Server...................................................................... 34
3.4.4 Map Filenet engine back to HTTP server ........................................................ 38
3.4.5 Upgrade CE Client and FNCS ......................................................................... 43
3.4.6 Map Navigator back to HTTP Server ............................................................... 45
3.4.7 Verify the CE Client and FNCS upgrade worked ............................................. 49

3/2016 Page 2
Upgrade to IBM Connections 5.0 CR4 (with CCM)

1 Introduction
This document illustrates the steps followed by one administrator to apply IBM
Connections 5.0 CR4 where everything is installed on a single Windows 2012 server.
The environment being upgraded is a test environment, so not sized for production.
Refer to Update strategy for IBM Connections 5.0 for documentation and complete
steps.

The installation in this document is from IC 5.0 CR3 to IC 5.0 CR4. There are no
database schema changes or updates to FileNet when upgrading from IC 5.0 CR3.
There additional steps that are needed to upgrade from IC 5.0 to IC 5.0 CR4 are noted
in the document.

Cognos Metric customers who are upgrading from IC 5.0 to IC 5.0 CR4 need to refer to
technote 1696033 for additional steps when upgrading.

2 Part Numbers & Fixes


The following fixes have been downloaded:

 IBM WebSphere Application Server Network Deployment V8.5.5. Fix Pack 7


Technote 4040533

3/2016 Page 3
Upgrade to IBM Connections 5.0 CR4 (with CCM)

 IBM Connections 5.0 requirements for IBM FileNet for use with Connections Content
Manager (CCM) (No updates since IC 5.0 CR3)

Technote 1683147

IC 5.0 GA Upgrade: Upgrading from IC 5.0 GA requires additional FileNet component


files (the files are highlighted in blue in the screenshot above). The additional
requirements are:

IBM Content Navigator 2.0.3

IBM FileNet Content Engine Server 5.2.1

IBM FileNet Content Engine Client 5.2.1

 Installation Manager 1.8.0 (No updates since IC 5.0 CR1)

http://ibm.co/1sdInra

Note: This is the 32 bits version of Installation Manager.

 IBM Connections 5.0 CR4


Fix Central download link for the 5.0 CR4 package (5.0.0.0-IC-Multi-CR04-LO85990)

 Updating the IBM Connections 5.0 databases to the required schema versions for
Cumulative Refresh 3 (CR3) (No updates since IC 5.0 CR3)

Technote 1902944

3/2016 Page 4
Upgrade to IBM Connections 5.0 CR4 (with CCM)
It is assumed that that all installation packages have been copied into the folder
C:\Install\CONNECTIONS-CR with the following folder structure:

 IM

 WAS-FP7

 IC-CR4

 FILENETCR

3 Install IBM Connections CR4


This step will guide you through the installation of IBM Connections CR4.

This installation mainly consists on the four following steps:

 Upgrade to the latest version of Installation Manager (No updates since IC 5.0 CR1)

 Upgrade to WebSphere Application Server 8.5.5.7 (FP7)

 Install IBM Connections 5.0 CR4

 Apply FileNet Updates (No updates since IC 5.0 CR3)

3.1 Upgrade to the latest version of Installation Manager

This section is not required when upgrading from IC 5.0 CR3 to IC CR4

3.1.1 Prepare IM installation package

Go to C:\Install\CONNECTIONS-CR\IM.

Unzip the file agent.installer.win32.win32.x86_1.8.0.20140902_1503.zip into the same


folder.

3.1.2 Install Installation Manager

Go to C:\Install\CONNECTIONS-
CR\IM\agent.installer.win32.win32.x86_1.8.0.20140902_1503 and run install.exe.

3/2016 Page 5
Upgrade to IBM Connections 5.0 CR4 (with CCM)

Click Next.

Accept the license terms then click Next.

3/2016 Page 6
Upgrade to IBM Connections 5.0 CR4 (with CCM)

Click Install.

3/2016 Page 7
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Click Restart Installation Manager.

Close Installation Manager.

3.2 Install WebSphere Application Server 8.5.5 FP7

3.2.1 Stop all WAS and HTTP processes

To stop all WAS processes, open a Command prompt window then issue the following
commands:

cd C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
stopServer.bat Connections_server1 -username wasadmin -password Passw0rd
stopNode.bat -username wasadmin -password Passw0rd

cd C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin
stopManager.bat

Stop all Java processes on the system that might be locking files

Stop the HTTP services:

 IBM HTTP Administration for WebSphere Application Server V8.5

 IBM HTTP Server V8.5

3.2.2 Prepare WAS FP4 installation packages TBU

Go to C:\Install\CONNECTIONS-CR\WAS-FP7.

3/2016 Page 8
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Create 2 subfolders within folder C:\Install\CONNECTIONS-CR\WAS-FP7:

 WASND_855_FP7

 WASND_855_SUPP_FP7

Note: We strongly advise you to proceed sequentially as you can easily mix up
distribution packages.

The following table shows where to unzip each .ZIP file located into
C:\Install\CONNECTIONS-CR\WAS-FP7:

ZIP File Destination


8.5.5-WS-WAS-FP0000007-part1.zip WASND_855_FP7
8.5.5-WS-WAS-FP0000007-part2.zip WASND_855_FP7

8.5.5-WS-WASSupplements-FP0000007-part1.zip WASND_855_SUPP_FP7
8.5.5-WS-WASSupplements-FP0000007-part2.zip WASND_855_SUPP_FP7

3/2016 Page 9
Upgrade to IBM Connections 5.0 CR4 (with CCM)
During the extraction, when the system asks you to merge the native folder click Yes.

At the end, you should see the following:

In folder WASND_855_FP7:

3/2016 Page 10
Upgrade to IBM Connections 5.0 CR4 (with CCM)
In folder WASND_855_SUPP_FP7:

3.2.3 Apply WebSphere Application Server 8.5.5 FP7

Run Installation Manager and select File then Preferences...

Click Add Repository...

3/2016 Page 11
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Select repository C:\Install\CONNECTIONS-CR\WAS-
FP4\WASND_855_FP7\repository.config then click OK.

Repeat the steps above to select C:\Install\CONNECTIONS-CR\WAS-


FP4\WASND_855_SUPP_FP7\repository.config.

Click OK.

3/2016 Page 12
Upgrade to IBM Connections 5.0 CR4 (with CCM)

Select Update.

Select IBM WebSphere Application Server V8.5 then click OK

Note: Do not select “Update all packages…” you may upgrade more than what is required

3/2016 Page 13
Upgrade to IBM Connections 5.0 CR4 (with CCM)

3/2016 Page 14
Upgrade to IBM Connections 5.0 CR4 (with CCM)
If a Password required window is displayed, click Cancel until it disappears.

Check that Version 8.5.5.7 is displayed then click Next.

3/2016 Page 15
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Accept the license terms then click Next.

Click Next.

3/2016 Page 16
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Click Update.

Click Finish once the update has completed

3/2016 Page 17
Upgrade to IBM Connections 5.0 CR4 (with CCM)

3/2016 Page 18
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Repeat previous steps for:

 IBM HTTP Server V8.5

 Web Server Plug-ins for IBM WebSphere Application Server V8.5

There may be additional screens. Accept the default values and click Next.

When you're done, keep Installation Manager open.

3.2.4 Restart Deployment Manager and HTTP processes

To start Deployment Manager, open a Command prompt window then issue the following
commands:

cd c:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin
startManager.bat

Start the HTTP services:

 IBM HTTP Administration for WebSphere Application Server V8.5

 IBM HTTP Server V8.5

3.3 Install IBM Connections 5.0 CR4

3.3.1 Prepare IBM Connections 5.0 CR4 repository

Go to C:\Install\CONNECTIONS-CR\IC-CR4

Unzip the file 5.0.0.0-IC-Multi-CR04-LO85990.zip into the same folder.

3/2016 Page 19
Upgrade to IBM Connections 5.0 CR4 (with CCM)
3.3.2 Update IBM Connections to CR4

Go back to Installation Manager and select File then Preferences...

Remove the existing repositories that were added for WAS.

Add the following repository:

C:\Install\CONNECTIONS-CR\5.0.0.0-IC-Multi-CR04-LO89550\Updates\repository.config

Click OK.

Click Update.

3/2016 Page 20
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Select IBM Connections then click Next.

Check that Version 5.0.0.0_CR4 is displayed then click Next.

3/2016 Page 21
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Accept the license terms and click Next.

Ensure that ALL applications are selected the click Next.

3/2016 Page 22
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Enter the administrative id and password then click Validate then OK. When the Vaildation is
successful, click Next.

3/2016 Page 23
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Click the Update button and begin the installation

3/2016 Page 24
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Click Finish

Close Installation Manager.

3.3.3 Deploy updated applications

Open a Command prompt window then issue the following commands:

cd c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
startNode.bat

This will deploy all IBM Connections applications to Connections node.

You can check if updated applications are deployed by going to


C:\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\connections5Cell01.

The modification date of applications should be updated to the current date/time.

3/2016 Page 25
Upgrade to IBM Connections 5.0 CR4 (with CCM)

Wait for the CPU activity to be flat before going further.

3.3.4 Update IBM Connections databases

Note: This section is not required when upgrading from IC 5.0 CR3 to IC 5.0 CR4
Go to C:\Install\CONNECTIONS-CR\IC-CR3.

Unzip the file 50cr3-database-updates.zip into the same folder.

Go to C:\Install\CONNECTIONS-CR\IC-CR3\50cr3-database-updates\50cr3-database-
updates\From-50 CR2\db2.

IC 5.0 GA Upgrade: Use the schema upgrades in the directory “From-50”when upgrading
from IC 5.0 GA and follow the same procedure. The bat file will be named readme-db2-
updates-from-50.bat.

Rename the file readme-db2-updates-from-50CR2.txt to readme-db2-updates-from-


50CR2.bat.

3/2016 Page 26
Upgrade to IBM Connections 5.0 CR4 (with CCM)
From the Windows Start menu, go to IBM DB2 DB2COPY (Default) then select Command
Window - Administrator.

From this window issue the following commands:

cd C:\Install\CONNECTIONS-CR\IC-CR3\50cr3-database-updates\50cr3-database-updates\From-
50CR2\db2
readme-db2-updates-from-50CR3.bat

3/2016 Page 27
Upgrade to IBM Connections 5.0 CR4 (with CCM)

Close the DB2 Command prompt window.

3/2016 Page 28
Upgrade to IBM Connections 5.0 CR4 (with CCM)

3.3.5 Clean-up temporary folders

Note: This is an important step and must be completed


Open a Command prompt window then issue the following commands:

cd c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
stopNode.bat -username wasadmin -password Passw0rd

Remove temporary WebSphere Application Server directories such as the


app_server_root/profiles/AppSrv01/temp directory.

Remove the contents of the folder temp

Note: It is important to resync the applications prior to starting the application server

Start the node agent and resync the applications

cd c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
startNode.bat

Perform a full synchronization to push the update to all nodes.

Wait for the CPU activity to be flat before going further.

3.3.6 Restart IBM Connections

Open a Command prompt window then issue the following commands:

cd c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin startServer.bat Connections_server1

Wait for the CPU activity to be flat before going further.

3/2016 Page 29
Upgrade to IBM Connections 5.0 CR4 (with CCM)
3.3.7 Update the CCM Domain

Important: Updating the CCM Domain is NOT required when upgrading from IC 5.0 CR3 to
CR4. It IS required when updating from 5.0 GA or CR1.

Make sure the DMGR, nodeagents and Connections nodes are all running

Still from the Command prompt window, issue the following commands:

cd C:\IBM\Connections\addons\ccm\ccmDomainTool

ccmUpdate.bat

When asked for the administrator user ID, just hit Enter to accept the default value
(wasadmin).

3/2016 Page 30
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Then enter wasadmin password (Passw0rd) and hit Enter.

Hit Enter to regenerate the file dminfo.properties.

Close the Command prompt window.

3/2016 Page 31
Upgrade to IBM Connections 5.0 CR4 (with CCM)
3.4 Upgrade FileNet components

Note: This section is not required when upgrading from IC 5.0 CR3 to IC 5.0 CR4

3.4.1 Backup DB2 FNOS and FNGCD (Object Store and GCD)

Stop all WAS processes, open a Command prompt window then issue the following
commands:

cd c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
stopServer.bat Connections_server1 -username wasadmin -password Passw0rd
stopNode.bat -username wasadmin -password Passw0rd
cd c:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin
stopManager.bat

Create a new folder on called 'FILENETbackup' (this is where the FNOS and GCD databases
will be saved/ backed up to).

From the Windows Start menu, go to IBM DB2 DB2COPY (Default) then select Command
Window - Administrator.

3/2016 Page 32
Upgrade to IBM Connections 5.0 CR4 (with CCM)
From this window issue the following commands:

db2 backup database FNOS to C:\FILENETbackup

Once this completes successfully issue the following command:

db2 backup database FNGCD to C:\FILENETbackup

close the window and verify the backup files are now in C:\FILENETbackup

3.4.2 Prepare FileNet installation packages

Important: See Technote 1968883 for upgrading FileNet Content Server in an environment
where WebSphere Application Serve is installed in a non-English locale

Go to C:\Users\IBM_ADMIN\DownloadDirector\

unzip the following files into the same folder:

 5.2.1.2-P8CE-WIN-FP002.zip

 5.2.1.2-PBCPE-Client-WIN-FP002.zip

 2.0.3-ICN-FP003-WIN.ZIP

Copy the three following files into folder C:\Install\CONNECTIONS-CR\FileNetCR3:

 5.2.1.2-P8CPE-CLIENT-WIN-FP002.EXE

 5.2.1.2-P8CPE-WIN-FP002.EXE

 IBM_CONTENT_NAVIGATOR-2.0.3.3-FP003-WIN.exe

IC 5.0 GA Upgrade: Upgrading from IC 5.0 GA requires additional FileNet component files
which needs to be copied in the folder. The additional requirements are:

IBM Content Navigator 2.0.3 (IBM_CONTENT_NAVIGATOR-2.0.3-WIN.exe)

IBM FileNet Content Engine Server 5.2.1 (5.2.1-P8CPE-WIN.exe)

IBM FileNet Content Engine Client 5.2.1 (files 5.2.1-P8CPE-CLIENT-WIN.exe)

3/2016 Page 33
Upgrade to IBM Connections 5.0 CR4 (with CCM)

3.4.3 Upgrade Content Engine Server

Make sure the DMGR, nodeagents and Connections nodes are all running
Open a command prompt window and issue the following commands
C:\IBM\Connections\ccm\ccm\ccm\scripts\backup.bat -was.dm.path
"C:\IBM\WebSphere\AppServer\profiles\Dmgr01" -was.admin.user localadmin -
was.admin.password password

3/2016 Page 34
Upgrade to IBM Connections 5.0 CR4 (with CCM)

C:\IBM\Connections\ccm\ccm\ccm\scripts\update-ce.bat -was.dm.path
"C:\IBM\WebSphere\AppServer\profiles\Dmgr01" -was.admin.user wpsadmin -
was.admin.password wpsadmin -ce.fp.installer.location C:\Install\CONNECTIONS-
CR\FileNetCR3\5.2.1.2-P8CPE-WIN-FP002.EXE

3/2016 Page 35
Upgrade to IBM Connections 5.0 CR4 (with CCM)

IC 5.0 GA Upgrade: When upgrading from IC 5.0 GA use the following command.
When prompted if FNCE has been upgraded to 5.2.1, enter n. Enter the location of the FNCE
Server 5.2.1 and then fixpack 5.2.1.2

NOTE: This part took about 40 – 60 minutes to complete


Monitor C:\IBM\Connections\ccm\ccm\ccm\scripts\ fn-ce-update.log for progress on the
install
The following message in the logs is generated when the update has completed
successfully.

3/2016 Page 36
Upgrade to IBM Connections 5.0 CR4 (with CCM)

3/2016 Page 37
Upgrade to IBM Connections 5.0 CR4 (with CCM)

3.4.4 Map Filenet engine back to HTTP server

Open a browser to the Integrated Solutions Console and login

Go to Applications - Application Types - WebSphere Enterprise Application and click on


FileNetEngine

Click on Manage Modules

3/2016 Page 38
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Select all Modules and map them to the cluster and webservers
Once all are mapped correctly, click OK

Save your changes

3/2016 Page 39
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Synch the Nodes

Start the NetEngine

3/2016 Page 40
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Go to Servers - Applications Server - Web servers
Select your web servers and click Generate plug-in

Select the webservers again, and click Propagate Plug-in to copy the plugin file to the http
server location

3/2016 Page 41
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Restart the IBM http Server

Verify the CE upgrade was successful

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


the engine version number :

Launch the browser and go to <your server>(port if required)/FileNet/Engine

The following page should be displayed. If not check that the FileNet app is started

3/2016 Page 42
Upgrade to IBM Connections 5.0 CR4 (with CCM)

3.4.5 Upgrade CE Client and FNCS

Make sure the DMGR, nodeagents and Connections nodes are all running
Open a Command prompt window and issue the following commands:

cd C:\IBM\Connections\ccm\ccm\ccm\scripts

update-fncs-ceclient.bat -was.dm.path "C:\IBM\WebSphere\AppServer\profiles\Dmgr01" -


was.admin.user wpsadmin -was.admin.password passw0rd -doInstallFNCS y -skipInstallFNCSBase y
-fncs.fp.installer.location "C:\Install\CONNECTIONS-CR\FileNetCR3\IBM_CONTENT_NAVIGATOR-
2.0.3.3-FP003-WIN.EXE" -doInstallCEClient y -ceclient.fp.installer.location "
C:\Install\CONNECTIONS-CR\FileNetCR3\5.2.1.2-P8CPE-CLIENT-WIN-FP002.EXE" -supportIBMDocs
n

Note : This example has –supportIBMDocs n, depending on your configuration you may
need to set this to y.

3/2016 Page 43
Upgrade to IBM Connections 5.0 CR4 (with CCM)
IC 5.0 GA Upgrade: Set ‘-skipInstallFNCSBase n’ and enter the location of the ICN 2.0.3
install file. The following is an example of running the update-fncs-ceclient.bat when
upgrading from 5.0 GA.

update-fncs-ceclient.bat -was.dm.path "C:\IBM\WebSphere\AppServer\profiles\Dmgr01" -


was.admin.user wpsadmin -was.admin.password passw0rd -doInstallFNCS y -skipInstallFNCSBase n
-fncs.installer.location C:\Install\CONNECTIONS-CR\FileNetCR3\IBM_CONTENT_NAVIGATOR-2.0.3-
WIN.EXE" -fncs.fp.installer.location "C:\Install\CONNECTIONS-
CR\FileNetCR3\IBM_CONTENT_NAVIGATOR-2.0.3.3-FP003-WIN.EXE" -doInstallCEClient y -
ceclient.fp.installer.location " C:\Install\CONNECTIONS-CR\FileNetCR3\5.2.1.2-P8CPE-CLIENT-WIN-
FP002.EXE" -supportIBMDocs n

This screenshot is an example of each of the prompts for update-fncs-ceclient.bat when


upgrading from 5.0 GA.

3/2016 Page 44
Upgrade to IBM Connections 5.0 CR4 (with CCM)
3.4.6 Map Navigator back to HTTP Server

Open a browser to the Integrated Solutions Console and login


Go to Applications - Application Types - WebSphere Enterprise Application and click on
Navigator

Click on Manage modules.

Select IBM FileNet Collaboration Services

3/2016 Page 45
Upgrade to IBM Connections 5.0 CR4 (with CCM)

Within list Clusters and servers, select ConnectionsCluster and webserver1 then click Apply

The module must now be mapped with both ConnectionsCluster and webserver1.

Click OK.

Click Save

3/2016 Page 46
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Click OK

Go to Servers > Clusters > WebSphere application server clusters then stop and start
ConnectionsCluster.

3/2016 Page 47
Upgrade to IBM Connections 5.0 CR4 (with CCM)
Go to Servers - Applications Server - Web servers
Select your web servers and click Generate plug-in

Select the webservers again, and click Propagate Plug-in to copy the plugin file to the http
server location

Restart HTTP services.

3/2016 Page 48
Upgrade to IBM Connections 5.0 CR4 (with CCM)

3.4.7 Verify the CE Client and FNCS upgrade worked

Verify the ContentEngine here: <yourserver>/Filenet/Engine

Verify FNCS here <yourserver>/dm

3/2016 Page 49
Upgrade to IBM Connections 5.0 CR4 (with CCM)

Congratulations! You have upgraded IBM Connections to CR4!

3/2016 Page 50

Vous aimerez peut-être aussi