INTRODUCTION

This document describes step by step how to apply a Connections 4.5 CR when using Connections Content Manager ( CCM ) .

The steps and screenshots below have originally been captured for CR1, however apply as well to CR2 if updating from Connections 4.5 .

If updating from CR1 you would have already updated CE/Server and CE/Client and will only need to update Collaboration Services (FNCS) using IF1 .

Note : The procedure described in this document is for existing installations of Connections 4.5 with CCM . For new installations, please refer to IBM Connection Content Manager (CCM) - Information on FileNet 5.2.0 FP1 .

Note : For any problems regarding the update of CE/Server, CE/Client, or FNCS, please contact FileNet support . For any other questions, Connections support would be first point of contact .

Note : FNCS 2.0.0 IF1 is cumulative and newer than FNCS 2.0.0 FP1 . FNCS 2.0.0 IF1 is required for Connections CR2 and works with both Connections CR1 and CR2 .

Applying a Connections CR requires to update Connections Content Manager ( CCM ) first, please see :

Update strategy for IBM Connections 4.5

Information on updating FileNet 5.2.0 for use with IBM Connection Content Manager (CCM)

Updating the Content Platform Engine server version implies that the Content Platform client version needs to be updated . Please see FileNet InfoCentre .

You need both CE/Server and CE/Client . Both can be downloaded from FixCentral . Direct links are included in this Technote .

We need as well to update FNCS . Current version is 2.0.0 IF1 and can be downloaded from FixCentral . Direct links are included in this Technote .

In regard to the update instructions, you may want to check out the following links in addition to the links listed above :

Installation instructions for CE/Server and CE/Client are in the ReadMe that you download with the fixes from FixCentral .

FixPack instructions for FNCS are as well in the InfoCentre .

Here the link to Reconfiguring and redeploying IBM FileNet Collaboration Services in the FileNet InfoCentre .

And to Configuring FileNet Collaboration Services for the Connections Content Manager in the Connections documentation .

The following steps were tested successfully in my test environment .

The test environment is a small topology with all applications incl. CCM on a single host ( c45.renovations.xyz ) and deployment manager on a separate host ( perc45.renovations.xyz ) . Note that this environment is not customized . The steps do not cover any required backup steps .

The specific steps vary with the specifics of your installation, however I hope the steps can help as a guidance . Please make sure to read the documentation carefully as you may need to run additional tasks, or the documentation may be updated .

Before you begin

Make sure you have a working backup .
Read the documentation carefully before you start .
It is important to backup customizations and product modifications made to the application prior to applying a set of CR interim fixes.
Please refer to the topic Backing up IBM Connections in the product documentation for details as well as the Technote Update strategy for IBM Connections 4.5 .

We begin with updating the Content Platform Engine server and follow the instructions in the ReadMe :

Installing and configuring the feature pack 5.2.0.1

Preparing the CPE server for installation

1. Log on as the "ce_install_user". If you used Connections to install FileNet, this should be the user specified during the Connections install. In my case this is "root".

2. Stop Content Platform Engine and all client applications
In my environment I stopped the cluster, nodeagents and deployment manager.

3. Extract files to temporary location :
/files/CR1/server : tar zxvf 5.2.0.1-P8CE-LINUX-FP001.tar.gz

4. back up all existing bootstrapped Engine-xx.ear files
cp -v /opt/IBM/Connections/addons/ccm/ContentEngine/tools/configure/profiles/CCM/ear/Engine-ws.ear /files/CR1/backup/

Installing the CPE server updates interactively

Note : The details slightly differ for the Windows platform . Also, in Windows the installer is trying to connect to 'http://CEServer:port/wsi/FNCEWS40MTOM', hence the server actually needs to be started. For details please refer to the FileNet documentation .

Run the installation program :
cd /files/CR1/server
./5.2.0.1-P8CE-LINUX-FP001.BIN

The welcome screen opens . Click "Next" .

Make sure "Content Platform Engine Server " is selected . Click "Next" .

The setup program identified the existing installation correctly . Click "Next" .

Update the URL and click "Next" . Below is the content of the properties file from my environment for reference only .

cat /opt/IBM/Connections/addons/ccm/ContentEngine/tools/PE/config/WcmApiConfig.properties
RemoteServerUrl = http://localhost:9080/wsi/FNCEWS40MTOM/
CredentialsProtection = Clear
CredentialsProtection/UserToken = Symmetric
CryptoKeyFile/UserToken =

Review the summary and click "Install" .

Verify the installation completed successfully and click "Done" to complete this step .

Completing the CPE server installation

1. Review the CPE log files .

I am including a file listing from my test server for reference only :
cd /opt/IBM/Connections/addons/ccm/ContentEngine/
ls -lart
total 664
drwxrwxr-x 3 root root 4096 May 3 01:46 properties
drwxrwxr-x 2 root root 4096 May 3 01:46 license
drwxrwxr-x 2 root root 4096 May 3 01:46 cdapi
drwxrwxr-x 3 root root 4096 May 3 01:46 config
drwxrwxr-x 2 root root 4096 May 3 01:47 _ceuninst
-rwxr-xr-x 1 root root 298987 May 3 01:47 ce_install_log_5.2.0.txt
drwxr-xr-x 7 root root 4096 May 3 01:49 ..
-rw-r--r-- 1 root root 673 May 3 02:05 Servers.xml
-rwxrwxr-x 1 root root 157 May 23 00:13 ce_version.txt
drwxrwxr-x 5 root root 4096 Jun 28 16:35 _cejvm
drwxrwxr-x 6 root root 4096 Jun 28 16:36 tools
drwxrwxr-x 2 root root 4096 Jun 28 16:36 resources
drwxrwxr-x 2 root root 4096 Jun 28 16:38 lib
drwxrwxr-x 3 root root 4096 Jun 28 16:38 samples
drwxrwxr-x 2 root root 4096 Jun 28 16:38 Kerberos
drwxrwxr-x 2 root root 4096 Jun 28 16:46 tsm100
-rwxrwxr-x 1 root root 510 Jun 28 16:46 ce_install_summary.txt
-rwxr-xr-x 1 root root 302844 Jun 28 16:46 ce_install_log_5.2.0.1.txt

2. Review the CPE version log file

Make note of the Content Engine Build number . You will use it later in the installation process to confirm the deployment of the update CPE .

Just for reference I am including the content of the file from my test system .
cat ce_version.txt
P8 Content Platform Engine 5.2.0.1
Content Engine Build dap520.001.052
Configuration Manager Build cm520.001.009
P8 Deployment Tool Build dep520.001.004

Configuring the CPE server after installation

We are only updating an existing CPE 5.2.0 system, so we continue with the next step .

Removing a deployed CPE

Open the WebSphere Administration console and go to Applications -> Application Types -> WebSphere enterprise applications and select "FileNetEngine" . Then click the "Uninstall" button .

Note that this deletes the Engine-ws.ear from the WAS Server .

Confirm that you want to uninstall by clicking "OK" .

And click "Save" to save your changes .

The application has now been deleted .

Removing the application cache directories

1. Stop the deployment manager and all nodes

2. On all nodes ( nothing to do on the deployment manager itself ) remove the FileNetEngine directory where the application server cache data is stored :

rm -r -f /opt/IBM/WebSphere/AppServer/profiles/Conn45n01/temp/C45Node01/C45CCM_server1/FileNetEngine/

3. Restart the deployment manager and all nodes

Clearing the Internet browser cache on ACCE clients

Clear internet browser cache on all client computers that use the Administration console for CPE ( ACCE ) for administering CPE

Completing Configuration Manager tasks interactively

Starting the Configuration Manager

1. Log on to the CPE server as "config_mgr_user"
In my case this is logging on to dmgr as root

2. Start the Configuration Manager
/opt/IBM/Connections/addons/ccm/ContentEngine/tools/configure/configmgr

Bootstrapping the CPE

In the configuration manager go to File -> Upgrade Profile ...

Review the details and click "Next" .

On the next screen enter the administrator user name and password, then click the "Test Connection" button . Make sure the connection is successful . Close the dialog box with clicking "OK" .

You are back to the previous screen . Click "Finish" .

You will be prompted with additional information . Review and click "OK" .

The following screen should look similar to this . We select the task "Configure Bootstrap and Text Extraction" .

Make sure the Bootstrap operations shows "Upgrade" .

Verify the path in the field "Bootstrapped EAR file" .

Click "Save" .

Then click "Run Task" .

Review the status messages and make sure the task completes successfully before proceeding .

Below is the console output from my test environment for reference only :
Starting to run Configure Bootstrap and Text Extraction
Configure Bootstrap and Text Extraction *************************
*************************
*************************
*************************
*************************
*************************
*************************
*************************
*************************
*************************
*
Finished running Configure Bootstrap and Text Extraction
INFO: Configuring Bootstrap data ...
INFO: Text extraction version in initial EAR file: "8.3.7-p15954226_837.001" (Platform: N\A)
INFO: Text extraction version in Configuration Manager: "8.3.7-p15954226_837.001"
INFO: Content Search Services API version in initial EAR file: "2.1.0.0, 3740, 2013/01/17 17:42:35.704"
INFO: Content Search Services API version in Configuration Manager: "2.1.0.0, 3895.FP1, 2013/05/09 18:25:54.426"
INFO: Installing Text extraction version 8.3.7-p15954226_837.001 (platform: linux) to EAR file.
INFO: Executing Platform: linux
INFO: Done installing and updating EAR file.

Deploying the CPE

Still in the configuration manager select now the task "Deploy Application" .

Note that the console is not clearing automatically when switching between tasks, but it will be cleared when running a new task .

Right-click "Deploy Application" in the CPE Task View pane and select "Edit Selected Task" .

Verify the path in the field "Bootstrapped EAR file" .

Click "Save" .

For reference only the paths from my test environment :

Bootstrapped ear file : /opt/IBM/Connections/addons/ccm/ContentEngine/tools/configure/profiles/CCM/ear/Engine-ws.ear
Script : /opt/IBM/Connections/addons/ccm/ContentEngine/tools/configure/scripts/deployWSApplication.tcl

Click "Run Task" .

Review the status messages and make sure the task completes successfully .

We are done with the deployment of the CPE Server update . You can now close the configuration manager .

Restarting the application server

Before restarting the environment, you may want to remap the FileNetEngine application and update the webserver plug-in .

From the WebSphere Solution Console open the "FileNetEngine" configuration .

Go to "Manage Modules"

Select all modules and the clusters and servers you want them mapped against . Then click "Apply" .

You see the mappings now updated . To save your changes click "OK" .

Now click "Save" .

To update the webserver plugin in my environment I go to Server -> Server Types -> Web servers .

Select the webserver and click "Generate Plug-in" .

Review the status messages and make sure the plug-in is generated successfully .

Then select the webserver again and click "Propagate Plug-in" .

Verify that the propagation is successful .

Restart all servers .

Verifying the deployment of the updated CPE EAR file

Go to https://perc45.renovations.xyz/FileNet/Engine

Make sure that the Startup Message key for CPE is the same as the CPE build number recorded earlier ( taken from ce_version.txt )

Checking the autoUpgradeStatus page

Go to : https://perc45.renovations.xyz/FileNet/AutomaticUpgradeStatus

Wait until the status says 'Completed' . For details on the status codes, please see the FileNet InfoCentre .

You can as well follow the links 'Completed' seen in the screenshot to view the messages written out .

If you restarted the server after the autoUpgrate already completed, you should see the status "Ready" . In this case you may want to check the log files . In my environment the logs have been written to the following file on the node that is CCM is running :

/opt/IBM/WebSphere/profiles/Conn45n01/FileNet/C45CCM_server1/p8_server_error.log.1

You should see entries similar to the following :

"Completed domain upgrade sequence from version '5.1.1.61' to version '5.2.0.7'..."

"Completed object store upgrade sequence from phase '18.2.2 InstallUAO's' to phase '18.2.2'..."

Updating FNCS from 2.0.0.0 to 2.0.0.1

Uninstall the current FNCS Application

In the WebSphere Solution console select the application FNCS and click "Uninstall" .

Confirm that you want to uninstall the application by clicking "OK" .

Save your changes by clicking "Save" .

Delete the temp cache area for this application on all nodes in the cluster

Shutdown all servers, nodes and the deployment manager .

