IBM Support

Release Notes - IBM Watson Explorer Foundational Components, Version 11.0.2

Release Notes


Abstract

This document describes new features, known issues and workarounds, and installation information for the foundational components of IBM Watson Explorer Version 11.0.2.

Content

Watson Explorer V11.0.2 Release Notes

Overview

IBM Watson Explorer Version 11.0.2 helps search, analyze, and interpret vast amounts of structured and unstructured information across many enterprise systems and data repositories. It also provides a cost-effective and efficient entry point for exploring the value of big data technologies through a powerful framework for developing applications that use existing enterprise data. Watson Explorer Content Analytics brings its powerful text analytics to Watson Explorer applications along with its advanced content mining capabilities. IBM Watson Explorer Version 11.0.2 also delivers enhancements to the Application Builder and Watson Explorer Engine modules of the Watson Explorer suite along with many other new and improved capabilities.

The IBM Watson Explorer Version 11.0.2 announcement is available here. If prompted to do so, select the appropriate values for the Home Country and Site Language fields and click Continue. You can then enter Watson Explorer in the search box and click Search. See the announcement for the following information: Detailed product description Product-positioning statement Packaging and ordering details

Back to top


Installation

For step-by-step installation instructions, see Installing and Integrating IBM Watson Explorer Foundational Components and Watson Explorer Upgrade Options. For upgrade information, see Upgrading to Watson Explorer Foundational Components Version 11.0.2. To install the Annotation Administration Console, extract all files from the wex-aac-11.0.2.x archive file, and then see: Installing Annotation Administration Console. Note: For v11.0.2, the installation program files are named install.bin (Linux) and install.exe (Windows). The names in Installing Annotation Administration Console are incorrect.

Back to top


System Requirements

For information about the requirements for installing any Watson Explorer component, see Watson Explorer Version 11.0.2 system requirements.
Note: Red Hat Enterprise Linux versions 6 are not supported after Version 11.0.2.6.

Back to top

Release Notes for Version 11.0.2.19

What's new in 11.0.2.19

Watson Explorer Foundational Components V11.0.2.19 includes PSIRT fixes.

Version 11.0.2 fix pack 19 is the final release since IBM Watson Explorer version 11.0.2.x is EOS and removed from future releases.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issue and work-around

  • The Fix for Content Analytics Studio is not included in this Fix Pack release. Continue to use the Content Analytics Studio of Version 11.0.2.2 if you need to use Content Analytics Studio.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.19, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.
  • The Salesforce connector does not start in version 11.0.2.19. See the following work-around to solve the issue.
    1. Copy the folders connector-salesforce-5.1.15.zip and connector-box-5.1.15.zip under $ENGINE/lib/java/plugins/ to your working directory
    2. Run the following command in your working directory. 
      unzip connector-salesforce-5.1.15.zip plugin.xml
    3. Under the runtime section, add the following line: 
      <library id="org.scala-lang:scala-library:jar:2.10.7" path="lib/scala-library-2.10.7.jar" type="code"/>
    4. Run the following commands: 
      
$ zip connector-salesforce-5.1.15.zip plugin.xml
$ unzip connector-box-5.1.15.zip lib/scala-library-2.10.7.jar
$ zip connector-salesforce-5.1.15.zip lib/scala-library-2.10.7.jar
    5. Copy the folder connector-salesforce-5.1.15.zip back to $ENGINE/lib/java/plugins/

Note

EXSLT function exlt:nodeset is no longer available. Use exsl:node-set instead.

Lotus Notes v9.x and v10.x will be deprecated and end of support effective 1 June 2024, since the underlying software is no longer supported after that date.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.18

What's new in 11.0.2.18

Watson Explorer Foundational Components V11.0.2.18 includes PSIRT fixes.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues

  • The Fix for Content Analytics Studio is not included in this Fix Pack release. Please continue to use the Content Analytics Studio of Version 11.0.2.2 if you need to use Content Analytics Studio.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.18, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

Note

EXSLT function exlt:nodeset is no longer available. Use exsl:node-set instead.

Lotus Notes v9.x and v10.x will be deprecated and end of support effective 1 June 2024, since the underlying software is no longer supported after that date.

Deprecated and Removed Features in Version 11.0.2.18

The following feature, which is part of Watson Explorer Foundational Components is no longer supported.

  • Search security feature of OneDrive for Business Connector

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.17

What's new in 11.0.2.17

Watson Explorer Foundational Components V11.0.2.17 includes PSIRT fixes.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues

  • The Fix for Content Analytics Studio is not included in this Fix Pack release. Please continue to use the Content Analytics Studio of Version 11.0.2.2 if you need to use Content Analytics Studio.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.17, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

Note

EXSLT function exlt:nodeset is no longer available. Use exsl:node-set instead.

Lotus Notes v9.x and v10.x will be deprecated and end of support effective 1 June 2024, since the underlying software is no longer supported after that date.

 

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.16

What's new in 11.0.2.16

