IBM Connections 5.5 CR2 upgrade
These were the steps I followed to apply IBM Connections 5.5 CR2 where everything is
installed on a single RH Linux server. The install of 5.5 on this environment is
documented here:
https://www.ibm.com/developerworks/community/groups/service/html/communityview?
communityUuid=4021cbfe-77ed-4a39-89de59b2fd63adb5#fullpageWidgetId=Wc32719394918_47ef_817f_e7c8b6842227&file=6e5
eadd2-0dd2-46d7-9b5e-47afb14af3fa
This server also integrates with Docs, which is documented here
https://www.ibm.com/developerworks/community/groups/service/html/communityview?
communityUuid=4021cbfe-77ed-4a39-89de59b2fd63adb5#fullpageWidgetId=Wc32719394918_47ef_817f_e7c8b6842227&file=dac
f94f5-a7ea-42c9-b29f-ce243e3adb23
IBM Connections 5.5 CR2 upgrade .................................................................................... 1
1. Software Needed ......................................................................................................... 2
2. Install IBM Install Manager 1.8.5 ............................................................................... 4
3. Install WebSphere Application Server 8.5.5.9............................................................ 6
3.1. Update WebSphere Application Server to 8.5.5.9 ............................................... 7
3.2. Update IBM HTTP Server to 8.5.5.9 ................................................................. 11
4. Apply CR2 to Connections 5.5 ................................................................................. 21
4.1. Update 5.5 to CR2 .............................................................................................. 21
5. Updating Connections Databases ............................................................................. 28
6. Update TDISOL directory for CR2 .......................................................................... 29
7. Update FileNet components for CR2 ........................................................................ 30
7.1. Verify Content Engine profile is set correctly ................................................... 31
7.2. Verify FNCS profile is set correctly .................................................................. 31
7.3. Backup ObjectStore and GCD Database ............................................................ 31
7.4. Upgrade the FileNet Content Engine Server ...................................................... 32
7.5. Upgrade CE Client and FNCS ........................................................................... 34
Appendix ........................................................................................................................... 37
8. Updating FNCS Profile ............................................................................................. 37
1.
Software Needed
http://www-01.ibm.com/support/docview.wss?uid=swg21972646
I downloaded the following files prior to installing:
IBM Connections 55 CR2 from IBM Fix Central http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Lotus/Lotus+Conn
ections&release=5.5.0.0&platform=All&function=fixId&fixids=5.5.0.0-IC-Multi-CR02LO89068&includeRequisites=1&includeSupersedes=0&downloadMethod=http&source=
fc
IBM Install Manager 1.8.5 - http://www01.ibm.com/support/docview.wss?uid=swg27025142
WebSphere Application Server 8.5.5 FP9 (8.5.5.9)
http://www-01.ibm.com/support/docview.wss?uid=swg24041819
WebSphere Application Server 8.5.5.9 ifix:
none when I did the upgrade, but check the system requirements: http://www01.ibm.com/support/docview.wss?uid=swg27047297
TDISOL update http://www.ibm.com/support/fixcentral/swg/quickorder?parent=Collaboration%2BSoluti
ons&product=ibm/Lotus/Lotus+Connections&release=5.5.0.0&platform=All&function=
aparId&apars=LO90611&source=fc
FileNet: https://www-01.ibm.com/support/docview.wss?uid=swg21991528
FileNet Content Engine Server 5.2.1.4
FileNet Content Engine Client 5.2.1.4
FileNet Content Navigator (FNCS) 2.0.3.7
Database scripts needed for CR2: https://www01.ibm.com/support/docview.wss?uid=swg21991529
Cognos Wizard for CR1: https://www01.ibm.com/support/docview.wss?uid=swg21982603
IBM Community Surveys - https://www01.ibm.com/support/docview.wss?uid=swg21991532
Ephox Editors http://www.ibm.com/support/fixcentral/swg/quickorder?parent=Collaboration%20Solutio
ns&product=ibm/Lotus/Lotus+Connections&release=5.5.0.0&platform=All&function=fi
xId&fixids=EphoxEditors-IC55_CR-3.0.1.205&includeSupersedes=0&source=fc
2.
Install IBM Install Manager 1.8.5
Software needed for this step
IBM Install Manager 1.8.5 - http://www01.ibm.com/support/docview.wss?uid=swg27025142
Extract the fix pack zip download by running
unzip com.ibm.cic.agent.offering_1.8.5000.20160506_1125.zip -d InstallMgr
1. Start IBM Installation Manager by running ./IBMIM from
/opt/IBM/InstallationManager/eclipse/
2.
3.
4.
5. Click on Updates, select Search for Installation Manager updates and click Apply,
then click OK
6. Click Update
7.
8.
3.
Install WebSphere Application Server 8.5.5.9
Software needed for this step:
WebSphere Application Server 8.5.5 FP9 (8.5.5.9)
http://www-01.ibm.com/support/docview.wss?uid=swg24041819
I extracted the WebSphere FP9 files to the same directory by running
unzip 8.5.5-WS-WAS-FP0000009-part1.zip -d was8559
unzip 8.5.5-WS-WAS-FP0000009-part2.zip -d was8559
The supplements FP9 will be used in the next step.
3.1. Update WebSphere Application Server to 8.5.5.9
1. Shut down all servers
2. Start IBM Install Manager by running ./IBMIM from
/opt/IBM/InstallationManager/eclipse/
3.
4.
5. Browse to the WebSphere 8.5.5 FP9 folder
6. Make sure Search service repositories during installation and updates is unchecked,
and click OK
7. Click Update
8. Select WebSphere Application Server V8.5 and click Next>
9.
10.
11.
12.
13.
My HTTP server is on the same machine, so I'm going to leave this open to update the
HTTP Server, and later Connections itself.
3.2. Update IBM HTTP Server to 8.5.5.9
Software needed for this step:
WebSphere Application Server 8.5.5 FP9 (8.5.5.9)
http://www-01.ibm.com/support/docview.wss?uid=swg24041819
I extracted the WebSphere FP9 files by running
unzip 8.5.5-WS-WASSupplements-FP0000009-part1.zip -d wassupp8559
unzip 8.5.5-WS-WASSupplements-FP0000009-part2.zip -d wassupp8559
1. Make sure to stop IBM HTTP Server by running ./apachectl stop from
/opt/IBM/HTTPServer/bin/
2. If you are not still in the IBM Install Manager, start that, and add the Supplements
folder to the repositories:
3.
4. Make sure Search service repositories during installation and updates is unchecked,
and click OK
5. Click Update
6. Select IBM HTTP Server
7.
8.
9.
10.
11.
12. Click Update to now update the plugin
13.
14. Select Web Server Plug-in for IBM WebSphere Application Server and click Next>
15.
16.
17.
18. Click Update
19.
20. I will leave Install Manager open and start the Connections CR2 upgrade
21. Start IBM HTTP Server by running ./apachectl start from /opt/IBM/HTTPServer/bin/
4.
Apply CR2 to Connections 5.5
In this step, we will install the CR2 fixes. Software needed for this step:
IBM Connections 55 CR2 from IBM Fix Central http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Lotus/Lotus+Conn
ections&release=5.5.0.0&platform=All&function=fixId&fixids=5.5.0.0-IC-Multi-CR02LO89068&includeRequisites=1&includeSupersedes=0&downloadMethod=http&source=
fc
4.1. Update 5.5 to CR2
Extract 5.5.0.0-IC-Multi-CR02-LO89068.zip by running
unzip 5.5.0.0-IC-Multi-CR02-LO89068.zip -d ic55cr2
In this step the connections nodes and nodeagents should be stopped, but DMGR should
be running.
1. Start IBM Install Manager
2.
3.
4. Browse to the location you extracted CR2 /opt/install/ic55cr2/ic55cr2 and go to
updates\repository.config
5. Make sure Search service repositories during installation and updates is uncheck, and
click Ok
6. Click Update
7. Select IBM Connections and click Next
8.
9.
10.
11.
12.
13.
14.
15.
16. Clear the WAS temp directories by removing all folders under
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp
17. Start the nodeagent.
18. Look in the nodeagent's SystemOut.log for the following messages
ADMA7021I: Distribution of application Activities completed successfully.
ADMA7021I: Distribution of application Mobile completed successfully.
ADMA7021I: Distribution of application navigator completed successfully.
ADMA7021I: Distribution of application FileNetEngine completed successfully.
ADMA7021I: Distribution of application Files completed successfully.
ADMA7021I: Distribution of application Forums completed successfully.
ADMA7021I: Distribution of application News completed successfully.
ADMA7021I: Distribution of application PushNotification completed successfully.
ADMA7021I: Distribution of application RichTextEditors completed successfully.
ADMA7021I: Distribution of application Search completed successfully.
ADMA7021I: Distribution of application Profiles completed successfully.
ADMA7021I: Distribution of application WidgetContainer completed successfully.
ADMA7021I: Distribution of application Moderation completed successfully.
ADMA7021I: Distribution of application Dogear completed successfully.
ADMA7021I: Distribution of application Wikis completed successfully.
ADMA7021I: Distribution of application Blogs completed successfully.
ADMA7021I: Distribution of application Common completed successfully.
ADMA7021I: Distribution of application Metrics completed successfully.
ADMA7021I: Distribution of application Homepage completed successfully.
ADMA7021I: Distribution of application Help completed successfully.
ADMA7021I: Distribution of application Mobile Administration completed successfully.
ADMA7021I: Distribution of application URLPreview completed successfully.
ADMA7021I: Distribution of application ConnectionsProxy completed successfully.
ADMA7021I: Distribution of application Extensions completed successfully.
ADMA7021I: Distribution of application Communities completed successfully.
This part took about 30 minutes to complete after the node agent started on my test
machine.
5.
Updating Connections Databases
Files needed for this step:
Database scripts needed for CR2: https://www01.ibm.com/support/docview.wss?uid=swg21991529
I downloaded the zip file and extracted it running
unzip 55cr2-database-updates.zip -d cr2db
1. Copy the folder for your environment to the db2inst1 home directory. For example
I’m using DB2 and currently I’m running Connections 5.5, so I need to go to
/opt/install/ic55cr2/cr2db/55cr2-database-updates/From-55 and copy the db2 folder to
my db2inst1 directory by running
cp -R db2/ /home/db2inst1/ic55cr2
2. Go to /home/db2inst1 and change ownership of the ic55cr2 directory to db2inst1 by
running
chown db2inst1:db2iadm1 ic55cr2/
3. Sign into the DB2 server as db2inst1
4. Look in the readme file for the version you are upgrading from for the list of
command you need to run. For example, I’m using DB2 and am currently on 5.5, so I
looked at /opt/install/ic55cr2/cr2db/55cr2-database-updates/From-55 readme-db2updates-from-55.txt and found the 6 commands I needed to run.
db2 -td@ -vf 55-CR1-homepage-db2.sql
db2 -td@ -vf 55-CR2-mobile-db2.sql
db2 -td@ -vf 55-CR2-activities-db2.sql
db2 -td@ -vf 55-CR2-files-db2.sql
db2 -td@ -vf 55-CR2-wikis-db2.sql
db2 -td@ -vf 55-CR2-homepage-db2.sql
Run each command
5. Once run, close out of the DB2 command window
6. Start the environment, and Connections will be upgraded to 5.5 CR2
6.
Update TDISOL directory for CR2
Software needed for this step
TDISOL update http://www.ibm.com/support/fixcentral/swg/quickorder?parent=Collaboration%2BSoluti
ons&product=ibm/Lotus/Lotus+Connections&release=5.5.0.0&platform=All&function=
aparId&apars=LO90611&source=fc
Extract the downloaded tar file - 5.5.0.0-IC-Multi-TDISOL-LO90611LinuxAIX_20161104.tar. by running
tar -xf 5.5.0.0-IC-Multi-TDISOL-LO90611-LinuxAIX_20161104.tar -C
/opt/install/ic55cr2
This will create a tdisol/TDI directory
1. Backup your existing TDI directory. On my system, I have this in
/opt/IBM/TDI/V7.1.1/tdisol/TDI by running
cd /opt/IBM/TDI/V7.1.1/tdisol
mv TDI TDIorig
2. Copy the new TDI directory to /opt/IBM/TDI/V7.1.1/tdisol by running
mkdir TDI
cp -r /opt/install/ic55cr2/tdisol/TDI/* TDI/
3. Copy the following files from the old TDI directory to the new and overwrite the
existing files
profiles_tdi.properties
map_dbrepos_from_source.properties
tdienv.sh
4. Edit profiles_tdi.properties and add the following settings to the end of the file. I
copied these from the end of the cr2 profiles_tdi.properties file
hash_db_entries_state=Enabled
hash_source_entries_state=Enabled
sync_all_dns_main_state=Enabled
sync_all_dns_process_delete_state=Enabled
sync_all_dns_process_add_state=Enabled
LookupMemTimestampDb_state=Enabled
5. If there are other files you have modified in your env, you will need to merge the
changes.
6. Edit profiles_tdi.properties and set
sync_updates_show_summary_only=true
This way when we run a sync, it will run the sync as normal, and tell us how
many users would have been modified, inactivated or unchanged, but won’t
actually update the users in the profiles database.
7. Run /opt/IBM/TDI/V7.1.1/tdisol/TDI>./sync_all_dns.sh
If you get the results you expect, then set sync_updates_show_summary_only
back to false and run the sync again, otherwise, review the updates in the tdisol
dir until you are able to run a sync as expected.
8. In my environment I also have external users set in in tdisol/external, so I
completed the same steps above for the external directory as well.
7.
Update FileNet components for CR2
Software needed for this step:
FileNet: https://www-01.ibm.com/support/docview.wss?uid=swg21991528
FileNet Content Engine Server 5.2.1.4
FileNet Content Engine Client 5.2.1.4
FileNet Content Navigator (FNCS) 2.0.3.7
Extract the 3 files:
5.2.1.4-P8CPE-CLIENT-LINUX-FP004.tar.gz
5.2.1.4-P8CPE-LINUX-FP004.tar.gz
2.0.3-ICN-FP007-WIN.zip
By running:
mkdir filenet
tar -C filenet -zxvf 5.2.1.4-P8CPE-LINUX-FP004.tar.gz
tar -C filenet -zxvf 5.2.1.4-P8CPE-CLIENT-LINUX-FP004.tar.gz
tar -C filenet -xvf 2.0.3-ICN-FP007-LINUX.tar
7.1. Verify Content Engine profile is set correctly
1. Go to /opt/IBM/Connections/FileNet/ContentEngine/tools/configure/profiles/CCM
and verify all values are set correctly in this applicationserver.xml. If any settings are
not set, update the value for that setting. In a few customer environments I’ve seen
Admin password not be set.
7.2. Verify FNCS profile is set correctly
1. Go to /opt/IBM/Connections/FNCS/configure/profiles/CCM and verify the settings in
applicationserver.xml are correct. If any values are incorrect, update them in the file.
2. Open configurefncstask.xml and deployapplication.xml, if any settings are not
populated in this file, go down to Appendix section Updating FNCS Profile and
follow the steps to reconfigure these config settings. So far I’ve only had to do this
on 1 internal server in IBM. If anyone reading this knows Matt Milza, please make
sure to tell him I blame him for screwing up these files so bad. :)
7.3. Backup ObjectStore and GCD Database
1. Stop Connections, nodeagents and DMGR
2. As the db2admin user (db2inst1)
3. Create a directory to store the backup, I used /home/db2inst1/fn55backup
4. Run the following commands
db2 backup database FNOS to /home/db2inst1/fn55backup
db2 backup database FNGCD to /home/db2inst1/fn55backup
5. Log out the db2admin user
7.4. Upgrade the FileNet Content Engine Server
NOTE: Make sure you’ve checked that everything is correct in the Content Engine and
FNCS profile xml files before running the backup, during the upgrade we copy files from
this backup location to the …/configure/profiles/CCM and if the xml files in the backup
are not correct it will cause the upgrade to fail.
1. Start the DMGR, nodeagent and Connections server
2. Verify the applicationserver.xml file is correctly in your environment by going to
/opt/IBM/Connections/FNCS/configure/profiles/CCM. Open applicationserver.xml
and check the values for each entry (was admin name, was admin password,
connections hostname etc.) are set correctly, update any you find are not set correctly.
3. Also go to /FileNet/ContentEngine/tools/configure/profiles/CCM and verify all
values are set correctly in this file as well.
4. From /opt/IBM/Connections/FileNet.update/scripts/ run
./backup.sh -conn_home_path="/opt/IBM/Connections"
to backup FileNet
5. Verify /opt/IBM/Connections/FileNet_backup/fncs/CCM/applicationserver.xml has
the password set for the WAS admin user, by opening the file and searching for
Password. If the value is not set update it here. In my environment this was set
correctly
6. From /opt/IBM/Connections/FileNet.update/scripts run ./update-ce.sh was_dm_path=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 was_admin_user=localadmin -was_admin_password=password conn_home_path=/opt/IBM/Connections ce_fp_installer_location=/opt/install/ic55cr2/filenet/5.2.1.4-P8CPE-LINUXFP004.BIN
Verify the upgrade completed successfully
7. Go to /opt/IBM/Connections/FileNet/ContentEngine and open ce_version.txt
8. Go to the Integrated Solution Console and start the FileNetEngine application server
9. Open the browser to http://cpdocs2.swg.usma.ibm.com/FileNet/Engine
make sure the Version match’s the version from the ce_version.txt file
7.5. Upgrade CE Client and FNCS
10. From /opt/IBM/Connections/FileNet.update/scripts run ./update-fncs-ceclient.sh was_dm_path=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 was_admin_user=localadmin -was_admin_password=password conn_home_path=/opt/IBM/Connections -doSetAnonymous=y anonymous_user=fnanon -anonymous_password=password fncs_fp_installer_location=/opt/install/ic55cr2/filenet/IBM_CONTENT_NAVIGAT
OR-2.0.3.7-FP007-LINUX.bin ceclient_fp_installer_location=/opt/install/ic55cr2/filenet/5.2.1.4-P8CPE-CLIENTLINUX-FP004.BIN
NOTE: If you don’t allow anonymous access to Communities, you can set -
doSetAnonymous=n and remove -anonymous_user=fnanon anonymous_password=password
anonymous_user is a system user in the ldap directory only used by FileNet to give
access to FileNet libraries to anonymous users.
Verify the CE Client upgrade completed successfully
11. Open /opt/IBM/Connections/FileNet/CEClient/ce_version.txt and check the version:
Verify the FNCS application upgrade completed successfully
12. Open a browser to http://cprice55.swg.usma.ibm.com/dm
Connections Content Manager is now upgraded to 5.5 CR2
Appendix
8.
Updating FNCS Profile
So far I’ve only see this come up on 1 system that was running on linux. These are the
steps I took to fix the FNCS profile prior to backing it up and upgrading both Content
Engine Server and FNCS. You will notice the hostnames and all location are different
from the rest of the document because this was all done on Matt’s test environment.
1. Verify the applicationserver.xml file is correctly in your environment by going to
/opt/IBM/Connections/FNCS/configure/profiles/CCM. Open applicationserver.xml
and check the values for each entry (was admin name, was admin password,
connections hostname etc.) are set correctly, update any you find are not set correctly.
On your server I updated a lot – including application server version, password etc.
2. Check configurefncstask.xml and deployapplication.xml – if they are not set correctly
continue with these steps, if they are, go to the next section…
a. Go to /opt/IBM/Connections/FNCS/configure and run ./configmgr
b.
c.
d. Double click on Update the FileNet P8 Client Connector, update it as follows and
click save
e. Double click on Configure IBM FileNet Collaboration Services, update it as
follows and click Save
*** Matt, please set schema to LCUSER ***
I want to see if you have this error in ccm systemOut
---- Begin backtrace for Nested Throwables
com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-727,
SQLSTATE=56098, SQLERRMC=2;-204;42704;DUMMY.CONFIGURATION,
DRIVER=4.18.60
f. Double Click on Build the Web Application, set it as follows and click Save
Build Script:
/opt/IBM/Connections/FNCS/configure/explodedformat/create_ear.sh
Temporary directory: /opt/IBM/Connections/FNCS/configure/tmp
g. Double click on Deploy the Web Application, set it as follows and click Save
Deployment type: Cluster
Deployable EAR file:
/opt/IBM/Connections/FNCS/configure/deploy/navigatorEAR.ear
Web application name: navigator
Application server virtual host: CCMCluster
Application server virtual host: default_host
Application Edition Management: default
Deployment script:
/opt/IBM/Connections/FNCS/configure/scripts/deployWSApplication.tcl
Temporary directory: /opt/IBM/Connections/FNCS/configure/tmp
h. Close out of the deployment tool
The profile should now be fixed and you can return to Backup ObjectStore and GCD
Database to complete the upgrade of Filenet.