To upgrade IBM® Legacy
Content Search Engine interactively, you run a program wizard.
If you have an existing IBM Legacy
Content Search Engine installation configured,
you must back up associated configuration data as you begin to upgrade
this component. To do this backup, you use the backup_k2.bat file that is shipped in the IBM Legacy
Content Search Engine installation package. The configuration data includes
the K2 servers that were created and modified in K2 Dashboard and
any custom changes to the FileNet_FileSystem_PushAPI style set. The
configuration data controls how your users' documents that are created
in particular applications are indexed for content search. Files from
this backup are used to restore your existing configuration to complete
the IBM Legacy
Content Search Engine upgrade.
To upgrade IBM Legacy
Content Search Engine interactively:
- Open your completed Installation
and Upgrade Worksheet file.
Tip: In the worksheet
file, verify that the command is enabled. To view only IBM Legacy
Content Search Engine values, filter by CSE Installer in the Installation or Configuration
Program column.
- Access the Autonomy K2
machine and log on as k2_os_user.
- Access Windows® Services and stop the Verity K2 Administration
Web Server service and the Verity K2 Administration Server service.
- Copy the IBM Legacy
Content Search Engine installation package
to the Autonomy K2 machine.
- Open a command window
and access the IBM Legacy
Content Search Engine installation package.
- Back up your configuration
data by accessing the backup_k2.bat file from
the installation package and running the following command:
backup_k2.bat "verity_install_path" "temporary_location_path"
verity_install_path is the path to the verity directory in the current installation path. temporary_location_path is the location in which you want
to temporarily back up your configuration data outside of the current
installation path, and which is not used by any other application.
For example,
backup_k2.bat "C:\Program Files\IBM\FileNet\ContentEngine\verity"
"C:\temp"Important: Failure to back up and
later restore this configuration data can result in corrupted content
search indexes or unexpected search results.
- (Upgrading from version
4.0.1 only) Access the Windows control panel and remove, in reverse order of installation, each
Autonomy-related entry that is listed in the Add or Remove Programs
control panel. Ensure that each program has been removed before you
continue.
Important: The order
in which you remove the programs is crucial. Some of the entries do
not contain any obvious version identification, and you must click
the Change/Remove button and wait for the Autonomy
uninstaller to start in order to identify the version number. Then
uninstall the entries by starting with the one with the highest version
number. This step removes only the added Service Pack and fix pack
updates and does not remove the base IBM Legacy
Content Search Engine software.
- (Upgrading from version
4.0.1 only) Complete the manual program removal procedure for IBM Legacy
Content Search Engine 4.0.1 by removing the
K2 Dashboard service:
- From a command window, access the following directory: C:\Progam Files\Filenet\ContentEngine\verity\appserver\bin.
- Enter the following command: service remove
k2.
- If collections are stored
anywhere in the installation path, move the collections directory and the temp directory to a temporary
location outside of the installation path.
- Access the IBM Legacy
Content Search Engine installation package.
- Run the 5.0.0-P8CSE-WIN.EXE file.
- Complete the IBM Legacy
Content Search Engine installation program screens by using the values from
your worksheet.
- Review the following IBM Legacy
Content Search Engine log files for upgrade
errors.
verity_install_path\cse_install_log_5.0.0.log
verity_install_path\vconfig.log
Refer
to the log file for help in determining the cause for serious errors,
for example, if after the upgrade you are unable to index or search
for documents.
Important: After an upgrade from version
4.5.0, you might see a file-size mismatch error in the cse500_1.mf.log file regarding the data\docs\support\docList.js file. You can ignore this benign error.
- Access Windows Services and stop the Verity K2 Administration
Web Server service and the Verity K2 Administration Server service.
- Open a command window
and access the IBM Legacy
Content Search Engine installation package directory where the restore_k2.bat file is located.
- If you backed up your
configuration data as instructed earlier, restore it from the backup
files by running the following command:
restore_k2.bat "temporary_location_path" "verity_install_path"
temporary_location-path is
the temporary path you entered earlier in this procedure when you
ran backup_k2.bat. verity_install_path is the path to the verity directory in the
Autonomy K2 installation path.
For example, restore_k2.bat
"C:\temp" "C:\Program Files\IBM\FileNet\ContentEngine\verity"
- Add the following
lines to the file verity_install_path\data\stylesets\FileNet_FileSystem_PushAPI\style.ufl to
enable the IBM Legacy
Content Search Engine partitioning
feature, which is new as of version 4.5.1.
data-table: fce
{
fixwidth: cemp_partition_date 4 unsigned-integer
}
- If you moved
collections as instructed earlier in this procedure, restore your collections directory and temp directory
to their original locations.
- For a single-machine
configuration of IBM Legacy
Content Search Engine, access Windows Services
and start the Verity K2 Administration Web Server service and the
Verity K2 Administration Server service. For multiserver configurations,
do not start the services until all Autonomy K2 servers are upgraded.
- Access the K2 Dashboard
and verify that the services from your previous installation are restored
and running.
- For Master Administration
Servers, delete the temporary_location_path directory
of the backup that you ran earlier.
- If you are upgrading
from version 4.5.0 or earlier, you can skip the remaining steps.
- If the K2 domain that
you are upgrading was new in IBM Legacy
Content Search Engine 4.5.1 (not upgraded from a previous version), you have
incorrect style files that must be fixed:
- Open the IBM Legacy
Content Search Engine installation package and copy the files from the FileNet_FileSystem_PushAPI.zip file.
- Navigate to verity_install_path\data\stylesets\FileNet_FileSystem_PushAPI.
- Replace the installed FileNet_FileSystem_PushAPI files with the files that you copied from the installation package.
- Compare all the FileNet_FileSystem_PushAPI files with the file in the style directory of each collection.
- Apply the same changes to the verity_install_path\data\stylesets\FileNet_FileSystem_PushAPI\style.ufl file
that you made in step 17.
- Update the default style files in the FileNet_FileSystem_PushAPI folder to include any style file customizations that were made in
the existing collections.
- If the style sets in
all of the collections in the new K2 domain differ from the correct
files, reindex from the CBR base class with subclasses:
- Right-click the newly enabled CBR-enabled class.
- Click
- If the style sets in
only some of the collections in the new K2 domain differ from the
correct files, reindex only those incorrect collections to apply the
correct style set.
- Right-click on the index area that contains the collections.
- Select Properties.
- Select the tab.
- Select the collections you want to reindex.
- Click Index for Content Search to reindex. One index job is created for each selected collection.