Realtime Export
The Realtime Export configuration category includes the following configurable options:
Concurrent Consumers
Channel Name Prefix
Realtime Export Script (File)
Realtime Export Script (Text)
Transaction-Based Processing
|
|
Concurrent Consumers |
|
|
|
| POSITIVE_INTEGER | |
| The concurrent number of consumers reading messages from the channel. Note that setting this higher than 1 can result in more out-of-order errors. | |
|
|
| (no default) | |
|
|
|
Channel Name Prefix |
|
|
|
| STRING | |
If using POINTCUT source, this is the prefix that will be added to the channel name realtime.export. If you have only a single realtime export module, you can omit this.
|
|
|
|
| (no default) | |
|
|
|
Realtime Export Script (File) |
|
|
|
| Resource Path | |
| If set defines a set of rules to transform resources into exported rows in an external database. | |
|
|
| (no default) | |
|
|
|
Realtime Export Script (Text) |
|
|
|
| JAVASCRIPT | |
| If set defines a set of rules to transform resources into exported rows in an external database. | |
|
|
{
"concatenationDelimiter": " - ",
"retainAllHistory": false,
"namedTransformers": {},
"transformers": []
}
|
|
|
|
|
Transaction-Based Processing |
|
|
|
| BOOLEAN | |
| If enabled, transactions will be processed as a complete unit, as opposed to on a per-operation basis. Note that this only has an effect when running in POINTCUT mode. Also note that any transactions that contain cyclic references will not be processed. | |
|
|
| (no default) | |
|