rm -f -r /opt/IBM/WebSphere/AppServer/profiles/Conn45n01/temp/C45Node01/C45CCM_server1/FNCS

Uninstall the application binaries

cd /opt/IBM/Connections/addons/ccm/FNCS/uninstall
./fncs-uninstall

Deleting the FNCS directory

Backup the file : /opt/IBM/Connections/addons/ccm/FNCS/configmanager/profiles/fncs-sitePrefs.properties

Note: Only backup the CE_API directory if you are upgrading from CR1 to CR2 and apply FNCS 2.0.0.1-FNCS-IF001 only .

This step does not apply when upgrading from 4.5 to 4.5CR1 or from 4.5 to 4.5CR2 .

Backup the directory : /opt/IBM/Connections/addons/ccm/FNCS/CE_API

Delete the directory : /opt/IBM/Connections/addons/ccm/FNCS

Install the new FNCS Application

cd /files/CR1/FNCS
./FNCS-2.0.0.1-Linux.bin

Note: for FNCS IF1 this is : ./2.0.0.1-FNCS-IF001-Linux.bin )

On the welcome screen choose your language and click "OK" .

Click "Next" .

Accept license agreement and click "Next" .

Update the installation directory ( the installer defaults to /opt/IBM/FNCS ) .

Then click "Next" .

Make sure the information is correct . Then click "Install .

The installer will show its progress .

When completed make sure the installation was successful .

This completes the installation of FNCS 2.0.0.1 ( IF1 ).

Installing the CPE client updates interactively

Restart your environment . For the next steps the server needs to be up and running .

Extract files to temporary location on the dmgr :
cd /files/CR1/client/
tar zxvf 5.2.0.1-P8CE-CLIENT-LINUX-FP001.tar.gz

Run the installation program
cd /files/CR1/client/
./5.2.0.1-P8CE-CLIENT-LINUX-FP001.BIN

The installation program starts up . Click "Next" .

The CPE client program is detected correctly . Click "Next" .

Update the details to match your environment .

In my environment the port number is the value of WC_defaulthost for this server .

Click "Next" .

The installer performs a connection test . Make sure the connection is successful and click "OK" .

Make sure "IBM FileNet Services for Lotus Quickr" is selected .

In my environment the option was selected automatically and no changes were needed .

Click "Next" .

Review the status message and make sure it is correct .

Click "Next" .

Enter a browser program . Default is "mozilla" . I changed it to "firefox" to match the configuration of my local environment .

I kept the default on the Common Files directory .

Make sure the summary is correct. Click "Next" .

C

The installer shows its progress ...

... when finished make sure the installation completed successfully .

This completes the CPE client update . Click "Done" to close the window .

Configuring FNCS

Before you begin :

Restore the file fncs-sitePrefs.properties ( /opt/IBM/Connections/addons/ccm/FNCS/configmanager/profiles/fncs-sitePrefs.properties )

Note: Only if you are upgrading from CR1 to CR2 and apply FNCS 2.0.0.1-FNCS-IF001 without upgrading FileNetContent Server and Client .
Do not perform this step if upgrading as well the FileNet Content Engine Server and Client .
Otherwise you may overwrite the CE_API directory with an older version .
Restore the directory CE_API ( /opt/IBM/Connections/addons/ccm/FNCS/CE_API )

cd /opt/IBM/Connections/addons/ccm/FNCS/configmanager
./configwizard.sh

On the welcome screen select your language and click "OK" .

Review the details on the next screen and make sure you meet the requirements . Click "Next" .

Enter the details matching your environment .

The port number is the value of the BOOTSTRAP_ADDRESS for this server .

Click "Next" .

Enter the correct values on the next screen . These are not read from the environment .

Click "Next" .

Enter the correct credentials and click "Next" .

Make sure the connection is successful . Click "Next" .

For "Web client application" select "None" .

Click "Next" .

Enter the Connections URL . Click "Next" .

Select the server profile and enter administrator credentials .

Click "Next" .

In this case I am running a single-node cluster and select "Application server cluster" .

Click "Next" .

Select the cluster name and click "Next" .

I am changing the name of the FNCS application to "FNCS" ( in capitals ) .

Click "Next" .

Review the summary to make sure everything is correct .

Click "Next" .

