When upgrading eDiscovery Analyzer to Version 2.2 Fix Pack 2 (or to any previous version), the upgrade overwrites the cacerts keystore file which is part of the eDiscovery Analyzer JRE. If this file was previously populated with your public certificate keys, they are lost. Because of this, you must re-import all of your public certificates after a version upgrade.
The cacerts file is located in EDA_INSTALL_DIR\_jvm22\jre\lib\security\cacerts. You would use this file if you want an SSL connection between eDiscovery Analyzer and a FileNet P8 content management server and you have to import your public certificate key for the P8 server into the cacerts file.
After an upgrade, the eDiscovery Analyzer server fails to start, or logging into eDiscovery Analyzer fails with communication errors to the FileNet P8 content management server.
After an upgrade, eDiscovery Analyzer can no longer communicate with the FileNet P8 content management server using SSL because a valid public certificate for use by HTTPS cannot be found.
Diagnosing the problem
Verify whether the FileNet P8 content management server public certificate is in the cacerts keystore file:
> cd EDA_INSTALL_DIR\_jvm22\jre\lib\security
> EDA_INSTALL_DIR\_jvm22\jre\bin\keytool.exe -list -v -keystore .\cacerts
Resolving the problem
To resolve this problem, save a copy of the cacerts file before you upgrade your eDiscovery Analyzer server.
After the upgrade, copy your saved cacerts file to EDA_INSTALL_DIR\_jvm22\jre\lib\security\cacerts.
Alternately, you can use the keytool command in EDA_INSTALL_DIR\bin\keytool to re-import your public certificate key or keys into the cacerts keystore file.
Note: The upgrade installer usually creates a backup file (such as eDiscoveryAnalyzer.zip). In this backup file, you should be able to locate the original cacerts file even if you did not back up the cacerts file before upgrading eDiscovery Analyzer.