Watson Explorer Foundational Components V11.0.2.16 includes PSIRT fixes.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues

  • The Fix for Content Analytics Studio is not included in this Fix Pack release. Please continue to use the Content Analytics Studio of Version 11.0.2.2 if you need to use Content Analytics Studio.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.16, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

Note

EXSLT function exlt:nodeset is no longer available. Use exsl:node-set instead.

Deprecated and Removed Features in Version 11.0.2.16

Products integrated in Analytical Components

The below platforms are no longer supported since the supported software versions have reached end of support (EOS).

  • Cognos Analytics 11.0.6.0 (Formerly known as Cognos BI)
  • Lotus Notes Version 8 (Later versions are supported for crawling)
  • IBM Open Platform with Apache Hadoop (Biginsights)
  • Integration with IBM Content Classification

Lotus Notes v9.x and v10.x will be deprecated and end of support effective 1 June 2024, since the underlying software is no longer supported after that date.

 

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.15

What's new in 11.0.2.15

Watson Explorer Foundational Components V11.0.2.15 includes PSIRT fixes.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues

  • The Fix for Content Analytics Studio is not included in this Fix Pack release. Please continue to use the Content Analytics Studio of Version 11.0.2.2 if you need to use Content Analytics Studio.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.15, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

Note

EXSLT function exlt:nodeset is no longer available. Use exsl:node-set instead.

Removed Features in Version 11.0.2.15

Data sources in Analytical Components

  • Data sources that are supported by IBM Content Integrator
  • IBM InfoSphere Federation Server

Features in Foundational Components

  • Results Module
  • Big Index
  • The Collection Broker
  • ASPX End Point API
 

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.14

What's new in 11.0.2.14

Watson Explorer Foundational Components V11.0.2.14 includes PSIRT fixes.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues

  • The Fix of Content Analytics Studio is not included in this Fix Pack release. Please continue to use the Content Analytics Studio of Version 11.0.2.2 if you need to use Content Analytics Studio.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.14, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

Note

EXSLT function "exlt:nodeset" is no longer available. User can use "exsl:node-set" instead.

Some of the following features may be deprecated for the future release. While some features may continue to work with the existing components (Foundational Components / Analytical Components), few features may be deprecated for all the components.

Data sources in Analytical Components

  • Data sources that are supported by IBM Content Integrator
  • IBM InfoSphere Federation Server

Features in Foundational Components

  • Results Module
  • Big Index
  • The Collection Broker
  • ASPX End Point API

Removed Features in Version 11.0.2.14

The following data source connectors in Watson Explorer Foundational Components are removed.

In Foundational Components

  • Large Database Connector
  • Legacy SharePoint Connector
  • Universal SAP KM Connector
  • Enovia Connector 
  • Exchange 2003 / 2007 Connector
  • SMB Fileshares Connector 
  • Confluence Connector
  • IBM Web Content Manager Connector
  • Alfresco Community Connector
 

The following converter in Watson Explorer Foundational Components is removed.

  • WordPerfect to HTML

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.13

What's new in 11.0.2.13

Watson Explorer Foundational Components V11.0.2.13 includes PSIRT fixes.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues and limitations

  • “An unexpected error occurred: [[could not attach calling thread to jvm: [Embedded JVM is shut down.]]]” occurs when using a Language Support stream in your collection, and indexer-service stops working. Please refer to the remediation in the technote.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.13, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.
 

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.12

What's new in 11.0.2.12

Watson Explorer Foundational Components V11.0.2.12 includes PSIRT fixes.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Disabled features

The Connector, Java converter, and Lexical analysis logging functions are disabled to address the security vulnerabilities in Apache Log4j 1.x in Version 11.0.2.12 or later.

Known issues and limitations

  • “An unexpected error occurred: [[could not attach calling thread to jvm: [Embedded JVM is shut down.]]]” occurs when using a Language Support stream in your collection, and indexer-service stops working. Please refer to the remediation in the technote.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.12, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.11

What's new in 11.0.2.11

New Data Source Support

  • HCL Domino 11.0.1 is newly supported.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues and limitations

  • “An unexpected error occurred: [[could not attach calling thread to jvm: [Embedded JVM is shut down.]]]” occurs when using a Language Support stream in your collection, and indexer-service stops working. Please refer to the remediation in the technote.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.11, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.10

What's new in 11.0.2.10

Watson Explorer Foundational Components V11.0.2.10 upgrades IBM Java to 8.0.6.30 and includes PSIRT fixes.

System Requirements in Version 11.0.2.10

  • Red Hat Enterprise Linux (RHEL) Server 8 on x86-64 platform is newly supported.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues and limitations

  • “An unexpected error occurred: [[could not attach calling thread to jvm: [Embedded JVM is shut down.]]]” occurs when using a Language Support stream in your collection, and indexer-service stops working. Please refer to the remediation in the technote.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.10, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.9

What's new in 11.0.2.9

Watson Explorer Foundational Components V11.0.2.9 upgrades IBM Java to 8.0.6.25 and includes PSIRT fixes.

