Figure 1 shows how Text Extender is integrated into the DB2 client/server environment.
Figure 1. Integration of Text Extender into the DB2 client/server environment
![]() |
For a list of the DB2 Communications Support protocols (such as TCP/IP or NETBIOS) for a client , see the DB2 Quick Beginnings Guide for the appropriate platform.
The main part of Text Extender is installed on the same machine as the DB2 server. Only one Text Extender server instance can be installed with one DB2 server instance.
A Text Extender installation is flexible and can comprise:
Figure 2 shows a typical Text Extender configuration. To run Text Extender from a client, you must first install a DB2 client and some Text Extender utilities. These utilities constitute the Text Extender "client" although it is not a client in the strict sense of the word. The client communicates with the server via the DB2 client connection.
Figure 2. A Text Extender configuration
![]() |
Text Extender has the following main components:
Tip |
---|
The Text Extender client utilities offer the two main functions: administration and the API. (The UDFs are available on the server.) To use the Text Extender administration functions or the API on the client, you must install the Text Extender client. If you do Text Extender administration only at the Text Extender server, then you need to install the Text Extender client utilities only on clients that use the API functions. If you need only the search capability on the client using DB2 UDB SQL statements, you do not need to install the Text Extender client. All communication is handled by DB2 UDB and the Text Extender search engine runs only on the server. |