The Autonomy K2 software must be installed on each machine
that is part of your IBM® Legacy
Content Search Engine configuration.
You must designate one machine in the configuration as the Master
Administration Server.
The Master Administration Server can be used as a stand-alone IBM Legacy
Content Search Engine, or additional K2 Administration
Servers can be added. All K2 Administration servers are configured
and controlled through the K2 Dashboard of the Master Administration
server.
The Autonomy K2 software that underlies IBM FileNet® P8 IBM Legacy
Content Search Engine has many inherent features
that you might want to configure that are not discussed in the IBM
FileNet documentation. For details, see the Autonomy documentation
that is installed with the Autonomy K2 Master Administration Server
located at: http://Master Administration Server hostname:9990/verity_docs/
The Autonomy documentation set is not searchable from the IBM FileNet P8 Help but it does have its
own internal index and search functionality.
Important: Although the K2 Dashboard provides you with
documentation for, and direct interfaces to, the K2 collections, IBM
FileNet requires that you use Enterprise Manager to
manage collections associated with IBM Legacy
Content Search Engine index areas (for example,
to add and remove index areas).
- Autonomy K2 was previously known as Verity, and you will see Verity
still used in many of the interfaces described in the following procedures.
- If your Content Engine runs
on Windows, then the machines in your IBM Legacy
Content Search Engine configuration must run
on Windows. If your Content Engine runs
on UNIX, then the machines in your IBM Legacy
Content Search Engine configuration must run
on UNIX, but it to doesn't have to be the same UNIX type.
- Where machine name variables are required, IP addresses will not
validate. A valid name must be entered.
- If you unimport the style set, the original files will be deleted
from your system. In this scenario, if you wish to re-import the style
set, recover it from your installation package. In order to avoid
this situation, you can either enter a unique name for the Style Set
Alias during the initial IBM Legacy
Content Search Engine (Autonomy
K2) installation, or make a backup copy of the original style set.
If you enter a unique name for the style set during installation,
ensure you use that name when you configure Content Engine for Content-Based Retrieval.
- Stop word files can be used to increase performance by about 30%.
You can place the style.stp file into the stylefiles directory
to list words you do not want full-text indexed, for example, short
words such as a, the, or and. However, any word in the stop word file
cannot be searched. See the K2 documentation for more details. To
create a stop word file you can typically copy the vdk30.stp file
from either the main K2 install directory or the foreign language
locales package over to the main stylefile directory,
and then rename the file style.stp. You must
do this copy operation before you create collections.
Because indexing
is case sensitive, the style.stp file should
include lower-case and upper-case versions of words in the stop word
list. For example, use "the", "The" and "THE" if you think that all
of these might be encountered in a search.