System Requirements in Version 11.0.2.9

  • Windows Server 2019 Standard Edition is newly supported.

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues and limitations

  • “An unexpected error occurred: [[could not attach calling thread to jvm: [Embedded JVM is shut down.]]]” occurs when using a Language Support stream in your collection, and indexer-service stops working. Please refer to the remediation in the technote.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.9, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.8

What's new in 11.0.2.8

Watson Explorer Foundational Components V11.0.2.8 upgrades IBM Java to 8.0.6.10 and includes PSIRT fixes.

Supported software in Version 11.0.2.8

  • Oracle WebCenter Content v12 is newly supported as a Data Source.
  • 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 the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues and limitations

  • Watson Explorer Engine's search API may hang depending on document contents. Refer to the technote to fix the issue.
  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.8, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.7

What's new in 11.0.2.7

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues and limitations

  • To upgrade AppBuilder from version 11.0.2.5 or before to 11.0.2.7, you must first upgrade ZooKeeper to 11.0.2.6 or later. See the Readme.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.6

What's new in 11.0.2.6

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues and limitations

  • When you merge conflicted nodes in Synchronize Repository Nodes page or Import Repository Nodes page from Engine administration tool, “Invalid Token: (null)” error may occur. Refer to the technote to fix the error.
  • To upgrade AppBuilder to 11.0.2.6, you must first upgrade ZooKeeper to 11.0.2.6. See the Readme.
  • Users will not be able to configure SMTP over SSL/TLS in 11.0.2.6 and later versions.
  • When you install Query Modifier after installing 11.0.2.6, you need to modify querymodifier.yml before starting Query Modifer service. Set true for the register parameter in the engine section.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.5

What's new in 11.0.2.5

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Known issues

  • When you install Query Modifier after installing 11.0.2.5, you need to modify querymodifier.yml before starting Query Modifer service. Set true for the register parameter in the engine section.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.4

What's new in 11.0.2.4

For the information about connecting to Fix Central to obtain the readme file or fix pack software, see the download document.

Note

Some of the following features may be deprecated for the future release. While some features may continue to work with the existing components (Foundational Components / Analytical Components), few features may be deprecated for all the components.

Supported Data Sources

In Analytical Components

  • Data sources that are supported by IBM Content Integrator
  • IBM InfoSphere Federation Server

In Foundational Components

  • Large Database Connector
  • Legacy SharePoint Connector
  • Universal SAP KM Connector
  • Enovia Connector 
  • Exchange 2003 / 2007 Connector
  • SMB Fileshares Connector 
  • Confluence Connector
  • IBM Web Content Manager Connector

Supported features

In Foundational Components

  • Results Module
  • Big Index
  • The Collection Broker
  • ASPX End Point API

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top

Release Notes for Version 11.0.2.3

What's new in 11.0.2.3

This section summarizes the enhancements in Version 11.0.2.3 and provides related the additional information. Also, consult the IBM Watson Explorer 11.0.2.3 Readme document, and the download document.

Watson Explorer Engine Connectivity

This section summarizes Connector enhancements bundled in Version 11.0.2.3 and provides related links to the additional information.

New Data Source Support

Following data sources are newly supported to crawl.

  • IBM FileNet Content Manager Version 5.5.0
  • Microsoft Windows Remote Filesystem

Watson Explorer Application Builder

Following features are newly introduced.

  • Spell correction with the search context
    • An administrator can enable/disable spell correction for each search context.
  • Developer role
    • The Developer role is introduced for the user entity. Administrators can assign users to the developer role and can specify which administrator UI pages (Data sources, Entities, Endpoints, Layouts, and Settings) can be accessed by developers.

Known issues

  • Annotation Administration Console (wex-aac-11.0.2.3-ee.tar or wex-aac-11.0.2.3-ee.zip for Enterprise Edition, wex-aac-11.0.2.3-ae.tar or wex-aac-11.0.2.3-ae.zip for Advanced Edition) is not included in this Fix Pack release. Please continue to use the Annotation Administration Console of Version 11.0.2.2 if you need to use Annotation Administration Console.

Back to top


Note

Some of the following features may be deprecated for the future release. While some features may continue to work with the existing components (Foundational Components / Analytical Components), few features may be deprecated for all the components.

Supported Data Sources

In Analytical Components

  • Data sources that are supported by IBM Content Integrator
  • IBM InfoSphere Federation Server

In Foundational Components

  • Large Database Connector
  • Legacy SharePoint Connector
  • Universal SAP KM Connector
  • Enovia Connector 
  • Exchange 2003 / 2007 Connector
  • SMB Fileshares Connector 
  • Confluence Connector
  • IBM Web Content Manager Connector

Supported features

In Foundational Components

  • Results Module
  • Big Index
  • The Collection Broker
  • ASPX End Point API

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top


Release Notes for Version 11.0.2.2

What's New in 11.0.2.2

This section summarizes the enhancements in Version 11.0.2.2 and provides related the additional information.

