IBM Support

Problems and solutions in IBM OmniFind Enterprise Edition Version 9.1

Release Notes


Abstract

This document describes known issues and workarounds for IBM OmniFind Enterprise Edition Version 9.1, including any Version 9.1 fix packs.

Content

The information is organized according to information type.

Requirements
Deprecated content
Installation
Administration
Search applications
Application development
Documentation updates
Version 9.1 Fix Packs

Requirements

This section describes known issues and workarounds for system requirements and supported data sources. For the most current information about requirements, see System requirements and Supported data sources.

Linux on System z


If you install the product on Linux on System z:
  • These crawlers are supported: Web, Windows file system, UNIX file system, and JDBC database.
  • You can use the JDBC database crawler to collect data from DB2 databases only.
  • The ability to generate thumbnail images of crawled documents is not supported.

Portal Document Manager
IBM Content Integrator no longer extends support to Portal Document Manager content. Disregard references to Portal Document Manager in the OmniFind Enterprise Edition user interfaces and product documentation.

Web application server
The embedded Jetty web application server is required for certain functions, even if you use WebSphere Application Server. For example, the Jetty server is used for administration, monitoring, and the search functions for both search collections and classic search collections. (ESAdmin, ESSearchServer, and the customization applications run on the embedded application server.) You can use WebSphere Application Server to support classic search collections, but the functions that became available for search collections in V9.1 require the embedded Jetty web application server.

WebSphere Portal Version 7.0


The product documentation includes several references to support for WebSphere Portal 7.0, such as the ability to integrate with OmniFind Enterprise Edition.

If you use OmniFind Enterprise Edition 9.1: Disregard those references. Version 7.0 is not a supported version of WebSphere Portal in the base version of OmniFind Enterprise Edition V9.1. For current information, see Supported data sources.

If you use OmniFind Enterprise Edition 9.1 Fix Pack 1 or a later fix pack: Support is extended to WebSphere Portal 7.0 and Lotus Quickr 8.5. For details, see Documentation updates for Version 9.1.

Back to top

Deprecation

This section describes functions in older releases of OmniFind Enterprise Edition that are being deprecated in Version 9.1.

Non-Lucene index architecture


The framework for indexing content in classic search collections will not be supported in future releases. When you create new collections in OmniFind Enterprise Edition Version 9.1, create search collections, not classic search collections. In addition, you should migrate your classic search collections to the search collection framework. For details, see Migrating your collections.

SIAPI Administration APIs and Web Services APIs
The SIAPI Administration APIs and Web Services APIs are being deprecated and will not be supported in future releases. To develop custom administration applications, use the REST Administration and Search APIs, which are included in OmniFind Enterprise Edition Version 9.1. Information about using the REST APIs is available in the ES_INSTALL_ROOT/docs/api/rest directory. Sample scenarios for performing administration tasks are available in the ES_INSTALL_ROOT/samples/rest directory.

This announcement pertains only to the administration APIs and web services. The SIAPI Search APIs continue to be supported.

Back to top

Installation

This section describes known issues and workarounds for installing the product.

Non-root user installation

  • When you install the product as a non-root user, you do not need to restart the computer after the installation program is completed. The First Steps program automatically starts after the installation program ends.
  • If you install the product as a non-root user on AIX or Linux, the OmniFind Enterprise Edition administrative user ID and password cannot be validated if the targetpw option is set for the sudo command. In this case, you must skip user validation by specifying the following option when you run the installation program:
    ./install.bin -D\$IGNORE_UID_PASSWORD\$=true

DBCS characters
DBCS characters cannot be used for the OmniFind Enterprise Edition administrative user ID or the installation directory paths. Only ASCII characters are supported.

IPv6 addresses
When you install the product or add a server, IPv6 raw address cannot be used as the host name of the server.

Administrative user privileges
The OmniFind Enterprise Edition administrative user ID must have read and execute permissions to the parent directories of the installation and data directories. For example, if the installation directory (ES_INSTALL_ROOT) is the /opt/IBM/es directory, then the OmniFind Enterprise Edition administrative user must have read and execute permissions to the /opt and /opt/IBM directories.

Installing on Solaris
If the default user home directory is not the /export/home directory, you must specify the user home directory with a startup argument when you run the installation program. In the following example, replace user home directory with the correct directory, such as /home/esadmin:
    ./install.bin -D\$FORCE_USER_HOME_FOR_UNIX\$=true -D\$USER_HOME_DIR\$=user home directory

