You create one or more cleanser and matcher servers for each real-time project you will be running. Each server is uniquely configured for a specific project.
To create a cleanser, or matcher server
On the Realtime View tab, right-click a Director and select Create a Cleanser Service or Create a Matcher Service. The Create form opens, similar to the form shown in the figure below.
Figure 1. Create Cleanser Form
Server Host: Select the host on which this server will run. Only hosts that have been identified through the Setup process, described in Setting Up Hosts, are listed.
Passphrase: For Linux hosts, enter the passphrase for this host.
System: Enter a one-byte system identifier. This can be any alphanumeric character that will help you identify the system and application with which this server is associated. For example, you can use a common identifier to identify servers that are dedicated to a particular project or task.
Server: Enter a server identifier of one to eight characters. This is the name that will be displayed in the Director System Manager. On Windows systems this is used as the Server ID in the Registry. Cleanser names must begin with a C or c; matcher names must begin with an R, r, M, or m.
Service Name: Enter a service name. On Windows systems, this is the service name listed in the Registry.
Service Display: Enter a service display name. On Windows systems, this is the name displayed in the Windows Services list. On Linux systems, this is a specific comment ID generated within the script.
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 and operating system. 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 or 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 cleansing or 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 cleansing or matching. Other requests will wait until a request is completed. This level is most appropriate for a system with more than four cores, assuming that records are spread among different countries.
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.
Config File: Enter or browse to the connector configuration file created with the Project Deployment Manager, as described in Creating Real-Time Projects (for example, Trillium.cfg or TrilSAP.cfg). Within the real-time project’s directory, the file will be located in the Settings directory.
Trace File: Enter or browse to select a location for the server’s trace file, or accept the default. If you do not enter a trace file name, a trace file cannot be created. Refer to Using Trace Files for more information about trace files.
Log File: For Linux systems, enter or browse to select a location for the server’s log file. To create a new file, browse to the directory, click New File and enter a file name. This option is inactive for Windows systems; use the Windows Event Viewer to view messages.
The server’s listen port is assigned dynamically, allowing use of any available port. If you need to specify a specific port due to firewall requirements:
Click Advanced.
Enable the Need to specify a specific port due to a firewall option.
Enter the port number. Ensure that the same port is not used by multiple services.
Click OK.
Click Create. Click Refresh to update the Director System Manager list. The service is started automatically.