Configuration: Global

config-file

Short option: –f
Type: String
Default: dumpconf.conf

Main config file

application-root

Short option: –r
Type: String
Default: None

Application Root

application-name

Short option: –n
Type: String
Default: dumpconf

Application Name

runtime-user

Type: String
Default: None

The user to run as

event-log

Type: String
Default: event-%a.log

Event Log filename

preprocessor-binary

Type: String
Default: None

This option should refer to the full path to a binary or script that can preprocess configuration files prior to them being parsed by the datasource libraries.

Depending upon your choice of preprocessor, this allows variables to be substituted, extended logical conditions to be validated and generally reducing the configuration management requirements.

The preprocessor should take as its first argument the name of the file to process, and output a rewritten configuration file to standard out.

This feature has been extensively tested using the GNU M4 macro processor.

http-download-command

Type: String
Default: wget -nv -O -

HTTP config file download command

quiet-config

Short option: –q
Type: Boolean
Default: FALSE

This is now the default

verbose-config

Short option: –v
Type: Boolean
Default: FALSE

Report all messages for config files being loaded

ignore-missing-config-files

Short option: –i
Type: Boolean
Default: FALSE

Do not fail if configuration files do not exist

enable-threaded-callbacks

Type: Boolean
Default: FALSE

Release 4.4 of the Caplin Platform introduced a major new feature and an important pre-requisite for components that sit within the platform.

Prior to 4.4, all DataSource messages were serviced on a single thread and callbacks could be guaranteed to occur only on a single thread. With 4.4, multiple threads service DataSource messages, with the result that callbacks can occur on more than one thread and that more than one callback may be in progress at any point in time.

In order to maintain source compatibility with products built using older versions of DSDK, all callbacks into the application will occur on the thread that called ds_loop(), this naturally introduces a synchronisation point and will impact performance.

Enabling this option will remove the synchronisation point and performance will be increased, however the application must be threadsafe.

syslog-facility

Type: Integer
Default: 176
Acceptable Values:

Name	Value	Desc
auth	32
authpriv	80
cron	72
daemon	24
ftp	88
kern	0
lpr	48
mail	16
news	56
security	32
syslog	40
user	8
uucp	64
local0	128
local1	136
local2	144
local3	152
local4	160
local5	168
local6	176
local7	184

Syslog Facility

event-module

Type: Integer
Default: 4
Acceptable Values:

Name	Value	Desc
epoll	1	Use the epoll event manager (Linux only)
devpoll	2	Use the /dev/poll event manager (Solaris only)
poll	4	Use the poll event manager (Unix only)
select	8	Use the select event manager (not recommended)
iocomp	16	Use the IO completion event manager (Windows only)

This option defines the default event manager used by DataSource threads. It's not recommended to change the default; DSDK will automatically find the best event manager to use on a given platform.

disable-threadname-logging

Type: Boolean
Default: FALSE

Disable logging of thread names

daemon-enable

Short option: –d
Type: Boolean
Default: FALSE

Daemon mode enable

pid-filename

Type: String
Default: %r/var/%a.pid

Filename for the pid file

license-file

Type: String
Default: license-%a.conf

License file

rmi-registry-port

Type: Integer
Default: -1

Port for the RMI registry

rmi-client-port

Type: Integer
Default: -1

Port for the RMI registry

rmi-server-hostname

Type: String
Default: None

RMI server host name

stringpool-hashtable-size

Type: Integer
Default: 100000

Size of hashtable for stringpool

write-monitoring-templates

Type: String
Default: None

Write monitoring templates to file