Use the following command line options to start a Director process. On Linux systems, use the & option to launch the Director in the background or insert the appropriate command in your system’s inittab file.
TrilliumDirector -p port
-t filename
-l filename
-cl
-M Address:Port
-b Address
-n name
-d name
-a optionParameters
|
|
Port on which the Director listens for incoming connection requests. If no value is found, the port assigned to the service “TSQ Director” will be used. |
|
|
Trace file name. The full path and name of the file the Director will use to record network trace information. The trace function can be activated or de-activated from the Director System Manager, or by an application through a Director API call. |
|
|
Log file name. Path and name of the file the Director will use to log various startup, informational and error messages. Note: This is only used if the Director is registered as a local
server. Windows messages are sent to the system’s Application
Event Log.
|
|
|
(Windows) Start a Director that has not been registered as a service with Windows. |
|
|
The IP address and port for Multicast messages. See SDK Connector Failover Option section for information on using a multicast address. |
|
|
IP address from which the Director will accept incoming connection requests. The Director will be accessible only from the local host and from the machine at this IP address. (The Director is always accessible from the local host.) Setting -b to 127.0.0.1 will cause the Director to accept requests only from the local host. If -b is not specified, the IP addresses from which the Director will accept requests is not limited. Note: On Windows, this functionality can also be accomplished by
creating a Windows registration key, BoundIPAddr, set to an IP
address.
|
|
|
Internal service name. |
|
|
Service display name. |
|
|
The load balancing option: 0 (zero) for Current Load (the default), or 1 (one)/rr/RR for Round Robin. |