Also consult the IBM Watson Explorer 11.0.2.2 Readme document, and the download document.

New Platform Support Windows Server 2016 is now supported. See Software Product Compatibility Reports (SPCR) for the latest information. Watson Explorer Engine For the information about List of fixes in Version 11.0.2.2, see IBM Watson Explorer Foundational Components, Version 11.0.2 Fix Pack 2 Readme. For information about connecting to Fix Central to obtain the readme file or fix pack software, see the download documents. Integrate Watson Explorer API with DataPower Gateway Watson Explore api-soap application now generates the WSDL that passes the validation by IBM DataPower Gateway. Watson Explorer Engine Connectivity This section summarizes Connector enhancements bundled in Version 11.0.2.2 and provides related links to the additional information. New Data Source Support Following data sources are newly supported to crawl. Documentum Version 7 Sharepoint 2016 LDAP Connector Incremental Crawl support Incremental Crawl function crawls newly created and updated entries from the last crawling. This function does not detect the deleted LDAP entries and a full crawl is required to sync the deletes. Incremental Crawl function is only supported for Directory servers which are compliant with LDAP v3. Watson Explorer Application Builder Performance improvement Several updates are available to improve Application Builder performance. New server startup options to specify dictionaries for spell correction. and to stop automated dictionary build. Disable logging and monitoring option for Websphere Liberty Profile. Topic cloud widget stops checking display condition by default. The administrator must specify the condition explicitly to hide the widget when the content is empty. SAML authentication support with Microsoft Active Directory Federation Server (ADFS) Starting from Watson Explorer Application Builder 11.0.2.2, Application Builder supports SAML (Security Assertion Markup Language) claims based authentication using Microsoft Active Directory Federation Service (ADFS) 3.0 as the SAML ID provider.

Note

Some of the following features may be deprecated for the future release. While some features may continue to work with the existing components (Foundational Components / Analytical Components), few features may be deprecated for all the components.

Supported Data Sources

In Analytical Components

  • Data sources that are supported by IBM Content Integrator
  • IBM InfoSphere Federation Server

In Foundational Components

  • Large Database Connector
  • Legacy SharePoint Connector
  • Universal SAP KM Connector
  • Enovia Connector 
  • Exchange 2003 / 2007 Connector
  • SMB Fileshares Connector 
  • Confluence Connector
  • IBM Web Content Manager Connector

Supported features

In Foundational Components

  • Results Module
  • Big Index
  • The Collection Broker
  • ASPX End Point API

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top


Release Notes for Version 11.0.2.1

What's New in 11.0.2.1

This section summarizes the enhancements in Version 11.0.2.1 and provides related the additional information.

Watson Explorer Engine

For the information about List of fixes in Version 11.0.2.1, see IBM Watson Explorer Foundational Components, Version 11.0.2 Fix Pack 1 Readme. For information about connecting to Fix Central to obtain the readme file or fix pack software, see the download documents.

Watson Explorer Engine Connectivity

This section summarizes Connector enhancements bundled in Version 11.0.2.1 and provides related links to the additional information.

 

New Data Source Support

Following data sources are newly supported to crawl.

  • IBM Connections Version 6.0
  • IBM WebSphere Portal Version 9.0 and Web Content Manager(WCM) Version 9.0

The seed of WCM seedlist continuous update support

The seed of WCM seedlist in WCM and Portal Connector Version 1.0.17 or previous versions deletes all crawled documents from Index and recrawl them with Continuous Update mode. The seed of WCM seedlist in connector Version 1.0.18 reflects an incremental seedlist of WCM and only updates the changes on the data source.

Salesforce Connector Version 5.1.0 or later requires generated libraries

Salesforce Connector Version 5.1.0 or later versions requires the generated partner and metadata jars to crawl the custom Salesforce components introduced to your environment. See Step 2: Generate or Obtain the Web Service WSDL and Step 3: Import the WSDL File Into Your Development Platform in SOAP API Developer Guide about how to generate your own libraries from Salesforce WSDL files.

When configuring the connector, specify the directory containing the generated libraries such as force-wsc-$version.jar and its dependencies. See https://mvnrepository.com/artifact/com.force.api/force-wsc about force-wsc-$version.jar and its dependencies.

Box Connector enhancement

  • Box Connector Version 5.1.0 supports to crawl Box contents with proxy settings. Specify the proxy settings in Box Connector Seed > General Settings > HTTP specific.
  • Box Connector Version 5.1.0 supports to use private keys with encrypted or unencrypted PEM format in addition to existing Unencrypted DER format. See http://www.ibm.com/support/docview.wss?uid=swg22002611 for more information.

IBM WCM and Portal Connector Known Issues

The Known Issues describes the specific version such as WCM Version 8.5 or Portal Version 8.5, but it is also applicable to the later versions of WCM and Portal, such as Version 9.0.

Watson Explorer Application Builder

For information about List of fixes in Version 11.0.2.1, see IBM Watson Explorer Foundational Components, Version 11.0.2 Fix Pack 1 Readme. For information about connecting to Fix Central to obtain the readme file or fix pack software, see the download documents.

