Since as usual, I encountered a few issues while doing an upgrade from ICN 2.0.1 to ICN 2.0.3, I thought I would describe the procedure here. Also the whole platform has been installed by a CPIT installer, therefore with all defaults settings.
Backup the profile you used to configure ICN 2.0.1
cp /opt/IBM/cpit/install-scripts/profiles/NexusConfig /opt/IBM/cpit/install-scripts/profiles/NexusConfigBackup
As usual, take a snapshot of your VM before you start!
Before starting, if you didn’t install you platform with the script I gave you in this post, you might run out of memory. It is best to increase the maximum heap size for the WebSphere server before to start (restart of WebSphere required). I explain how to to that in the same post.
Launch the installer (I always disable enforce to make sure, even if think it’s not useful for this upgrade)
/usr/sbin/setenforce 0 ./IBM_CONTENT_NAVIGATOR-2.0.3-LINUX.BIN
If you are running your platform on a windows server, you would need to run the configuration tool as an Admin user (Right Click > Run as Administrator) (thank you Tom).
Here are some screen shots if you have some troubles with the installer, but it is pretty straightforward.
Choose upgrade the profile
Select the profile the CPIT installer used (you should have backup it)
CMIS is now shipped with ICN, so if you want to install it now would be the time 🙂
The db password set by the CPIT installer is the same than for P8Admin. If you are not sure you can check out in the profile you backup, in the create jdbc datasource xml file! Also do not check Run the script because it doesn’t work (at least it didn’t for me). We will run it manually later.
Don’t bother with test the connection it doesn’t work. It cannot find the JDBC driver, although the path is correct. Don’t worry everything will work at the end.
Run the task
Under Windows, it is possible that the configuration tool freezes and just keeps spinning but it could work anyway, llok at the log (see Tom’s comment).
And that’s all for the configuration part. Now we still have to update the database.
Start DB2 Configuration Center:
xhost + su - dsrdbm01 db2cc
If you are running under a Windows platform, log in as a Windows administrator and run the command:
grant SECADM on database to user dsrdbm01
and adjust dsrdbm01 admin permissions as needed (thanks again Tom, see its comment at the bottom of this post for more information).
And launch the script DB2_UPGRADE_SCRIPT.sql. Be careful to take the one in the modified folder, not the one in db2 folder:
Add your DB to the list
Select the script created by the configuration tool (take extra care to use the one in the modified subfolder, the one in the DB2 folder is the original one without your information)
Launch the script
The upgrade is finished. You can restart WebSphere to make sure but Content Navigator should work right away.