When you upgrade IBM® Legacy
Content Search Engine silently, you run a command in the IBM Legacy
Content Search Engine software package that
references parameters in an installation text file.
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 silently:
- 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.
- To stop the Autonomy K2 Administration Server service and
the Tomcat application server, run the following command.
Option |
Description |
AIX® |
verity_install_path/k2/_rs6k43/bin/k2adminstop |
HP-UX |
verity_install_path/k2/_hpux/bin/k2adminstop |
Linux® |
verity_install_path/k2/_ilnx21/bin/k2adminstop |
Solaris |
verity_install_path/k2/_ssol26/bin/k2adminstop |
- Copy the IBM Legacy
Content Search Engine installation package to the server.
- (Master Administration Server only) Change directory to
the location of the IBM Legacy
Content Search Engine installation package.
- (AIX only) Run the command slibclean as the root user to remove all unused libraries
from shared memory.
- If K2 collections are stored anywhere in the installation
path, move the collections directory and the temp directory to a temporary location outside the installation
path.
- 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.sh "verity_install_path" "temporary_location_path"
verity_install_path is the path to the verity directory in the
current installation path. temporary_location_pathis the location in which you want to temporarily backup your configuration
data, outside of the current installation path, and which is not used
by any other application.
For example,
backup_k2.sh
"/opt/IBM/FileNet/ContentEngine/verity" "/opt/temp"Important: Failure to back up and restore this configuration
data can result in corrupted content search indexes or unexpected
search results.
- Access the IBM Legacy
Content Search Engine installation package.
- Edit cse_silent_install.txt to reflect
the appropriate responses for your installation by using the values
in your worksheet. You must install to the same path as your previous
installation.
- Run the following command:
./5.0.0-P8CSE-UNIX_type.BIN -f cse_silent_install.txt -i silent
- Review the following IBM Legacy
Content Search Engine log files for installation
errors. The files are located in the verity directory
of the installation path.
- verity_install_path/cse_install_log_5.0.0.log
- verity_install_path/vconfig.log
It is a best practice to review log files even if the IBM Legacy
Content Search Engine installation program
does not indicate any errors. Some errors that are noted in the log
files are benign. If an error is not benign (for example, you cannot
subsequently index or search for documents), refer to the log file
for help in determining the cause.
- To stop the Autonomy K2 Administration Server service
and the Tomcat application server, run the following command.
Option |
Description |
AIX |
verity_install_path/k2/_rs6k43/bin/k2adminstop |
HP-UX |
verity_install_path/k2/_hpux/bin/k2adminstop |
Linux |
verity_install_path/k2/_ilnx21/bin/k2adminstop |
Solaris |
verity_install_path/k2/_ssol26/bin/k2adminstop |
- Access the IBM Legacy
Content Search Engine installation package and locate the restore_k2.sh file.
- If you backed up your configuration data as instructed
earlier, restore it from the backup files by running the following
command:
restore_k2.sh "temporary_location_path"
"verity_install_path"
temporary_location_path is the temporary path you entered earlier in this procedure when
you ran the backup_k2.sh file.
verity install path is the path to the verity directory in the Autonomy K2 installation path.
For example, restore_k2.bat "/opt/temp" "verity_install_path"
- Add the following lines to the file verity_install_path/data/stylesets/FileNet_FileSystem_PushAPI/style.ufl:
data-table: fce
{
fixwidth: cemp_partition_date 4 unsigned-integer
}
Important: The purpose of this edit is to
enable use of the IBM Legacy
Content Search Engine partitioning feature, which is new as of version 4.5.1.
- Run the following commands to set the setuid bit for the
vspget program so that the service runs as root.
Important: Most processes for the Autonomy K2 software run as k2_os_user. However, the vspget process must run as root.
For details on required accounts and related permissions, see "Specify IBM FileNet® P8 accounts" in Plan and Prepare Your Environment for IBM FileNet P8.
chown root verity_install_path/k2/_platform/bin/vspget
chmod u+s verity_install_path/k2/_platform/bin/vspget _platform is the following
directory:
Platform |
Directory |
AIX |
_rs6k43 |
HPUX |
_hpux |
Linux |
_ilnx21 |
Solaris |
_ssol26 |
- If you moved collections as instructed earlier in this
procedure, restore your collections directory and temp directory to their original locations.
- For a single-server configuration of IBM Legacy
Content Search Engine, start the K2 services.
For multiserver configurations, do not start the services until Autonomy
K2 servers are upgraded.
To start the Verity K2 Administration
Server service and the Tomcat service, use the follow command.
Option |
Description |
AIX |
nohup verity_install_path/k2/_rs6k43/bin/k2adminstart |
HP-UX |
nohup verity_install_path/k2/_hpux/bin/k2adminstart |
Linux |
nohup verity_install_path/k2/_ilnx21/bin/k2adminstart |
Solaris |
nohup verity_install_path/k2/_ssol26/bin/k2adminstart |
- Access the K2 Dashboard and verify that the services from
your previous installation are restored and running.
- Delete the temporary_location_path directory
of the backup 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 . One index job is created for each selected collection.
- 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.