Upgrade to IBM Connections 5.5 CR2 from IBM Connections 5.5 CR1 With Connections Content Manager (CCM)

Transcription

1 Upgrade to IBM Connections 5.5 CR2 from IBM Connections 5.5 CR1 With Connections Content Manager (CCM) /19/2016 Page 1

2 Summary Upgrade to IBM Connections 5.5 CR2 (with CCM) 1 Introduction Part Numbers & Fixes Install IBM Connections 5.5 CR Upgrade to the latest version of Installation Manager Install WebSphere Application Server FP Stop all WAS and HTTP processes Apply WebSphere Application Server FP Restart Deployment Manager and HTTP processes Install IBM Connections 5.5 CR Prepare IBM Connections 5.5 CR2 repository Update IBM Connections to CR Deploy updated applications Update IBM Connections databases Clean-up temporary folders Restart IBM Connections Upgrade FileNet components Backup DB2 FNOS and FNGCD (Object Store and GCD) Prepare FileNet installation packages Upgrade Content Engine Server Upgrade CE Client and FNCS /19/2016 Page 2

3 1 Introduction This document illustrates the steps followed by one administrator to apply IBM Connections 5.5 CR2 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.5 for documentation and complete steps. Important: For customers who customize Freemarker Template files, refer to Technote ( Freemarker Template files are overwritten during IBM Connections CR2 install ) before installing IC 5.5 CR2. The installation in this document is from IC 5.5 CR1 to IC 5.5 CR2. There are database schema changes and updates to FileNet when upgrading from IC 5.0 CR1. Cognos Metric customers who are upgrading from IC 5.5 or above to IC 5.5 CR2 need to refer to technote for additional steps when upgrading. Customers that use IBM Communities Surveys are required to update the Waltz and Sonata jars on the FEB Server due to changes in IC 5.5 CR2 Sonata services. Refer to technote for additional steps when upgrading. 2 Part Numbers & Fixes The following fixes have been downloaded: IBM WebSphere Application Server Network Deployment V Fix Pack 9 Technote /19/2016 Page 3

4 IBM Connections 5.5 requirements for IBM FileNet for use with Connections Content Manager (CCM) Technote Installation Manager or above Technote IBM Connections 5.5 CR2 Fix Central download link for the 5.5 CR2 package ( IC-Multi-CR02-LO89068) Updating the IBM Connections 5.5 databases to the required schema versions for Cumulative Refresh 2 (CR2) Technote 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-FP9 IC-CR2 FILENETCR 3 Install IBM Connections 5.5 CR2 This step will guide you through the installation of IBM Connections 5.5 CR2. This installation mainly consists on the four following steps: Upgrade to the latest version of Installation Manager 12/19/2016 Page 4

5 Upgrade to WebSphere Application Server (FP9) Install IBM Connections 5.5 CR2 Apply FileNet Updates 3.1 Upgrade to the latest version of Installation Manager Upgrade to the IBM Installation Manager or above (64 bit) 3.2 Install WebSphere Application Server FP 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 password stopnode.bat -username wasadmin -password password cd C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin stopmanager.bat -username wasadmin -password password 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 V Apply WebSphere Application Server FP9 Run Installation Manager and update the WebSphere Application Server to 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 12/19/2016 Page 5

6 3.3 Install IBM Connections 5.5 CR2 IC 5.5 CR2 Install: For customers who customize Freemarker Template files, refer to Technote ( Freemarker Template files are overwritten during IBM Connections CR2 install ) before installing IC 5.5 CR Prepare IBM Connections 5.5 CR2 repository Go to C:\Install\CONNECTIONS-CR\IC-CR2 Unzip the file IC-Multi-CR02-LO89068.zip into the same folder. 12/19/2016 Page 6

7 3.3.2 Update IBM Connections to CR2 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\ IC-Multi-CR02-LO89068\Updates\repository.config Click OK. Click Update. 12/19/2016 Page 7

8 Select IBM Connections then click Next. Check that Version _CR2 is displayed then click Next. Accept the license terms and click Next. 12/19/2016 Page 8

9 Ensure that ALL applications are selected then click Next. 12/19/2016 Page 9

10 Enter the administrative id and password then click Validate then OK. When the Vaildation is successful, click Next. 12/19/2016 Page 10

11 Click the Update button and begin the installation 12/19/2016 Page 11

12 Click Finish Upgrade to IBM Connections 5.5 CR2 (with CCM) Close Installation Manager 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. Wait for the CPU activity to be flat before going further. 12/19/2016 Page 12