Note

Some of the following features may be deprecated for the future release. While some features may continue to work with the existing components (Foundational Components / Analytical Components), few features may be deprecated for all the components.

Supported Data Sources

In Analytical Components

  • Data sources that are supported by IBM Content Integrator
  • IBM InfoSphere Federation Server

In Foundational Components

  • Large Database Connector
  • Legacy SharePoint Connector
  • Universal SAP KM Connector
  • Enovia Connector

Supported features

In Foundational Components

  • Results Module
  • Big Index
  • The Collection Broker
  • ASPX End Point API

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion.

Back to top


Release Notes for Version 11.0.2

What's New in 11.0.2

IBM Watson Explorer Version 11.0.2 introduces new features and provides enhancements to the existing product capabilities.

Watson Explorer Engine

The following updates and improvements have been made to Watson Explorer Engine in Version 11.0.2.

  • The Velocity command-line utilities (velocity-startup, velocity-shutdown, velocity-webserver, velocity-cmd, and velocity-config) have been completely replaced with new tools in Watson Explorer Engine version 11.0.2. The new tools, originally introduced in Watson Explorer Engine version 11.0.0.3, are: engine-start, engine-shutdown, engine-cmd, engine-export, engine-import, engine-status, generate-key, embedded-webserver, and embedded-webserver-config. The new Engine utilities cannot be used interchangeably with the Velocity utilities. If your startup, shutdown, and other processes use the Velocity utilities, you will need to update them after upgrading to Watson Explorer version 11.0.2. For more information, see: https://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.2/com.ibm.swg.im.infosphere.dataexpl.install.doc/c_installation-sysadmin-cmd.html
  • This will be the final release of SharePoint Web Parts for Watson Explorer. Beginning with the next release, this feature will be removed from the product and SharePoint Web Parts will be made available as open source.
  • Beginning with Watson Explorer 11.0.2, the following three converters are no longer available: Entity Extractor (vse-converter-entity-extractor), Sentiment Analyzer (vse-converter-sentiment-analyzer), and IBM Text Analytics Converter (vse-converter-text-analysis). For backwards compatibility, the SystemT functionality that powered these converters has moved to WEX Analytical Components.
  • A converter issue was fixed that could cause 100% CPU utilization by a java process. This was caused by the crawler-service process terminating without first sending a "jvm-shutdown" message.
 

Watson Explorer Engine Connectivity

Bundled with this release of Watson Explorer Engine is the following connector:

  • Box Connector - The Box connector enables Watson Explorer Engine applications to crawl Box repositories and index the information that they contain. For more information, see http://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.2/com.ibm.swg.im.infosphere.dataexpl.connector.box.doc/c_box-introduction.html.
  • OneDrive for Business Connector - The OneDrive for Business connector enables Watson Explorer Engine applications to crawl OneDrive for Business Sites from SharePoint Personal sites, and index the information that they contain. The OneDrive for Business connector allows you to crawl Microsoft OneDrive for Business objects, such as documents, user profiles, site collections, blogs, list items, membership lists, directory pages, and more. For more information, see http://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.2/com.ibm.swg.im.infosphere.dataexpl.connector.od4b.doc/c_od4b-introduction.html.

The following updates and improvements have been made to Watson Explorer Engine Connectors in Version 11.0.2.

  • Updates have been made to the steps for creating a crawling account for Microsoft Office SharePoint Server 2007, and Microsoft SharePoint online.
  • Additional seed options have been added to the WCM connector.

 

Watson Explorer Application Builder

The following new features have been introduced in Watson Explorer Application Builder, Version 11.0.2:

  • Watson Discovery Service

    The functionality to enable you to add Watson Discovery services as data sources in Application Builder is released as an interim fix on IBM Fix Central. For information, see the release notes http://www.ibm.com/support/docview.wss?uid=swg27049247 You can read more about Watson Discovery services as data sources at http://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.2/com.ibm.swg.im.infosphere.dataexpl.appbuilder.doc/backends-hybrid-d.html

