Release Notes - IBM Watson Explorer Analytical Components, Version 11.0.1
This document describes known issues and workarounds for using the analytical components of IBM Watson Explorer Version 11.0.1.
Release Notes for Version 11.0.1
System requirements in Version 11.0.1
This section summarizes the changes in system requirements since the release of Watson Explorer Version 11.0. For the most current information about all system requirements and supported data sources, including requirements for Content Analytics Studio, see Watson Explorer Version 11.0.1 system requirements.
Watson Explorer Content Analytics Version 11.0.1 extends support to the following system resources:
|Java||IBM Java 8.0 SR3|
|Web browsers||Google Chrome Version 51 and future fix packs|
The following system resources are no longer supported in Watson Explorer Content Analytics Version 11.0.1. Support for later versions of most of these products is provided.
This section describes functions that are new in Version 11.0.1.
Integration with IBM Watson Knowledge Studio
After you train a machine-learning annotator in Watson Knowledge Studio, you can import the model and configure it to be used when analyzing documents in a Watson Explorer content analytics collection. Watson Explorer automatically creates facet definitions from the entity information in the model.
For information about this feature, see Using machine-learning annotators from Watson Knowledge Studio in Watson Explorer. This document includes information about:
- System requirements, including how to install prerequisite software
- Supported languages
- Guidelines for installing, configuring, and using a machine-learning annotator in Watson Explorer Content Analytics and Watson Explorer Annotation Administration Console.
Administrator activity logs
Major actions that administrative users take in the content analytics administration console or through the Admin REST API are now logged. Administrators can inspect these logs in the administration console. For details about this feature, see Inspecting administrator activity logs in Watson Explorer Content Analytics.
Analysis engine administrator role
You can assign a new administrator role to users who are responsible for administering system text analysis engines. This new administrator role allows users to do all of the operations that a collection administrator can do, plus upload text analysis engines to the Content Analytics system and associate the analysis engines with collections. For details, see Assigning an Analysis engine administrator role in Watson Explorer Content Analytics.
Viewing the custom annotator name while using a user application
You can see which custom annotator (text analysis engine) was used to annotate content in a collection by hovering the cursor over the collection name while you use a search application or the content analytics miner. Before, information about the custom annotator was shown only in the administration console. How this feature is implemented depends on how the custom annotator was added to the content analytics system and associated with the collection. For details, see Viewing a custom annotator name from within a search application or content analytics miner.
Setting the boolean operator in facet queries
When you select multiple facet values in the Facets view to refine a query, the values are concatenated by the boolean OR operator, by default. For example, if you select facet value A and facet value B, the query "A OR B" is submitted. Now, a new combo box in the Facets view toolbar lets you choose whether you want to use the boolean AND operator instead of OR. If you select AND in the combo box, and select facet value A and facet value B, the query "A AND B" is submitted.
Configuring WebSphere Application Server ports in the administration console
If you use WebSphere Application Server instead of the embedded web application server, you can now specify the WebSphere Application Server ports in the content analytics administration console. Before, this information had to be specified when Watson Explorer Content Analytics was installed. To configure ports, go to Security -> Application Login Security and SSL Configuration. If not specified, the default ports and protocols are used.
This section describes known issues and workarounds for installing Watson Explorer Analytical Components.
Installing Content Analytics Studio
Beginning with Version 11.0.1, Content Analytics Studio is a Windows 64-bit native application. Windows 32-bit edition is not supported. To install Studio, a 64-bit JRE is required. If you use Windows x64, but the system JVM is 32-bit, the installation program will prepare the installation, but will show the error LaunchAnywhere Error - Could not find a valid Java virtual machine to load.
In this situation, the workaround is to specify a 64-bit JRE using the LAX_VM option:
- Open a command prompt as a Windows administrator.
- Run the Content Analytics Studio installation program from the command prompt, and provide the path to the JVM using the LAX_VM option. For example:
ContentAnalyticsStudio-install.exe LAX_VM "C:\Program Files\IBM\jvm64\jre\bin\java.exe"
For information about upgrading your existing Watson Explorer Content Analytics and Content Analytics Studio system, including information about the supported upgrade paths, see Upgrading the Watson Explorer Analytical Components to Version 11.0.1.
Version 11.0.1 provides fixes for the following problems:
|IT11461||Document is categorized incorrectly.|
|IT14393||Exporter's mapping XML file name is different after being migrated from Watson Content Analytics V3.5.0.|
|IT14607||Exceptions in IBM Cognos BI report wizard occur after migrating from Watson Content Analytics 188.8.131.52 to Watson Explorer Analytical Components 184.108.40.206.|
|IT15079||Web crawler keeps crawling some error web pages.|
|IT14981||New facets are missing values in content analytics miner after a new PEAR file is exported to the server|
|PI63510||The following defects are fixed by IBM Watson Explorer Analytical Components, Version 11.0.1:
Search and analytics:
- Compound document phrase query performance was improved.
- An option was added to the Identity Management Component (IMC) APIs to handle user IDs in a case-insensitive manner.
- Saving disabled flag for my profile is allowed.
Content Analytics Studio:
- Assignment of the incorrect language code for the Slovak dictionary was fixed.
- "Premature end of file" error when importing a collection was fixed.
This section describes known issues and workarounds for administering Watson Explorer Content Analytics. No issues have been reported.
This section describes known issues and workarounds for integrating Watson Explorer Content Analytics with other products. No issues have been reported.
This section describes known issues and workarounds for using the application programming interfaces. No issues have been reported.
This section describes known issues and workarounds for using enterprise search applications and the content analytics miner. No issues have been reported.
IBM Watson Explorer Content Analytics Studio (Content Analytics Studio)
Important: All of the known issues, limitations, and workarounds that were documented for Content Analytics Studio in Version 10 still apply in Version 11.0.1. For details, see Release Notes - IBM Watson Explorer Analytical Components, Version 10.0.
This section describes corrections to the Watson Explorer Content Analytics documentation. Corrections are also embedded as comments to topics in IBM Knowledge Center
Exporting a UIMA pipeline for domain adaptive search
Two issues concern the "Other parameters" section in the Exporting a UIMA pipeline for domain adaptive search topic:
- The reference to DisableStopWord is incorrect. The correct spelling is DisableStopword. This correction also applies when you click F2 on the Domain Adaptive Search window to view help in Content Analytics Studio.
- The following statement is incorrect: "You can also specify whether queries from the same UIMA type are merged to a single query, and whether the UIMA type is enabled only when the original query is a plain text query that does not contain any special characters." Actually, the UIMA type is enabled when the original query is a plain text query without special syntax , which includes query syntax like '|' ("OR"), "IN',"WITHIN","INORDER","ANY", "samegroupas:", and so on, not just special characters like +,-,~,"", and so on.
BoardReader crawler help
Four help files about monitoring the BoardReader crawler and LDAP Entity Resolver were omitted from IBM Knowledge Center. You can read the content of the help files in this technote.
Configuring application user privileges
Disregard the information in the Configuring application user privileges topic. User privileges are configured through application customizers, not the administration console.
Content Analytics Studio
- The Installing Content Analytics Studio topic states: "If you plan to install Content Analytics Studio with Studio Demonstrator, and if there is an existing studioworkspace folder in the Users directory, rename the folder before you install Content Analytics Studio. If the studioworkspace folder is in the Users directory, the installer program automatically renames it to studioworkspace_bak30." For Content Analytics Studio V11.0.1, the installer program automatically renames the studioworkplace folder to studioworkspace_bak1101.
- In V11.0.1, several changes affect the Configuring source control to manage Content Analytics Studio resources topic:
- In the About this task section, the source control repositories were tested with Rational Team Concert 5.0.2, not 4.0.3.
- In Step 3, the web address for obtaining for the Eclipse client used by Content Analytics Studio changed from http://download.eclipse.org/releases/kepler/ to http://download.eclipse.org/releases/luna/.
- In Step 4, the path to the installation package directory changed from file:/C:/Install/RTC/403 to file:/C:/Install/RTC/502 .
Integrating with IBM BigInsights for Apache Hadoop Version 4.0
If you use IBM BigInsights for Apache Hadoop Version 4.0, disregard references to InfoSphere and Jaql in the Integrating with IBM InfoSphere BigInsights topic. In addition, disregard Step 3c in this procedure. There is no need to configure the JobTracker node for BigInsights V4.0, and the fields for specifying JobTracker information are no longer available in the Content Analytics administration console.
References to Apache Hadoop
Throughout the user interfaces, references to IBM InfoSphere BigInsights were changed to Apache Hadoop to reflect the product's support for IBM Open Platform with Apache Hadoop. Be aware that the name was not changed in the product documentation.
Installing an agent server
In the Installing an agent server topic, disregard the first paragraph under Step 4b. There is no need to specify the user name and password when you configure the agent server in the Content Analytics administration console.
Ambiguous references to high availability servers
The documentation uses the term "high availability" to describe servers that are configured to serve as backup servers for disaster recovery and to describe servers that are added to a system to provide scalability and failover support.
In a single-server installation, you can install one high availability server to support disaster recovery on Windows or AIX. In a distributed server installation, you can install two high availability servers to support disaster recovery on Windows or AIX; one server is dedicated to crawling and the other is dedicated to parsing and indexing.
All other servers that you add to a Watson Explorer Content Analytics system are designed to support increased scalability, throughput, and failover support. These additional servers, which are dedicated to search, document processing, or indexing, are not high availability servers for backup or disaster recovery purposes, and they can be installed on any of the supported operating systems.
Important: The documentation in IBM Knowledge Center about configuring support for high availability was originally written for the Windows Server 2008 environment, an environment that has been deprecated. For current procedures, see Configuring high availability in a Windows Server 2012 environment.