Concepts Guide
Man Pages for SRS

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:


SRS 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.

Usage: SRS [options] [configfile]
Available options:
-d, --dump dump the user configuration to stdout and exit
-D, --Debug=PATH:MASK set debug PATH and MASK
-h, --help display this help message and exit
-j, --java print Java properties to the SRS log file (-j -j = print more Java properties)
-v, --validate validate config file and exit
-x, --xsd dump the configuration XSD to stdout and exit
Description
TCP-based resolver services for UM messaging products are provided by SRS.
The 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.
The -d option prints to standard out the full SRS configuration. After printing, the SRS exits.
The -D option sets enables debugging output. This output is intended primarily for Informatica Support, not end-user consumption.
The -h option prints the above usage page. After printing, the SRS exits.
The -x option prints the XSD which is used to validate the configuration file. After printing, the SRS exits.
The -v option causes the SRS to simply validate the configuration file and print any errors it finds. After printing, the SRS exits.
The -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.
Exit Status
The exit status from SRS is 0 for success and some non-zero value for failure.


Srsds Man Page  <-

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.

Note
In the descriptions below, three different log files are referenced: "service log", "process log", and "SRS log". It is important that all three of these be specified, and that they be separate files. In normal use, only the "SRS log" will be written to; the other two are only necessary to record unusual error conditions.
Usage: srsds [options] srs_cfgfile_name
Available options:
-h, --help display this help and exit
-l, --service-log=FILE set a logfile name for the service log.
-p, --process-log=FILE set a logfile name for the srs process output.
-s, --service=request Install, remove or add a configuration file.
Examples: '-s install' to install the service with no config file
'-s install cfgfile.xml' to install the service with a configuration file of cfgfile.xml
'-s remove' to remove the service
'-s config cfg2.xml' to change or add a configuration file
-e, --event-log-level Update/set service logging level. This is the minimum logging
level to send to the Windows event log. Valid values are:
NONE - Send no events
INFO
WARN - default
ERROR
Description
TCP-based resolver services for UM messaging products are provided by SRS.
The srs_cfgfile_name parameter is used interactively to configure the SRS's XML configuration file.
The -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.)
The -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.
Warning
By default, the SRS's configuration file uses <log type="console">. In this case, normal SRS logs are written to standard out and will be captured in the "process" log file. This is not recommended as it leads to unbounded growth of the log file. Users should set <log type="file"> and related attributes to control the log file sizes.
The -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.
The -h option prints the above usage page. After printing, the SRS exits.
Exit Status
The exit status from SRS is 0 for success and some non-zero value for failure.