How to apply a Filenet CE iFix for IBM Connections (CCM) environment
David McCarthy 310000KJQX Visits (2154)
IBM Connections 6.0 CR1 on WAS 126.96.36.199 on Linux
For this document, we will be installing FileNet CPE 188.8.131.52 iFix 004.
The current version is 184.108.40.206.
The link to download 220.127.116.11 iFix004 is here:
1. Browse to http
2. Backup FN dbs
a. Follow all the steps in section "3.4.1 Backup DB2 FNOS and FNGCD (Object Store and GCD)" of this document:
3. Switch to Java 6 to upgrade FileNet
a. Follow all the steps in section "3.4.3 Switch to Java 6 to upgrade FileNet)" of this document:
4. Backup the existing FileNet EARs
a. Open a prompt and navigate to: /opt
b. Run command:
5. Download CPE 18.104.22.168 iFix 004.
a. Copy the Engine-ws.ear from the download .zip to this folder:
b. Choose to replace the 'Engine-ws.ear' file that is already there.
6. Use the ISC administrative console to uninstall the "FileNetEngine" application.
a. Ensure Connections is stopped, but nodeagent and DMGR are running.
b. In the ISC, go to Applications -> WebSphere Enterprise Applications.
c. Select "FileNetEngine" and click Uninstall.
d. Click OK.
e. After a few minutes, the application is uninstalled. Click Save.
f. Synch the nodes.
7. Clear cache
To help prevent errors when you are redeploying the updated version of Content Platform Engine, remove the application server cache
a. Stop all WAS processes.
b. Remove the FileNetEngine directory where the application server cache data is stored.
For example, the default Windows path for this directory is:
Specifies the profile for Content Platform Engine
Specifies the name of the Content Platform Engine application server instance node
Specifies the name of the Content Platform Engine application server instance
8. Start the FileNet Configuration Manager
a. Navigate to /IBM
b. Run configmgr.
c. Open profile from here:
9. Open "Edit Application server Properties" dialog.
a. Fill in the right details:
b. Click Test Connection.
10. Double click on "Configure Bootstrap and text Extraction" task.
a. Select Upgrade.
b. In the "Bootstrapped EAR file" field, browse to the Engine-ws.ear in this location:
c. Click "Run Task".
This will take several minutes. At the end, you should see:
Finished running Configure Bootstrap and Text Extraction
INFO: Configuring Bootstrap data ...
INFO: Text extraction version in initial EAR file: "8.5
INFO: Text extraction version in Configuration Manager: "8.5
INFO: Content Search Services API version in initial EAR file: "22.214.171.124FP007, 6119, 2017/05/25 15:07:16.360"
INFO: Content Search Services API version in Configuration Manager: "126.96.36.199FP007, 6119, 2017/05/25 15:07:16.360"
INFO: Installing Text extraction version 8.5.
INFO: Executing Platform: win64
INFO: Done installing and updating EAR file.
INFO: Product name for this deployment: IBM FileNet Content Platform Engine
INFO: Product version for this deployment: 5.2.1
INFO: Product installation directory for this deployment: C:\I
INFO: Product GUID for this deployment: 4640
11. Deploy the upgraded FileNetEngine application.
a. Ensure the DMGR and nodeagent(s) are running.
b. Double-click on the "Deploy Application" task to deploy the updated FileNetEngine application.
c. Check the details are correct for your environment. The "Bootstrapped EAR path" should be the same as the one in step 10.
d. Click "Run Task".
After a few minutes, you should see:
Finished running Deploy Application
12. Follow these steps to re-apply the Waltz & Sonata JARs to the updated FileNetEngine:
13. Follow the steps in section "3.4.6 Switch to Java 8 after upgrading FileNet" in this document:
14. Remap FileNetEngine application to the IHS server.
a. Go to the ISC console.
b. Navigate to Applications -> FileNetEngine -> Manage Modules.
c. Select all the modules and map them to the IHS server and WAS cluster:
d. Re-generate the plugin.
e. Propagate to the HTTP server.
f. Restart IHS.
15. Restart Connections.
16. Access the FileNet/Engine page again and verify the build number has been correctly updated as follows:
Congratulations! You have successfully applied a iFix to the FileNet CE!