Release Notes - IBM Watson Explorer Foundational Components, Version 10.0.0.10

Content

• Overview
• Upgrading
• System Requirements
• Limitations

Overview

IBM Watson Explorer Version 10.0.0.10 upgrades IBM Java to 8.0.6.20 and addresses security issues.  See the following Security Bulletin for more information:

• Security Bulletin: Vulnerability affects Watson Explorer Foundational Components (CVE-2020-1967)

For additional information about IBM Watson Explorer Version 10.0, see the Release Notes.

Back to top

Upgrading

For upgrade instructions, see Upgrading to Watson Explorer Foundational Components Version 10.0.0 Fix Packs .
 

Back to top

System Requirements

• Alfresco Community support is deprecated. Alfresco Community Connector will be removed in a future release. Consider to use Content Management Interoperability Services(CMIS) Connector as an alternative.

For information about the requirements for installing any Watson Explorer component, see Watson Explorer Version 10.0 system requirements.

Back to top

Limitations

• Annotation Administration Console (wex-aac-10.0.0.10-ee.tar or wex-aac-10.0.0.10-ee.zip for Enterprise Edition, wex-aac-10.0.0.10-ae.tar or wex-aac-10.0.0.10-ae.zip for Advanced Edition) is not included in this Fix Pack release. Please continue to use the Annotation Administration Console of Version 10.0.0.6 if you need to use Annotation Administration Console.
• If you upgrade to v10.0.0.10, and later upgrade to v11.0.0.1 or v11.0.1.0, the upgrade would fail because OpenSSL version downgrading is not possible. To work around this issue, ensure that any later upgrade to v11 is at least v11.0.2 and latest Fix Pack. For information about upgrading to v11.0.2, see Upgrading to Watson Explorer Foundational Components Version 11.0.2.
• If you use an older version of IBM DB2 JDBC driver, you might see a database connection failure with the error code as shown in the following technote: SqlException with message "Caught java.io.CharConversionException." and ERRORCODE=-4220. To work around this problem, upgrade the DB2 JDBC driver to Version 9.7 Fix Pack 5 or above.

Back to top