Objects configuration

These configuration items define how Caplin Transformer deals with objects.

A Transformer object is a piece of data that Transformer manages on behalf of client applications; for example, a financial instrument such as a DataSource record containing a currency pair. Transformer object types include all the DataSource data types.

contrib-return

contrib-return specifies when TRUE that if Transformer receives a contribution (updated data for a subject), it sends the contribution on to the DataSource application (typically an Integration Adapter) that owns the subject of the contribution.

Syntax: contrib-return <boolean>

Type: boolean

Default value: FALSE (a contribution received by Transformer isn’t sent on to the DataSource application that owns the subject of the contribution)

default-object-status-stale

default-object-status-stale specifies when TRUE that the default status of all objects is "stale".

Syntax: default-object-status-stale <boolean>

Type: boolean

Default value: FALSE (The default status of all objects is "ok")

Also see map-limited-status-to-ok in Peer management configuration.

record-max-cache

record-max-cache specifies the maximum number of updates to keep for each record containing type 3 (historic) data.

(This configuration item is equivalent to the Liberator configuration item record-type3-history-size)

Syntax: record-max-cache <maximum-number-of-updates>

Type: integer

Default value: 10 updates

type2-hash-size

type2-hash-size specifies the size in table entries of the Transformer hashtable that’s used to access cached Type 2 data.

(This configuration item is equivalent to the Liberator configuration item record-type2-hash-size)

Syntax: record-type2-hash-size <hashtable-size-in-entries>

Type: integer

Default value: 65536 entries

See also: