Upgrade to IBM Connections 6.0 CR2 from IBM Connections 6.0 CR1 and IFR1 With Connections Content Manager (CCM)

Transcription

1 Upgrade to IBM Connections 6.0 CR2 from IBM Connections 6.0 CR1 and IFR1 With Connections Content Manager (CCM) 6/25/2018 Page 1

2 6/25/2018 Page 2

3 Summary 1 Introduction Part Numbers & Fixes Install IBM Connections 6.0 CR Upgrade to version bit of Installation Manager Install WebSphere Application Server FP13 and Java SDK Stop all WAS and HTTP processes Prepare Installation Packages Apply WebSphere Application Server FP Apply IBM WebSphere Java SDK for WebSphere Application Server V & ifix PI94837 for APAR IJ Restart Deployment Manager and HTTP processes Install IBM Connections 6.0 CR Prepare IBM Connections 6.0 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 Switch to Java 6 to upgrade FileNet Upgrade Content Engine Server Upgrade CE Client Switch to Java 8 after upgrading FileNet /25/2018 Page 3

4 1 Introduction This document illustrates the steps followed by one administrator to apply IBM Connections 6.0 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 6.0 for documentation and other important information. The installation in this document is from IC 6.0 CR1 or IC 6.0 IFR1 to IC 6.0 CR2. There are five database schema updates for IC 6.0 CR2. There are no FileNet component updates. What is IBM Connection V6.0 IFR1? IBM Connections has delivered an interim release for IBM Connections v6 (April, 2018) that removes Cognos Business Intelligence v as a supporting program from the Connections License. The reason for the update is that IBM Cognos Business Intelligence v10.2.x is reaching End of Support. IBM Connections V6.0 IFR1 has replaced IBM Connections 6.0 GA on Passport Advantage (see table below for part numbers). IC V6.0 IFR1 includes IC 6.0 CR1 so there is no need to apply the CR or database schema updates after installation. For more information on Metrics support in IBM Connections 6.0 refer to document IBM Connections 6 Metrics update (Technote ). IBM Connections V6.0 IFR1 Passport Advantage Part Numbers: Description IBM Connections V6.0 IFR1 for Windows Multilingual IBM Connections V6.0 IFR1 for AIX Multilingual IBM Connections V6.0 IFR1 for Linux Multilingual IBM Connections V6.0 IFR1 Linux for System z Multilingual IBM Connections V6.0 IFR1 Wizard for Windows Multilingual IBM Connections V6.0 IFR1 Wizard for Linux, AIX Multilingual Part Numbers CNS97ML CNS98ML CNS99ML CNS9AML CNS9BML CNS9CML Important Updates: Review Install / Rollback for IBM Connections 6.0 CR2 with the <loginredirectwhitelist> LCC.xml setting (Technote ) to prevent Install and rollback failures. There are additional steps required before IC 6.0 CR1 can be rollbacked or rolling back to 6.0 when Metrics is installed. Refer to Rollback for IBM Connections 6.0 CR1 with Metrics for more details. IBM Connections 6.0 CR1 implemented additional security measures for custom and third party widgets which requires them to be registered in the Widget Container. Refer to IBM Connections 6.0 CR1 requires all widgets to be registered in the Widget Container (Technote ) for more details. 6/25/2018 Page 4

5 2 Part Numbers & Fixes The following fixes have been downloaded: 1. IBM WebSphere Application Server Network Deployment V8.5.5 Fix Pack 13 Technote The IBM WebSphere Java SDKs for WebSphere Application Server is Technote Required ifixes: Before upgrading to WAS or higher when using the Domino LDAP contact IBM WebSphere Support to obtain the following ifix - PI88438: When defining a root Base DN for a federated repository, display and login problems occur. Otherwise the server will experience login failures. IBM Connections 6.0 requires ifix PI94837 for APAR IJ04429 for SDK The ifix can be downloaded from Fix Central refer to the following technote for details PI94837: SHIP IBM Java SDK 8 IJ04429 AS AN IFIX FOR WAS (technote ) 6/25/2018 Page 5