Verifying the installation
You can verify installation with the First Steps application.

  • Windows:

  • The First Steps application is started automatically after you restart the operating system. When the system restarts, you must log in to the system as the OmniFind Enterprise Edition administrative user that you specified when you installed the product.
  • Linux and AIX:

  • For the First Steps application to start automatically after the installation program is completed, you must first export the DISPLAY variable. For example, enter these commands:
    DISPLAY=display configuration
    export DISPLAY
    ./launchpad.sh
  • Solaris:

  • The First Steps application is not started automatically. You must start the application manually after the installation program is completed. For instructions, see Installation - Starting the First Steps program. When you click Verify Install, the First Steps application might return error FFQO0262E, Session testing is not created yet. You can ignore this error message.

Using the console mode to uninstall on AIX
When you use the console mode to uninstall the product from an AIX system, the following folder remains. You must manually delete this folder:
    $ES_INSTALL_ROOT/_jvm/jre/javaws/javaws

Back to top

Administration

This section describes known issues and workarounds for administering the product.

Scheduling duplicate document detection


The ability to schedule duplicate document detection is not supported. Disregard references to scheduling duplicate document detection in the product documentation.

Troubleshooting disk full conditions
If a disk full condition occurs, the issue is logged in the indexservice audit log files (such as col_58876.indexservice_audit_20100514.log) but not in the collection log file. To monitor and receive notifications about pending disk full conditions, you can configure system alerts. For details, see Configuring system-level alerts.

Date range facet configuration
When you define a date range facet by specifying absolute dates, the time zone of the client browser in which the administration console is opened is used. Ensure that the client browser is set to the time zone that you want to use for date range facets before you configure the facets.

Backing up collection data from custom locations
The esbackup program does not create a backup image of collection data if the data is in a custom location. You must manually create a copy of the directory where the data is located.

JVM issues on Solaris
If the search service stops responding when a very high query load occurs continuously, the problem might be caused by frequent garbage collection (GC). In this case, you might try applying GC-related JVM options to the search session. For example, add the following line to the $ES_INSTALL_ROOT/configurations/interfaces/indexservice_searcher_interface.ini file:
    JVMOptions=-XX\:SoftRefLRUPolicyMSPerMB\=100000 -XX\:+UseConcMarkSweepGC

Back to top

Application development

This section describes known issues and workarounds for using the product application programming interface.

Custom crawler plug-ins


If a crawler gets NullPointerException when a custom crawler plug-in is configured, override com.ibm.es.crawler.plugin.AbstractCrawlerPlugin#isMetadataUsed() to return TRUE.

Multiple sort keys
Specify multiple sort keys through SIAPI method Query#setSortKeys(SortKey[] sortKeys). A SortKey instance can be obtained by using the SearchFactory#createSortKey() method.

Back to top

Search applications

This section describes known issues and workarounds for using the search applications that are provided with the product.

Search application: Thumbnail enlargement


If you open the search application in the Internet Explorer 7 browser, or the Internet Explorer 7-compatibility mode of Internet Explorer 8, thumbnail images will not be enlarged when you click them in the search results.

Search application: Scope selection
When you open the Preference dialog of the search application, the ability to select a scope is unavailable.

Search application: Query operators must use uppercase characters
Query operators such as AND, OR, NOT, and WITHIN must be specified in uppercase characters. For example, if you want to find documents about dogs or cats by specifying the OR Boolean operator, you must specify the query as (dogs OR cats), not (dogs or cats). The query (dogs or cats) searches for documents that contain all three words: dogs, or, and cats.

Classic search application: Searching specific types of sources
To search specific types of data sources, you must enter query syntax to specify the source type. For example: $source::unixfs

Back to top

Documentation updates

For information about changes and corrections to the OmniFind Enterprise Edition Version 9.1 information center, see Documentation updates for Version 9.1.


Back to top

Version 9.1 Fix Packs

If you install Version 9.1 Fix Pack 1 or later, and run the administration console in a Firefox browser, an error might be displayed if you attempt to move to a different page when collections are in a busy state. For example, if you click the Monitor icon for a collection while the status of collections in the Collections view is busy, a message states that an error occurred while processing the collection response and that you need to ensure that the search server is still available.



You can disregard this message. The interface successfully advances to the requested page.

Back to top

[{"Product":{"code":"SS5SQ7","label":"OmniFind Enterprise Edition"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 June 2018

UID

swg27018048