After you upgrade Content Engine data,
you must create new content-search index areas in Enterprise Manager. Then you can enable indexing
for designated classes and properties and reindex your stored data.
The reindexing process creates new Autonomy K2 collections.
Be sure that you have available
the Installation and Upgrade Worksheet that was completed during your
planning activities.
This procedure covers the minimum setup and configuration
steps to get content-based retrieval (CBR) configured and running
with Autonomy K2 for an upgrade from 3.5.2. For more detail on content-based
retrieval and Content Engine,
see the IBM® FileNet® P8 help topic .
Important: Where machine
name variables are required, IP addresses will not validate. In these
cases, you must enter the host name for the machine.
To complete the IBM Legacy
Content Search Engine upgrade
from version 3.5.2:
- Start Enterprise Manager and
log on as the Global Configuration Data (GCD)
Administrator.
- Create a Verity Domain Configuration (VDC).
- Open your completed Installation and Upgrade Worksheet
file.
Tip: In the worksheet file, verify that
the command is enabled.
To view only Enterprise Manager values
for this task, filter by EM: Verity Domain Configuration
Tab in the Installation or Configuration Program column.
- Right-click Enterprise Manager [domain] in
the Enterprise Manager tree and select Properties.
- Click the Verity Domain Configuration tab.
- Enter the following K2 Master Administration Server
access information:
- Host Name - the name of the host of the K2 Master Administration
Server.
- Port - the K2 Master Administration Server port. The default
port number is 9950.
- User Domain - the authentication domain in which your K2 services
are installed.
- User Group - K2 Security Group.
- Verity Username - K2 Security User.
- Password - the K2 Security User password.
- Click Create Configuration to
create a Verity Domain Configuration object.
- Assign a K2 Broker Server:
- Click the Verity Server tab.
- From the Brokers AVAILABLE pane, select the broker
and click Add to move the server to the Brokers
Selected pane.
- Click OK.
Important: You can assign multiple Broker Servers to a K2 Administration
Server, primarily for failover. If one Broker Server goes down, then
K2 can switch to another. In this configuration, you must ensure that
all Search Servers required to access K2 Collections (index areas)
are attached to each Broker Server. A given Content Engine server does not call multiple
Broker Servers or merge associated search results. See the appropriate
steps of the Configuring IBM Legacy
Content Search Engine task
for instructions on how to create Broker Servers and assign Search
Servers.
- To access the Verity Locale Configuration Guide, complete
the following substeps.
Important: For information
about how the K2 product uses locales and about performance and indexing
options, review the Verity Locale Configuration Guide in the Autonomy-supplied
documentation set.
- Open the Autonomy K2 Dashboard and click Help.
- Click Library (top right of the
screen) to access the Autonomy K2 product guides. Each guide is available
in HTML or PDF format.
- To assign a CBR locale to the object
store for which you want to enable indexing, complete the following
substeps:
- Right-click the object store in the left pane of Enterprise
Manager and choose Properties from the context
menu.
- In the Properties dialog box, click the CBR tab.
- Specify one of the following locales (which are installed
by default with Autonomy K2 IBM Legacy
Content Search Engine software)
in the CBR Locale box:
- uni (multi-language and slower indexing)
- englishv (enhanced word-stemming and faster indexing)
- english (limited capabilities and fast indexing)
If you click Set to Default CBR Locale,
the CBR locale is set to uni.
- Click Apply or OK.
- Create an index area for version 5.0 IBM Legacy
Content Search Engine collections:
- Open your completed Installation and Upgrade Worksheet
file.
Tip: In the worksheet file, verify
that the command is enabled.
To view only Enterprise Manager values
for this task, filter by EM: Create an Index Area in
the Installation or Configuration Program column.
- In the Enterprise Manager tree
view, expand the Object Stores container.
- Right-click the object store to which you want to add
an index area and select .
- Complete the Create an Index Area wizard by using the
values from your worksheet.
Important: In
the wizard, make sure you set the template type to P8_CSE50.
For more information about creating indexes, see the IBM FileNet P8 help topic .
- Re-enable content-based retrieval for class definitions
by activating the CBR Enabled flag for each class:
- Right-click class_name for
the class that you want to configure in the Enterprise Manager tree and click Properties.
- Select the CBR Enabled check
box, and click OK.
- Click Yes to confirm.
- For each class property for which you want to enable content-based
retrieval, complete the following substeps. The properties
you enable must include those that you indexed for content-based retrieval
in version 3.5.2 of Content Engine.
Refer to the list of properties that you generated by SQL query command
on each object store during the pre-upgrade phase of upgrading Content Engine.
- Right-click the base class or subclass that contains
the property or properties that you want to reindex and click Properties from
the context menu.
- Click the Property Definitions tab.
- Click the string property you want to enable for indexing
and then click Edit.
- Select the CBR Enabled check box, and then click OK.
- Reindex each class on which you enabled indexing in the
preceding two steps by right-clicking the class and choosing one of
the following:
For details, see the IBM FileNet P8 help
topic .
- To monitor the reindexing progress, complete the following
substeps:
- Select and right-click the object store node that contains
the index areas that are being reindexed.
- Choose .
- Click Refresh to monitor the
progress. Click Close when reindexing
is complete, as indicated by the job status <TERMINATED NORMALLY>.
- Because the version 3.5.2 IBM Legacy
Content Search Engine collections (indexes)
are no longer used, you can save hard drive space by deleting the
index directories and all subdirectories. For example, D:\CE_storage\FS_object_store_name\index.