6 2. IBM Connections 6.0 requirements for IBM FileNet for use with Connections Content Manager (CCM) (There are no FileNet updates for IC 6.0 CR2) IBM Connections 6.0 CR requirements for IBM FileNet for use with Connections Content Manager (CCM) (Technote ) Download table for IC 6.0 CR1: FileNet Component AIX Linux Windows FileNet Content Engine Server FileNet Content Engine Client P8CE-AIX- FP P8CPE-Client- AIX-FP P8CPE-LINUX- FP P8CPE-Client- Linux-FP P8CPE-WIN- FP P8CPE-Client- WIN-FP007 IBM Content Navigator ICN-FP008-AIX ICN-FP ICN-FP008-WIN (FileNet Collaboration Services (FNCS)) LINUX ** IC 6.0 CR1 does not require an update to ICN however there is a requirement to have the binary file available to update the FNCE Client. 3. Installation Manager or above (No updates since IC 6.0) Installation Manager and Packaging Utility download documents (Technote ) 4. IBM Connections 6.0 CR2 Fix Central download link for the IC 6.0 CR2 package ( IC-Multi-CR02- LO93505) 5. Updating the IBM Connections 6.0 databases to the required schema versions for Cumulative Refresh 2 (CR2) Updating the IBM Connections 6.0 databases to the required schema versions for Cumulative Refresh 2 (CR2) (Technote ) 6/25/2018 Page 6

7 It is assumed that all installation packages have been copied into the folder C:\Install\CONNECTIONS-CR with the following folder structure: IM (if needed) WAS IC-CR o WS-WAS-FP13 o WS-WASSupplements-FP13 o WS-IBMWASJAVA-platform o WS-WASJavaSDK8-platform-IFPI94837 FileNet (This is not required when upgrading from IC 6.0 CR1 or IC 6.0 IFR1 to IC 6.0 CR2) 3 Install IBM Connections 6.0 CR2 This step will guide you through the installation of IBM Connections 6.0 CR2. This installation mainly consists on the four following steps: Upgrade to the latest version of Installation Manager (if needed) Upgrade to WebSphere Application Server / SDK / ifix Install IBM Connections 6.0 CR2 Apply FileNet Updates (not required for IC 6.0 CR2) 3.1 Upgrade to version bit of Installation Manager If your server hasn t upgraded to IM bit or future fix packs please do so 3.2 Install WebSphere Application Server FP13 and Java SDK 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 6/25/2018 Page 7

8 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 Prepare Installation Packages Go to the C:\Install\Connections-CR\WAS directory and extract the installation files that were downloaded earlier. The directories should be like so: Apply WebSphere Application Server FP13 Run Installation Manager and select File then Preferences Click Add Repository Select the repository \8.5.5-WS-WAS-FP013\repository.config then click OK 6/25/2018 Page 8

9 Repeat the steps above to select C:\Install\Connections-CR\WAS\8.5.5-WS- WASSupplements-FP013\repository.configthen click OK Click OK Select Update 6/25/2018 Page 9

10 Select IBM WebSphere Application Server v8.5 then click Next Select Version then Next Note: do not select Update all packages you may upgrade more than what is required If a Password required window is displayed, click Cancel until it disappears 6/25/2018 Page 10

11 Accept the license terms click Next Click Next Click Next 6/25/2018 Page 11

12 Click Update 6/25/2018 Page 12

13 Click Finish Repeat previous steps for: IBM HTTP Server v8.5 Web Server Plugins for 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 6/25/2018 Page 13

14 3.2.4 Apply IBM WebSphere Java SDK for WebSphere Application Server V & ifix PI94837 for APAR IJ04429 From the Installation Manager select File then Preferences Click Add Repository Select the repository \WAS\ WS-IBMWASJAVA-Win then click OK Repeat the steps above to select \WAS\ WS-WASJavaSDK8-WinX64-IFPI94837 Click OK 6/25/2018 Page 14

15 Select Update Select IBM WebSphere Application Server v8.5 then click Next Note: do not select Update all packages you may upgrade more than what is required If a Password required window is displayed, click Cancel until it disappears Check the Version is displayed then click Next 6/25/2018 Page 15

16 Select the ifix WS-WASJavaSDK8-WinX64-IFPI94837 then click Next Click Update 6/25/2018 Page 16

17 Click Finish 6/25/2018 Page 17