Once completed verify that the configuration completed successfully . Click "Done" .

To complete the configuration open the WebSphere Administration console for Deployment Manager in a browser.

Enable use of authentication data on unprotected URLs :
Navigate to Security -> Global Security -> Web security -> General Settings
Make sure Authenticate only when the URI is protected is selected and Use available authentication data when an unprotected URI is accessed also is selected.




Modify security role mapping for the FileNet Collaboration Services application :
Navigate to Applications -> WebSphere Enterprise Applications -> FNCS
Click Security role to user/group mapping .
Select the Authenticated option and then select Map Special Subjects and Everyone ( by default this is mapped to "All Authenticated in Application's Realm ) .
Click OK to save your changes :





Install the authentication filter code :
Navigate to WebSphere Enterprise Applications .Select the FileNet Collaboration Services option .Click the Update button .



For Application update options, select the Replace, add, or delete multiple files option.
Select local file system if running the browser on the Deployment Manager node and then locate the auth_filter_patch.zip file in the /ccm/ccm/ccm/auth_filter_patch/auth_filter_patch.zip directory.
If the browser is not running on the Deployment Manager (DM) node, then select remote file system and choose the DM file system, locating the auth_filter_patch.zip file in the directory previously stated.
Click Next .




Click OK .



Make sure to save the update .

Validate FNCS was deployed correctly . Restart the environment then go to

http://perc45.renovations.xyz/dm/

Note : Build number changes when applying IF1 ( p8quickr200.001.070 )

We completed the FileNet update and can proceed with applying CR1 .

Applying CR1

1. Prepare to install CR1

Download CR1 and the latest UpdateInstaller from FixCentral .

On the deployment manager node, remove the existing updateInstaller directory : /opt/IBM/Connections/updateinstaller

Unzip the latest updateInstaller : 4.5.0.0-IC-Multi-UPDI-20130604.zip
in : /opt/IBM/Connections
( this creates a new directory '/opt/IBM/Connections/updateinstaller' )

Verify that executable rights are set .

Unzip 4.5.0.0-IC-Multi-CR01-LO75060.zip to a temporary directory .

Note : The archive contains the following .zip file that you need to extract separately : 45-CR1-CCM-OPTIONAL-UPDATE-UNZIP-AND-PLACE-JAR-IN-FIXES-DIRECTORY.zip


Move the fixes to /fixes directory :
mv -v *.jar /opt/IBM/Connections/updateInstaller/fixes/
LO75060-IC4500-CR01-Activities.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Activities.jar'
LO75060-IC4500-CR01-Blogs.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Blogs.jar'
LO75060-IC4500-CR01-Bookmarks.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Bookmarks.jar'
LO75060-IC4500-CR01-CCM.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-CCM.jar'
LO75060-IC4500-CR01-Common.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Common.jar'
LO75060-IC4500-CR01-Communities.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Communities.jar'
LO75060-IC4500-CR01-Container.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Container.jar'
LO75060-IC4500-CR01-Files.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Files.jar'
LO75060-IC4500-CR01-Forums.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Forums.jar'
LO75060-IC4500-CR01-Help.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Help.jar'
LO75060-IC4500-CR01-Homepage.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Homepage.jar'
LO75060-IC4500-CR01-Metrics.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Metrics.jar'
LO75060-IC4500-CR01-MobileAdmin.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-MobileAdmin.jar'
LO75060-IC4500-CR01-Mobile.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Mobile.jar'
LO75060-IC4500-CR01-Moderation.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Moderation.jar'
LO75060-IC4500-CR01-News.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-News.jar'
LO75060-IC4500-CR01-Profiles.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Profiles.jar'
LO75060-IC4500-CR01-Proxy.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Proxy.jar'
LO75060-IC4500-CR01-Search.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Search.jar'
LO75060-IC4500-CR01-Wikis.jar' -> `/opt/IBM/Connections/updateInstaller/fixes/LO75060-IC4500-CR01-Wikis.jar'

2. Applying the fixes

Stop the cluster and all nodeagents .

From a command prompt run :

cd /opt/IBM/WebSphere/AppServer/bin/
. ./setupCmdLine.sh
cd /opt/IBM/Connections/updateInstaller
chmod +x updateWizard.sh
./updateWizard.sh

Note : If the environment parameters should not be set correctly you may alternatively run the setupCmdLine script from the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/ directory .

On the welcome screen click "Next" .

Select "Install updates" . We can keep the directory path as we already moved the fixes to the default directory . Click "Next" .

Select all fixes you like to install . In this case we select all . Click "Next" .

The following screen is a reminder to backup and remerge any customizations . In this case there are no customizations, so we can go ahead . Click "OK" .

Enter credentials and click "Next" .

Review the summary and click "Install" .

The installer is busy ...

[

Once completed make sure all fixes have been installed successfully .. Click "Finish" to close the Wizard .

3. Post-install steps

Run the remaining tasks documented in IBM Connection Content Manager (CCM) - Information on FileNet 5.2.0 FP1 .

Run ccmUpdate.bat|sh in the ccmDomainTool package to update User Token Cache and Subject Cache to 3600, and install Social Collaboration User Identity Extensions AddOn.

Make sure the cluster and CCM are running before running the task

cd /opt/IBM/Connections/addons/ccm/ccmDomainTool/
chmod +x ccmUpdate.sh
./ccmUpdate.sh

For reference only here the output from my system :
ccmUpdate
/opt/IBM/Connections/addons/ccm/ccmDomainTool/../../../config.properties
Is existing CCM deployment : false
Please enter domain admin user password : password
Get DM Info command : /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/wsadmin.sh -conntype SOAP -host perc45.renovations.xyz -port 8879 -lang jython -username wsadmin -password password -f /opt/IBM/Connections/addons/ccm/ccmDomainTool/wkplc_GetDMInfo.py /opt/IBM/WebSphere/AppServer/profiles/Dmgr0/bin/dminfo.properties
http://C45.renovations.xyz:9080/wsi/FNCEWS40MTOM
*
Directory service provider name : IBM Virtual Member Manager
Domain name : ICDomain
Content Platform Engine webservice : FileNetP8WSI
File Storage Area root path : /opt/IBM/ContentStore/shared/ccm
Object store admin user : wsadmin
Object store display name : ICObjectStore
Object store name : ICObjectStore
JNDI data source : FNOSDS
JNDI XA data source : FNOSDSXA
Domain admin user : wsadmin
Possible Content Platform Engine Connection URI:
http://C45.renovations.xyz:9080/wsi/FNCEWS40MTOM
*
Geting connection to the Content Platform Engine URI : http://C45.renovations.xyz:9080/wsi/FNCEWS40MTOM ...
log4j:WARN No appenders could be found for logger (filenet_error.api.com.filenet.apiimpl.util.ConfigValueLookup).
log4j:WARN Please initialize the log4j system properly.
http://C45.renovations.xyz:9080/wsi/FNCEWS40MTOM
http://C45.renovations.xyz:9080/wsi/FNCEWS40MTOM
Updating Server Cache ...
Installing the 5.2.0 FP1 Social Collaboration User Identity Mapping Extensions AddOn ... done.
finished

Problems encountered during the update

Problem : ccmUpdate task was failing with :

./ccmUpdate.sh
ccmUpdate

/opt/IBM/Connections/addons/ccm/ccmDomainTool/../../../config.properties
Is existing CCM deployment : false
error:null
Cannot connect to any Content Platform Engine URI, please check whether the Connections Content Manager server is started

Solution : Back-up, then delete /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/dminfo.properties as documented in http://www-01.ibm.com/support/docview.wss?uid=swg21637792 .

Other lessons learned

If after running the './fncs-uninstall' task to uninstall FNCS you decide to delete the /opt/IBM/Connections/addons/ccm/FNCS directory, make sure to safe a copy of your configuration, before removing the directory .

In particular out-of-the-box we are storing the following 2 properties in fncs-sitePrefs.properties :

anonymousAccessEnabled=true
enablePropertySheetTemplateMinMax=true

Depending on your environment and configuration you may have added additional parameters . Make sure to set the parameters again in the updated version .

This problem does not occur if you run the'./fncs-uninstall' task only ( https://ibm.biz/BdxTGn ) . If you should have any problems or queries in regard to the FNCS update, please contact FileNet support .