The following updates and improvements have been made to Watson Explorer Application Builder in Version 11.0.2:

  • Chart Widget

    For the chart widget, a time display was added. Also, added X axis and Y axis title fields. For information, see http://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.2/com.ibm.swg.im.infosphere.dataexpl.appbuilder.doc/r_de-ab-devapp-pages-widget-chart.html

  • Saved Search

    Fixed an issue with deleting saved searches. If a saved search was deleted from a workspace, it was not entirely removed, which meant that it ran according to the monitoring interval that was selected by the user and possibly consumed some processing power. End-user documentation about saving searches is located on the following application page, http://localhost:8080/AppBuilder/help/search_page#searching_saving. For information about configuring workspaces, see http://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.2/com.ibm.swg.im.infosphere.dataexpl.appbuilder.doc/r_de-ab-devapp-global-options.html

  • Debugging

    Fixed an issue with Rails debugging. When trying to troubleshoot Application Builder applications, enabling Rails DEBUG level logging didn't produce additional messages. Now, DEBUG-level logs will show.

  • Email Notifications

    Fixed an issue with not being able to save a blank form for email notifications settings. This issue was a problem if, after enabling email notifications, you wanted to disable notifications and remove field values. For information about email notifications, see http://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.2/com.ibm.swg.im.infosphere.dataexpl.appbuilder.doc/t_de-ab-devapp-email-notifications.html

  • Natural Language Querying

    Fixed an issue for natural language querying. If query expansion was also enabled and the first search term had an expansion, the query incorrectly applied the search operators. For example, if your query was car broken, and car expanded the synonym automobile, the query should have been (car OR automobile) AND broken. The issue caused the query to be car OR (automobile AND broken). For information about natural language querying in Application Builder, see http://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.2/com.ibm.swg.im.infosphere.dataexpl.appbuilder.doc/t_de-ab-devapp-search-enable-nlq.html

    The link to disable natural language querying on the search results page was moved to the first page of search results.

Watson Explorer Results Module

There are no updates to report for Version 11.0.2.

Back to top

Known Issues in 11.0.2

At the time of publication, the following issues are known to be unresolved in the Watson Explorer foundational components:

Watson Explorer Engine

  • The indexer-service can potentially crash if an existing collection is upgraded, then a user performs a query on the upgraded collection that is identical to the query that was performed before the upgrade. The workaround is to remove all of the files of the form .../opt/ibm/WEX/Engine/data/search-collections/*/*/cache/viv_*
  • When using the search history display module, the first search listed in history should end with "under " but instead ends with "under "
  • The Scheduler Service is crashing on Windows when scheduled over 332 days in advance. The workaround is:
    1. From Management > Services, start the Scheduler Service.
    2. Click the Add a Scheduled Task button, choose Start the Query Service from the list. Click Add.
    3. Under Conditions, choose the Add a Scheduled Time button. Choose Fixed Intervals, then click Add.
    4. Set the Fixed Intervals to 331 days (or a lower number), click OK.

    See http://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.1/com.ibm.swg.im.infosphere.dataexpl.engine.doc/c_management-scheduler.html for more information about scheduling tasks in Watson Explorer Engine.

  • Occasionally, Query Modifier may fail to start, throwing the following stack trace:

    java.lang.IllegalStateException: Failed to load ApplicationContext
    ...
    Caused by: java.util.ConcurrentModificationException: null
    ...

    The work-around is to start Query Modifier again.
 

Watson Explorer Application Builder

