To create and control Director, cleanser, and matcher servers, you must first identify
Director host machines. On subsequent startups, the Director System Manager reads the
host list, stored in the hostandport.ini
file in:
C:\Users\user\AppData\Roaming\Data Quality\17\deployment
It searches the network to locate those hosts, and populates the Director System Manager main window with current information on server activity.
To start or modify Directors or servers, you must have the necessary privileges on the appropriate hosts. For Windows hosts, security is controlled by your Windows system administrator and your access rights for running, creating and modifying services. For Linux hosts, you must have either a home directory or a Trillium user account on the host system.
Linux systems must have SSH (Secure Shell) installed. The Director System Manager uses SSH security technology to provide a secure connection to run and modify the privileged Director services.
To identify hosts
Once hosts are configured, the Director System Manager displays statistics about the Director, cleanser, and matcher servers running on those host/port combinations. If a Director has not yet been created on this host/port combination, the Director System Manager displays a warning icon indicating that the Director was not found.
Note that the connection between hosts and the Director System Manager is subject to network related issues such as pauses and delays, unresponsive remote services, network traffic, power loss, or manual termination of a dependent process. If there is a network issue for a specific host and port, a warning icon displays next to the node in the left pane of the Director System Manager. Right click the warning icon to view the associated error.
TCPTimedWaitDelay REG_DWORD 30 seconds
MaxUserPort REG_DWORD 65534