Configuring DWA Emitters

Introduction

Each DWA Emitter has its own configuration section.

The following sections provide details on DWA Emitter configuration and are structured as follows:

• DWA Emitter common parameters

• DWA Emitter for XFERLOG

• DWA Emitter for OpenSSH SFTP Server

• DWA Emitter for C:D for distributed platforms

Each DWA Emitter has very FT/MFT middleware specific configuration requirements. The following sections provide details on each DWA Emitter will be discussed in more detail.

DWA Emitter Common Parameters

DWA Emitter common parameters -- Prefix emitter.<type>. [<label>].*

This section contains parameters that are shared by all DWA Emitters.

The actual property name contains a qualifier indicating the communicator type and its instance label, e.g. emitter.xferlog[MYXFERLOG1].active=false.

Several instances of the same type of emitter, identified by different labels, can be included in the same dwagent.properties file.

active = true | false	Switch that enables this DWA Emitter. NOTE: Several DWA Emitters can be active at runtime at any time.
logPollingTimeoutSeconds	Time to wait between each polling to check if new events have been produced.
logPollingMaxQuantity	Max number of log records to be read for each poll.
staleSessionCleanUpHours	Number of hours after which an idle session is marked as stale and removed from the emitter local cache. Sessions are persistent objects that emitters use to maintain state while scanning an event source, the persisted state information is normally very short lived.
localeLanguage localeCountry localeVariant	Combining these three values, the agent can understand and decode the Date format found in log files. It defaults to current user settings. The current values accepted for these three parameters are specified at this link:https://docs.oracle.com/javase/8/docs/api/java/util/Locale.html