DB2 10.5 for Linux, UNIX, and Windows

Configuring DB2 Text Search

Your options for configuring DB2® Text Search depend on whether you are performing the initial configuration or a reconfiguration and which platform you are using.

Before you begin

Before reconfiguration of the DB2 Text Search, stop the text search instance service, as outlined in Stopping the DB2 Text Search instance service.

For partitioned instances you need to be on the coordinating member or instance owning partition when using the configuration tool. This is the instance host where the integrated text search server is initially configured and is the lowest numbered partition server host.

Procedure

Determine whether DB2 Text Search is configured.
Run the configuration tool by issuing the following command:
```
	configTool printAll -configPath absolute-path-to-configuration-folder
```
In the output of the printAll option, the authentication token is an empty string if DB2 Text Search is not configured.
Configure DB2 Text Search for the first time.
On Linux and UNIX operating systems, use one of the following methods to configure DB2 Text Search:
- Rerun the silent installation as described in Installing and configuring DB2 Text Search with a response file.
- Rerun the GUI installation as described in Installing and configuring DB2 Text Search with the DB2 Setup Wizard .
- Use the configuration tool. Refer to Initial configuration of an integrated DB2 Text Search server. Note that using the configuration tool to perform a manual configuration requires you to manually configure most of the parameters, whereas using the installer requires you to configure only two parameters.
- Use one of the following commands to configure DB2 Text Search, depending on the instance type and operation:
  - For root installs, you can issue db2isetup command in the GUI to configure existing DB2 instance by selecting DB2 Text Search when it is being configured. You also can issue the db2iupdt command with -j option to configure integrated DB2 Text Search server. Note that when you create an instance using the db2icrt command with -j option, DB2 Text Search is also configured by default.
  - For non-root installs, issue the db2isetup command to configure the instance in the GUI, or issue the db2nrupdt or db2nrupgrade command with the -j option.
On Windows operating systems, use one of the following methods to configure DB2 Text Search:
- Rerun the silent installation as described in Installing and configuring DB2 Text Search with a response file.
- Rerun the GUI installation as described in Installing and configuring DB2 Text Search with the DB2 Setup Wizard.
- Issue the db2iupdt command with the -j option. Note that when you create an instance using db2icrt command with the -j option, DB2 Text Search is also configured by default.
Determine whether the Java™ developer kit is from IBM.
The DB2 Text Search internally uses a Java developer kit whose location is pointed by JDK_PATH of db2 get dbm cfg command and this Java developer kit has to come from IBM. To verify if the Java developer kit is from IBM, run the following command:
```
JDK_PATH/jre/bin/java -version
```
This command will display the Java version information and IBM should display as part of string if the Java developer kit is from IBM.
Re-configure DB2 Text Search.
After you have configured DB2 Text Search, you cannot use the GUI installer to re-configure it. You must make any updates to the configuration manually.
On Linux and UNIX operating systems, use one of the following methods to re-configure DB2 Text Search:
- Rerun the silent installation as described in Installing and configuring DB2 Text Search with a response file.
- Use the Configuration Tool. Refer to Initial configuration of an integrated DB2 Text Search server.
- Use one of the following commands to re-configure DB2 Text Search, depending on the instance type and operation:
  - For root installs, you can issue db2isetup command in the GUI to configure an existing DB2 instance by selecting the DB2 Text Search instance being configured. You also can issue the db2iupdt command with -j option to configure integrated DB2 Text Search server.
  - For non-root installs, issue the db2isetup command to configure the instance in the GUI, or issue the db2nrupdt or db2nrupgrade command with the -j option.
On Windows operating systems, use one of the following methods to re-configure DB2 Text Search:
- Rerun the silent installation as described in Installing and configuring DB2 Text Search with a response file.
- Use the Configuration Tool. Refer to Initial configuration of an integrated DB2 Text Search server.
- Run the db2iupdt, or db2iupgrade command, specifying the -j option as shown to meet your needs:
  - -j "TEXT_SEARCH" attempts to configure DB2 Text Search with the default service name and a generated port value.
  - -j "TEXT_SEARCH,[servicename]" reserves the service name with an automatically generated port number or with the same port number assigned to that service name if the service name is already reserved in the services file.
  - -j "TEXT_SEARCH,[port number]" reserves the port with the default service name.
  - -j "TEXT_SEARCH,[servicename],[port#]" reserves the specified service name and port number.
Note: On Windows operating systems, the PATH in the DB2 command window points to current-default-copy-install-path\db2tss\bin, so to configure an instance that is not in the current DB2 copy, first switch to the appropriate DB2 command window for that copy.