Installing Director SDK - trillium_discovery - trillium_quality - 17.1

The Trillium Quality Director SDK contains the application programming interface (API) tools required to develop client applications that call the Trillium Quality data cleansing and matching servers. The SDK installs the Java API and a sample Director project, director_proj. You can optionally install:

Cleansing Server: A server that handles data cleansing requests.

Matching Server: A server that handles data matching requests.

To install the SDK Cleansing Server

1. When you install the SDK cleansing server, you are prompted for the following:

   Director Host: Enter the host name or IP address of the node on which the Director is running.

   Director Port: Verify that the port number is the same as the port number on which the Director is listening.

   Cleansing Server Port: Enter the port number on which the cleansing server will listen for requests. Ensure that the same port is not used by multiple services. The default is 17410.

   Cleansing Configuration File: Accept the default path and file name for the sample Trillium configuration file, designed for use with the sample project, or enter a new path and name.

   Processing Level: The Processing Level determines how requests will be queued for handling by the server. The optimum processing level is dependent on your hardware configuration. In general, using one thread for each processor yields optimum performance.

   At all levels, the maximum number of concurrent attaches is 128. The processing level options are:

   1. Minimum - No threads will be spawned for cleansing. Requests will be placed in a queue. The client that has been waiting the longest for a request to be serviced (based on when the server last processed a request for that client) is processed next. Note that the network queue limits the number of attach requests that can be waiting.

   2. Default - One thread will be actively cleansing; another thread will be listening for requests on the network. Other requests will wait until the request is completed. This level is most appropriate for a system with one or two execution cores.

   3. High - Eight threads will be actively cleansing. Other requests will wait until a request is completed. This level is most appropriate for a system with more than four cores.

   4. Maximum - A thread will be created for each incoming request, within the limit of 128 concurrent attaches. This level can increase performance depending on the overall load on the system, for example, if some records require more processing resources.

   A summary of your selections displays.

2. Enter 1 to continue and press Enter. The next prompt displays depends on the components you have selected for installation.

To install the SDK Matching Server

1. When installing the SDK matching server, you are prompted for the following:

   Director Host: Enter the host name or IP address of the node on which the Director is running.

   Director Port: Verify that the port number is the same as the port number on which the Director is listening.

   Matching Server Port: Enter the port number on which the matching server will listen for requests. Ensure that the same port is not used by multiple services. The default is 17412.

   Matcher Configuration File: Accept the default path and file name for the sample Trillium configuration file, designed for use with the sample project, or enter a new path and name.

   Processing Level: The Processing Level determines how requests will be queued for handling by the server. The optimum processing level is dependent on your hardware configuration. In general, using one thread for each processor yields optimum performance.

   At all levels, the maximum number of concurrent attach is 1. The processing level options are:

   1. Minimum - No threads will be spawned for matching. Requests will be placed in a queue. The client that has been waiting the longest for a request to be serviced (based on when the server last processed a request for that client) is processed next. Note that the network queue limits the number of attach requests that can be waiting.

   2. Default - One thread will be actively matching; another thread will be listening for requests on the network. Other requests will wait until the request is completed. This level is most appropriate for a system with one or two execution cores.

   3. High - Eight threads will be actively matching. Other requests will wait until a request is completed. This level is most appropriate for a system with more than four cores.

   4. Maximum - A thread will be created for each incoming request, within the limit of 1 concurrent attach. This level can increase performance depending on the overall load on the system, for example, if some records require more processing resources.

   A summary of your selections displays.

2. Enter 1 to continue and press Enter. The next prompt displays depends on the components you have selected for installation.