18 3.2.5 Restart Deployment Manager and HTTP processes Before starting the Dmgr change SOAP Request Timeout to com.ibm.soap.requesttimeout=0 in the soap.client.props file to ensure that no requests timeout during a CR install. 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 Node cd c:\ibm\websphere\appserver\profiles\appsrv01\bin startnode.bat Start the HTTP services: IBM HTTP Administration for WebSphere Application Server V8.5 IBM HTTP Server V8.5 Confirm that the WebSphere components have been updated. From the Install Manager select File, View Installed Packages: The Web Server now should be at in the WebSphere Integrated Solutions Console: The log for the Deployment Manager should be at the following: ************ Start Display Current Environment ************ WebSphere Platform [ND cf ] [IBMJAVA cf ] running with process name IC6SQLCell01\IC6SQLCellManager01\dmgr and process id 6236 Host Operating System is Windows Server 2016, version 10.0 Java version = 1.8.0_151, Java Runtime Version = pwa6480sr5fp6ifix _01(sr5 FP6+IJ04429), Java Compiler = j9jit29, Java VM name = IBM J9 VM 6/25/2018 Page 18

19 3.3 Install IBM Connections 6.0 CR2 The DMGR should be running and the Node should be stopped Prepare IBM Connections 6.0 CR2 repository Go to C:\Install\CONNECTIONS-CR\IC-CR Unzip the file IC-Multi-CR02-LO93505.zip into the same folder. 6/25/2018 Page 19

20 3.3.2 Update IBM Connections to CR2 In the Installation Manager and select File then Preferences... Add the following repository: C:\Install\CONNECTIONS-CR\IC-CR\ IC-Multi-CR02- LO93505\Updates\repository.config Click OK. Click Update. 6/25/2018 Page 20

21 Select IBM Connections then click Next. Check that Version _CR2 is displayed then click Next. 6/25/2018 Page 21

22 Accept the license terms and click Next. Ensure that ALL applications are selected then click Next. 6/25/2018 Page 22

23 Enter the administrative id and password then click Validate then OK. When the Validation is successful, click Next. 6/25/2018 Page 23

24 Click the Update button and begin the installation 6/25/2018 Page 24

25 Click Finish 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\<CellName> The modification date of applications should be updated to the current date/time. Verify that the CR was successfully installed. Go to \IBM\Connections and open Version.txt to confirm the CR build number. IC 6.0 CR2 build number: IC6.0_CR2_Connections_ Wait for the CPU activity to be flat before going further. 6/25/2018 Page 25

26 3.3.4 Update IBM Connections databases Go to C:\Install\CONNECTIONS-CR\IC-CR Unzip the file 60cr2-database-updates.zip into the same folder. Go to C:\Install\CONNECTIONS-CR\IC-CR\60cr2-database-updates\60cr2-databaseupdates\From-60CR1_IFR1\db2. 6/25/2018 Page 26

27 Rename the file readme-db2-updates-from-60cr1.txt to readme-db2-updates-from- 60CR1.bat. 6/25/2018 Page 27

28 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-CR\60cr2-database-updates\From-60CR1\db2 readme-db2-updates-from-60cr1.bat Review the output from the scripts to verify there are no errors and close the DB2 Command prompt window. 6/25/2018 Page 28

29 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. 6/25/2018 Page 29

30 3.4 Upgrade FileNet components Note: This section is not required when upgrading from IC 6.0 CR1 or IC 6.0 IFR1 to IC 6.0 CR 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. 6/25/2018 Page 30

31 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 6/25/2018 Page 31

32 3.4.2 Prepare FileNet installation packages Go to C:\Users\IBM_ADMIN\DownloadDirector\ unzip the following files into the same folder: P8CPE-WIN-FP007.zip P8CPE-Client-WIN-FP007.zip ICN-FP008-WIN.ZIP Copy the three following files into folder C:\Install\CONNECTIONS-CR\FileNetCR: P8CPE-CLIENT-WIN-FP008.EXE P8CPE-WIN-FP008.EXE IBM_CONTENT_NAVIGATOR FP008-WIN.exe IC 6.0 CR1 does not require an update to ICN however there is a requirement to have the binary file available to update the FNCE Client. 6/25/2018 Page 32

