To install IBM® Legacy
Content Search Engine interactively,
you run a program wizard.
Note: If you are installing
IBM Legacy
Content Search Engine in a high availability
environment, you must run the
IBM Legacy
Content Search Engine installer
on each node, selecting the shared directory as the
IBM Legacy
Content Search Engine installation path. Verify
that your cluster is running before starting the installation procedure.
To install IBM Legacy
Content Search Engine interactively:
- Verify that you have performed the required preparation
tasks as shown in the Plan and Prepare Your Environment for IBM FileNet® P8 guide.
- 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.
- Log on to the host machine
as k2_os_user.
- Access the IBM Legacy
Content Search Engine installation
package and run the 5.0.0-P8CSE-WIN.EXE file.
- Complete the installation program screens by using the
values in your worksheet.

In a highly
available environment, use the following additional information:
- 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 noted in the log files are
benign. If an error is not benign (that is, you cannot subsequently
index or search for documents), refer to the log file for help in
determining the cause.
If you are installing in a highly available
environment, fail over to another node and repeat the install process
with the same parameters until you have installed IBM Legacy
Content Search Engine on all nodes.
- After the installation
finishes, complete the following substeps:
- Verify that the Verity K2 Administration Web Server
service (Tomcat server) is installed and has started.
- Verify that the Verity K2 6.2.1 Administration Server
service exists.