Common Property Files

inc_common.properties is an idiom you can adopt to configure all of the common settings across your workflows instead of configuring on a per processor basis - which you can do if you choose.


Common Settings

SettingDescription
service.namethe name of your integration - this will appear in logs when your integration runs, e.g. “starting service.name”, “finished processing service.name”.
data.charsetthe character set to use for data in your integration - defaults to utf-8.
data.sourcethe origin of the data for your integration - could be a business process or something related to a business process, etc.
data.typethis is the functional type of data in the integration: invoice, sales data, inventory, etc.
debug.modeset the debug mode - see Debug Modes below.
environmentTEDI is environment agnostic, but if you send your logs from all of your environments to the same log-aggregator, you can use environment to differentiate the logs entries.
storage.typefile or memory. see Storage Types below.
storage.retentionif using storage.type=file, storage.retention controls how long to persist the data on disk prior to purging.

Debug Modes

Debug modes are used to mainly aid troubleshooting.

SettingDescription
discardthe integration will run, but silently discards the received content. Use this settings when you want to effectively disable the integration.
verboseincrease logging output.
logAndDiscardlike discard, but will log the content first and then discard it.
logAndContinuelike logAndDiscard except the integration will continue to excute.

Storage Types

The storage type controls where TEDI writes content: in memory or to disk.

SettingDescription
memoryTEDI will not persist any content to disk. All data in transit will be completely persisted to memory - nothing will be written to disk.
fileWill persist the content to disk. Use file when you’re dealing with big files or when you regularly need to view the content for production support, etc. that moved thru TEDI.