The Director SDK contains the application programming interface (API) tools used to develop client applications that call the Trillium Quality data cleansing and matching services. The Java API, samples illustrating API calls and a sample project, director_proj are installed. Optionally, you can install:
Cleansing Service: A service that handles data cleansing requests. The default service name is TSQCleanser17.
Matching Service: A service that handles data matching requests. The default service name is TSQMatcher17.
Installing the SDK Cleansing Service
When installing the Cleansing Service, the TS Quality Cleansing Service for SDK window opens.
To install the SDK Cleansing Service
-
Set the following parameters:
Server Port: Enter the port number on which the Cleansing Service will listen for requests. Ensure that the same port is not used by multiple services. The default is 17410.
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. This port was established when the Director was installed. The default is 17400.
Configuration File: Accept the default path and file name for the sample Trillium configuration file 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:
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.
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.
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.
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.
-
If you want the Cleansing Service to start automatically when Windows starts, verify that Start services automatically? is selected. This check box is selected by default.
-
Click Next. The next window displayed depends on the components you have selected for installation.
Installing the SDK Matching Service
When you install the SDK matching service, the Matching Service for SDK window opens.
To install the SDK Matching Service
-
Set the following parameters:
Server Port: Enter the port number on which the matching service will listen for requests. Ensure that the same port is not used by multiple services. The default is 17412.
Director Host: Enter the host name or IP address of the node on which the Director for TS Quality is running.
Director Port: Verify that the port number is the same as the port number on which the Director is listening. This port was established when the Director was installed. The default is 17400.
Configuration File: Accept the default path and file name for the sample Trillium configuration file 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 1. The processing level options are:
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.
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.
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.
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.
-
If you want the matching service to start automatically when Windows starts, verify that Start services automatically? is selected. This check box is selected by default.
-
Click Next. The next window displayed depends on the components you have selected for installation.