Concepts Guide
|
Help for the Stateful Resolution Service (SRS) command line can be obtained by entering "SRS -h". Brief help for the SRS configuration file can be obtained by entering "SRS -x", which prints the XSD contents.
For more information on TCP-based TR, see TCP-Based Topic Resolution Details. For more information on Topic Resolution general, see Topic Resolution Description.
There are two executables for the SRS, each with it's own man page:
The SRS executable can be run interactively from a command prompt or from a script/batch file. For use as a Windows Service, see Srsds Man Page.
configfile
parameter is optional; if omitted, the SRS defaults all configurable options. If supplied, the file must be in XML format, and is validated against the XSD file shown below. See SRS Configuration File for configuration details. -d
option prints to standard out the full SRS configuration. After printing, the SRS exits. -D
option sets enables debugging output. This output is intended primarily for Informatica Support, not end-user consumption. -h
option prints the above usage page. After printing, the SRS exits. -x
option prints the XSD which is used to validate the configuration file. After printing, the SRS exits. -v
option causes the SRS to simply validate the configuration file and print any errors it finds. After printing, the SRS exits. -j
option prints Java properties to the SRS log file. It can be repeated ('-j -j') to increase the output. This output is intended primarily for Informatica Support, not end-user consumption.
The srsds executable is for use as a Windows Service. The service can be installed as a service by the Windows package installer.
Alternatively, the srsds executable can be run interactively from a command prompt to install the service or to change certain configuration elements. See UM Daemons as Windows Services for more details.
srs_cfgfile_name
parameter is used interactively to configure the SRS's XML configuration file.-l
option is used interactively to configure a "service" log file to be used by the SRS. Under normal circumstances, this log file will never be written to. It will be written if the SRS is unsuccessful in starting up as a service. (The normal SRS log file is configured differently, using the <log> element in the configuration file.)-p
option is used interactively to configure a "process" log file to be used by the SRS. Under normal circumstances, this log file will never be written to. It will be written if the Java JVM writes to standard out or standard error, of if the SRS is not able to write to its configured log file.-s
is used interactively to control the installation of the Windows service. The -e
is used interactively to configure the logging threshold for writing to the Windows Event Log. See UM Daemons as Windows Services for more details.-h
option prints the above usage page. After printing, the SRS exits.