13 3.3.4 Update IBM Connections databases Go to C:\Install\CONNECTIONS-CR\IC-CR2. Unzip the file 55cr2-database-updates.zip into the same folder. Go to C:\Install\CONNECTIONS-CR\IC-CR2\55cr2-database-updates\50cr2-databaseupdates\From-55 CR1\db2. Rename the file readme-db2-updates-from-55cr1.txt to readme-db2-updates-from- 55CR1.bat. 12/19/2016 Page 13

14 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-CR2\55cr2-database-updates\55cr2-database-updates\From- 55CR1\db2 readme-db2-updates-from-55cr1.bat Review the output from the scripts to verify there are no errors and close the DB2 Command prompt window. 12/19/2016 Page 14

15 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 password Remove temporary WebSphere Application Server directories such as the app_server_root/profiles/appsrv01/temp directory. Remove the contents of the folder temp Start the node agent and resync the applications cd c:\ibm\websphere\appserver\profiles\appsrv01\bin startnode.bat Note: It is important to resync the applications prior to starting the application server Perform a full synchronization to push the update to all nodes. Wait for the CPU activity to be flat before going further 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. 12/19/2016 Page 15

16 3.4 Upgrade FileNet components 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 password stopnode.bat -username wasadmin -password password cd c:\ibm\websphere\appserver\profiles\dmgr01\bin stopmanager.bat -username wasadmin -password password 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. 12/19/2016 Page 16

17 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 Prepare FileNet installation packages Go to C:\Users\IBM_ADMIN\DownloadDirector\ unzip the following files into the same folder: PBCE-WIN-FP004.zip PBCPE-Client-WIN-FP004.zip ICN-FP007-WIN.ZIP Copy the three following files into folder C:\Install\CONNECTIONS-CR\FileNetCR: P8CPE-CLIENT-WIN-FP004.EXE P8CPE-WIN-FP004.EXE IBM_CONTENT_NAVIGATOR FP007-WIN.exe Upgrade Content Engine Server Make sure the DMGR, nodeagents and Connections nodes are all running Open a command prompt window from the following directory: C:\IBM\Connections\FileNet.update\scripts and issue the following commands Run the script with the following parameters to back up the Deployment Manager profile. 12/19/2016 Page 17

18 backup.bat -conn.home.location=c:\ibm\connections 12/19/2016 Page 18

19 Run the script with the following parameters to update the FileNet Content Engine server. If you don't append these parameters, you are prompted for them while the update script runs. update-ce.bat -was.dm.path=c:\ibm\websphere\appserver\profiles\dmgr01 - was.admin.user=wasadmin -was.admin.password=password - conn.home.location=c:\ibm\connections -ce.fp.installer.location=c:\filenetfixpack\ p8cpe- WIN-FP004.EXE NOTE: This part took about minutes to complete Monitor C:\IBM\Connections\fileNet.update\scripts\fn-ce-update.log for progress on the install The following message in the logs is generated when the update has completed successfully. IBM FileNet Content Engine have been upgraded successfully. 12/19/2016 Page 19

20 Verify the CE upgrade was successful Go to C:\IBM\Connections\FileNet\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 Upgrade CE Client and FNCS Make sure the DMGR, Connections Application Servers and Connections nodes are all running Open a command prompt window from the following directory: C:\IBM\Connections\FileNet.update\scripts And issue the following command: update-fncs-ceclient.bat -was.dm.path=c:\ibm\websphere\appserver\profiles\dmgr01 -was.admin.user=wasadmin -was.admin.password=password - conn.home.location=c:\ibm\connections -dosetanonymous=n - fncs.fp.installer.location=c:\filenetfixpack\ibm_content_navigator FP007-WIN.exe -ceclient.fp.installer.location=c:\filenetfixpack\ p8cpe- CLIENT-WIN-FP004.EXE 12/19/2016 Page 20

21 Note : If you set dosetanonymous to 'y' or 'Y', you must also specify anonymous_user and anonymous_password. If you set dosetanonymous to 'n' or 'N', you do not need to specify anonymous_user and anonymous_password. 12/19/2016 Page 21

22 Verify the CE Client and FNCS upgrade completed successfully Open ce_version.txt in C:\IBM\Connections\FileNet\CEClient Verify the Content Navigator, use the following URL: <yourserver>(port if required)/dm Check the FileNet Collaboration Services (Content Navigator) log file (version.txt) for errors which is located in the folder C:\IBM\Connections\FNCS 12/19/2016 Page 22

23 Congratulations! You have upgraded IBM Connections 5.5 to CR2! 12/19/2016 Page 23