Watson Explorer Annotation Administration Console

  • Linux users importing a peer repository may see an "Unhandled signal 11" message after clicking View or Merge on a repository element with conflicting versions. This error can be safely ignored. To import the remote element, delete the local version manually first.
  • If you set up remote-push in a version of Watson Explorer earlier than version 11.0.0.1, and did not have user names and passwords specified in your remote-push configuration, remote-push and mirror configurations will stop working when you install Watson Explorer version 11.0.0.3. In addition, if your remote-push configuration includes unencrypted passwords, remote-push will stop working when you install Watson Explorer version 11.0.0.3. To fix this issue, see High Availability and Scalability Through Distributed Indices.
  • Beginning with Watson Explorer version 11.0.0.1, all Watson Explorer Engine user passwords are secured using the scrypt algorithm, which generates one-way cryptographic hashes. Password hashing may increase your ingestion or query times. If this affects your performance significantly, you may disable it. To learn how to do so, see Disabling Password Hashing. In addition, if you are using the Native Document Export feature, password hashing must be disabled for the ICS user(s). See Adding Native Document Export to a Display for more information about native document export and ICS users.
  • In the Watson Explorer Engine Administration Tool, the following error can occur when attempting to update an existing scheduled job: "Can't get element with elt-id="". Existing scheduled tasks cannot be updated as a result. To solve this problem, create a new scheduled task, enter the required fields, and save it. All previously existing tasks can now be edited. If desired, delete the new task after making your edits.
  • The velocity-shutdown command may display the error message "os: process already finished" and return a non-zero exit code when shutting down Watson Explorer Engine. To ensure Watson Explorer Engine has shutdown completely, re-run velocity-shutdown until it no longer displays the error message.
    • When upgrading from Watson Explorer 9.0.0.3 or earlier, if you applied the 9.0.0.3-WS-WatsonExplorer-Windows-HF001 hotfix posted on Fix Central prior to March 23, 2015, you will need to perform an additional step during your installation. This is because the MD5 checksum values that were documented in that hotfix were incorrect, and as a result the files listed in the hotfix will not be deleted during the uninstallation of Watson Explorer 9.0.0.x. To work around this issue, do one of the following before starting your installation of 11.0.0.3:
      • Manually delete these files from your system after uninstalling the 9.0.0.x software.
      • Before uninstalling 9.0.0.x, go to Fix Central and reapply the hotfix. The MD5 values listed in the version posted on March 23, 2015 will delete the files correctly.
    • Installation Manager might crash when run on Red Hat Linux 6.5 because of an issue with out-of-date graphics libraries. To work around this issue, either modify the IM/IMLinux/install.ini file in the offering directory (see IBM Installation Manager can not start from GUI mode for instructions) or upgrade the Installation Manager libraries (see IBM Installation Manager and IBM Packaging Utility GUI crashes while advancing through wizard screens on recent updates of RHEL 6). Alternatively, you can use the console installer to completely bypass this issue.
    • Only an Administrator should start IBM Knowledge Center. If a non-Administrator starts an instance of the service, that instance might not be detected during an uninstall.
    • On Windows, there can be an issue deleting data on a search collection if the file path is longer than 260 characters. To work around this issue, keep collection names as short as possible, but descriptive (for example, "docs" instead of "crawled-documents") or shorten the path to the installation directory (or the collection's data directories if located elsewhere). Contact IBN Software Support if you see errors (for example, in system reporting) regarding an inability to delete files and those file paths are >= 260 characters.
    • If the Maximum JVM Idle Time is set to 0 and you enqueue a large number of documents, such as 50 or more, in quick succession, many of the enqueues are rejected with the following error: [JAVA_CONVERTERS_REMOTE_JVM_COMMUNICATION_FAILED] There was a problem connecting or communicating with the JVM used for running Java converters. Last system error was: Connection refused. To work around the issue, increase the maximum JVM idle time to a value greater than 5.
    • The template Java converter that is described in the tutorial for the Java converter might not compile with some versions of Apache Ant. The Java converter tutorial was tested and successfully compiled with Version 1.7.1, which is available from the Apache Ant archive page.
    • If a collection is configured with invalid parameters (for example, specifying a stemmer that does not exist), an issue might arise where the indexer service enters a continuous restart state. This functionality is documented in the Indexing section. Parameters that can contain invalid values are:
      • The stemmer of a custom language stream.
      • The path name for the PEAR file for a custom content analytics stream.
      • In the Advanced section of the global settings for the indexer, the Lexical analysis logging configuration field. This field has no administrative use other than potentially as a tool for complex debugging.
      • Also in the Advanced section, the Lexical analysis JVM arguments field.
      If you encounter this issue, stop the crawler, correct the configuration, and restart the indexer.
    • (Linux only) If you use the PDF to HTML converter for PDFs that use fonts of double-byte character sets, some text might not be extracted. Text that is not extracted is not included in the converted document. To work around the issue, you can use the PDF to text converter instead. Because the two converters work differently, you might see slight differences in the output of the converted documents.
    • When installing Watson Explorer Engine in non-admin mode on a Microsoft Windows system, the redistributable Microsoft Visual C++ runtime components that are required by Watson Explorer Engine are not installed correctly. This issue can prevent any of the Watson Explorer Engine Windows executables from running correctly. This problem does not occur if Watson Explorer Engine is installed by a user with administrative privileges. To resolve this problem, remove the non-admin installation and reinstall as a user with administrative privileges.
    • When performing a silent installation of Watson Explorer, if any nodes have been removed from a response file, the value for these nodes will be set to the default value.
    • When using continuous update mode for the Oracle WCC connector, filters are not supported if the universal query format is used. If filters are required, use the database query format.
    • When saving a refined query to a folder using the Watson Explorer Engine display, the less than symbol is not supported in the query label field. If the less than symbol is used, the label will be truncated to the content before the less than symbol.
    • Enqueueing a vse-key delete node on a distributed indexing server might result in one corresponding audit log entry on the client when two are expected.
    • When using the Web Parts for Watson Explorer, removing the HTTP authentication user name and password will fail if Remember passwords for sites is enabled in your browser.
    • When using the reporting feature, if the Split System Reporting Database option is set to something other than the default value of monthly, Watson Explorer Engine might incorrectly log some error messages to the monthly reporting database. Similarly, the System Reporting Database Maximum option is ignored, so it might grow in size until hitting the default maximum limit of 2GB.
    • When adding a new seed to a collection, the list of seed types to choose from includes vse-crawler-seed-TEMPLATE. This seed is intended for IBM internal development and should not be used.
    • If you remove a connector plug-in, a search collection will continue to refresh without generating an error message that the connector plug-in was removed.
    • The Watson Explorer Engine internal web server could be vulnerable to the denial-of-service attack (DoS) that is described on the Apache wiki. If you are using the Watson Explorer Engine internal web server as an Internet facing portal, follow the mitigation steps listed at that link.
    • The vsw-form erroneously states that XML is acceptable for the document query condition field. This text is incorrect. XML should not be used for the document query condition field.
    • Bulk collaboration features (express tagging and renaming, adding, or deleting folders) have crawl-url priority of 1, which might result in a delay for users during normal refresh operations.
    • Links in the crawl graph might not be consistent if crawl URLs are enqueued with the parent-url attribute set. This behavior can cause a potential issue when switching a client to a server in distributed indexing if you are using the IO SharePoint Connector.
    • The use of non-ASCII characters in a Watson Explorer Engine installation path is not supported.
    • Calling the search-collection-read-only-all API function on a server with a large number (thousands) of collections results in increased CPU and memory usage, and can make the server appear to be unresponsive while the search collections on that server are being processed.
    • When using distributed indexing, if all data is deleted from the master server and a crawl is initiated, the client servers never attempt to synchronize, nor do they complain about the data mismatch.
    • Database Connector 5.0.1: In this version of the Database Connector, the document URLs will include the fetch size. This should not have any consequences, unless the fetch size is changed while continuous update is enabled.
    • IO SharePoint connector: When building access control lists (ACLs), the connector does not check the web application policy. When security is enabled for the search collection, the SharePoint user for the crawling account cannot see search results if the account was granted only Full Read permissions at the web application policy level. To work around the issue, grant the SharePoint user for the crawling account Full Read permissions at the site level and document level.
    • In some cases, large documents (for example, large Microsoft Excel files) will fail during conversion, with an error message that references the ISYS_XML_MEMORY_LIMIT environment variable. To workaround this issue, set the environment variable ISYS_XML_MEMORY_LIMIT high enough to allow the converter to process the document.
    • Nested document nodes can cause the query-meta application to exit abnormally.
    • The Watson Explorer autocomplete feature does not collect reporting information.
    • Watson Explorer might fail to open files with a path length of over 255 characters on Microsoft Windows systems.
    • When the Watson Explorer Engine Search Web Parts repair installer is used, the repaired features are left inactive and must be manually activated in each site collection.
    • When using the body toggle option in the custom document section of the Watson Explorer Engine display, the toggle option will not appear in the search results if the body toggle option does not specify any non-annotation, non-zero length content elements. For example, if rating (annotation) and URL (document attribute) were specified as body toggle fields, the body toggle option would not appear in the search results. If a content element (such as snippet) was also specified, the body toggle option would be present in results that have a non-zero length snippet content element. This situation is avoided by always specifying a non-zero length content element as a body toggle field.
    • By default, Log4J logging is set to debug. If performance for that connector is an issue, you can turn off logging in the Watson Explorer Engine administration tool by navigating to the Configuration tab for your search collection seed and adding the following logging settings in the Advanced - Logging section: Note that disabling logging will make it difficult to trace future issues.

       

    • When crawling an SMB file system that is configured with NETBIOS to limit which workstations the crawling account can log on with, the user not allowed to log on to this computer error message can occur if the computer VIV_CRAWLER is not present in the list of allowed workstations.
    • Selecting a graphical refinement for a nested facet causes the search page of the application to return 0 results.
    • If a saved search is deleted from a workspace, it is not entirely removed, which means that it runs according to the monitoring interval that was selected by the user. This issue could consume some processing power. End user documentation about saving searches is located on the following application page, http://localhost:8080/AppBuilder/help/search_page#searching_saving. For information about configuring workspaces, see Global Application Options.
    • When trying to troubleshoot Application Builder applications, enabling Rails DEBUG level logging doesn't produce additional messages.
    • For email notifications settings, you are not able to save a blank form. This issue is a problem if, after enabling email notifications, you want to disable notifications and remove field values. To work around this issue, enter a bogus address and port number, such as smtp.domain.com and 555, and then save the settings. For information about email notifications, see Email Notification Options.
    • For natural language querying, if query expansion is also enabled and the first search term has an expansion, the query incorrectly applies the search operators. For example, if your query is car broken, and car expands the synonym automobile, the query should be (car OR automobile) AND broken. The issue causes the query to be car OR (automobile AND broken). To work around this issue, avoid using query expansion and natural language querying together. For information about natural language querying in Application Builder, see Adding Natural Language Querying to Application Builder.
    • Selecting a graphical refinement for a nested facet causes the search page of the application to return 0 results.
    • iFrame Widget
      • The iFrame widget contains an iFrame, so it has any limitations that an iFrame has for a given browser.
      • In some browsers, when you move an iFrame widget between columns on the home page, the widget might not resize as accurately as other widgets.

  • In previous releases, you added a custom annotator to Annotation Administration Console by expanding the collection on the Collections view, clicking Actions > Text processing options, and then clicking Configure system text analysis engines. In Version 11.0.1, you configure a custom annotator by opening the System view and clicking Configure system text analysis engines on the Parse tab. These steps replace the first two steps in the Adding text analysis engines to the system topic, which still reflects the old procedure.
     

    Watson Explorer Results Module

    Known issues that were applicable in Version 11.0.0.3 are applicable in Version 11.0.1, see Release Notes - IBM Watson Explorer Foundational Components, Version 11.0.

Back to top

IBM Software Support

As problems are discovered and resolved, the IBM Support team updates the IBM Support Portal. Search the IBM Support Portal to find workarounds or solutions to problems.

Back to top

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS8NLW","label":"IBM Watson Explorer"},"ARM Category":[{"code":"a8m0z000000cvvoAAA","label":"Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"11.0.2","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
26 April 2024

UID

swg27048895

Page Feedback