33 3.4.3 Switch to Java 6 to upgrade FileNet Make sure deployment manager and the node agents are running and the Connections server is not running Open a Command prompt window then issue the following commands: cd c:\ibm\websphere\appserver\profiles\dmgr01\bin managesdk -listenabledprofileall This command will list the current SDKs for WebSphere managesdk -enableprofile -profilename Dmgr01 -sdkname 1.6_64 The following commands will switch the SDK to 1.6_64 Stop and restart the Dmgr by running the following commands: stopmanager.bat -username wasadmin -password password startmanager.bat cd c:\ibm\websphere\appserver\profiles\appsrv01\bin managesdk -enableprofile -profilename AppSrv01 -sdkname 1.6_64 6/25/2018 Page 33

34 Next perform a FullSync in the WebSphere Integrated Solutions Console by going to the System Administration > Nodes and selecting the the Full Resynchronize button. Run the following command to confirm that all profiles are set to SDK 1.6_64 managesdk -listenabledprofileall 6/25/2018 Page 34

35 Restart the Deployment manager, nodeagents and the Connections nodes by running the following commands: cd c:\ibm\websphere\appserver\profiles\appsrv01\bin stopnode.bat -username wasadmin -password password cd c:\ibm\websphere\appserver\profiles\dmgr01\bin stopmanager.bat -username wasadmin -password password cd c:\ibm\websphere\appserver\profiles\dmgr01\bin startmanager.bat cd c:\ibm\websphere\appserver\profiles\appsrv01\bin startnode.bat startserver.bat Connections_server Upgrade Content Engine Server 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. backup.bat -conn.home.location=c:\ibm\connections 6/25/2018 Page 35

36 6/25/2018 Page 36

37 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-FP007.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 log is generated when the update has completed successfully: IBM FileNet Content Engine have been upgraded successfully. 6/25/2018 Page 37

38 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 6/25/2018 Page 38

39 3.4.5 Upgrade CE Client IC 6.0 CR1 does not require an update to ICN however there is a requirement to have the binary file available to update the FNCE Client Open a command prompt window from the following directory: C:\IBM\Connections\FileNet.update\scripts And issue the following two commands: set skip_navigator=yes 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 FP008-WIN.exe -ceclient.fp.installer.location=c:\filenetfixpack\ p8cpe- CLIENT-WIN-FP007.EXE 6/25/2018 Page 39

40 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. 6/25/2018 Page 40

41 Verify the CE Client completed successfully Open ce_version.txt in C:\IBM\Connections\FileNet\CEClient Open a Command prompt window then issue the following command to stop the Connection server cd c:\ibm\websphere\appserver\profiles\appsrv01\bin stopserver.bat Connections_server1 -username wasadmin -password password Switch to Java 8 after upgrading FileNet Make sure deployment manager and the node agents are running and the Connections server is not running. Open a Command prompt window then issue the following commands: cd c:\ibm\websphere\appserver\profiles\dmgr01\bin managesdk -listenabledprofileall This command will list the current SDKs for WebSphere managesdk -enableprofile -profilename Dmgr01 -sdkname 1.8_64 This command will switch the SDK to 1.8_64 Stop and restart Dmgr01 by running the following commands: stopmanager.bat -username wasadmin -password password startmanager.bat 6/25/2018 Page 41

42 cd c:\ibm\websphere\appserver\profiles\appsrv01\bin managesdk -enableprofile -profilename AppSrv01 -sdkname 1.8_64 Next perform a FullSync in the WebSphere Integrated Solutions Console by going to the System Administration > Nodes and selecting the the Full Resynchronize button. Run the following command to confirm that all profiles are set to SDK 1.8_64 managesdk -listenabledprofileall 6/25/2018 Page 42

43 Restart the Deployment manager, the nodes and start the Connections server by running the following commands: cd c:\ibm\websphere\appserver\profiles\appsrv01\bin stopnode.bat -username wasadmin -password password cd c:\ibm\websphere\appserver\profiles\dmgr01\bin stopmanager.bat -username wasadmin -password password cd c:\ibm\websphere\appserver\profiles\dmgr01\bin startmanager.bat cd c:\ibm\websphere\appserver\profiles\appsrv01\bin startnode.bat startserver.bat Connections_server1 Congratulations! You have upgraded IBM Connections 6.0 to CR2! 6/25/2018 Page 43