Getting started

DWAgent interfaces external file transfer (FT) or manage file transfer (MFT) middleware products, detecting relevant events as they are produced and send them to Data Watcher for processing.
DWAgent can also be used to forward events generated by legacy Primeur products like Spazio MFT/S, GBI and others to Data Watcher.
Incoming events generated by legacy products can be read from a Spazio MFT/S queue, an ActiveMQ queue or an IBM MQ queue.
Output events are always sent to Data Watcher over ActiveMQ Artemis (Artemis).

Emitters, Proxies and Communicator

DWAgent is a long-running java process that hosts the following subcomponents:

  • One or more DWAgent Emitters (DWA Emitters), i.e FT/MFT middleware specific connectors that perform event detection at runtime. DWA Emitters responsibilities include:
    • Parsing and analyzing event data
    • Maintaining a persistent logical cursor over the event source (e.g. over a log file)
    • Aggregating information scattered across several events before sending them over to Data Watcher
    • Gracefully discarding irrelevant events
  • One or more DWAgent Proxies (DWA Proxies) among these:
    • Spazio MFT/S DWA Proxy
    • ActiveMQ DWA Proxy
    • IBM MQ DWA Proxy
  • A DWAgent Communicator, managing the connection over Artemis to Data Watcher.

Types of DWA Emitters

Many FT/MFT products communicate relevant events (e.g. “File myfile.txt received” event) to the external world by simply writing event data on human readable or other machine-readable log files.
In these cases, the associated DWA Emitter will parse and analyze the relevant portions of this log file and normalize them before sending them to Data Watcher.
On the other hand, when FT/MFT products (mainly MFT), support monitoring APIs, user exits or callbacks, the associated DW Emitter will include the appropriate bindings to exploit these monitoring interfaces.
Other FT/MFT products (mainly MFT) support some native form of monitoring event publishing. In these cases, the associated DW Emitter will include event subscription capabilities allowing access to the underlying event stream.

Environment

Prerequisites

  • JRE 1.8

Supported platforms

  • Linux RHEL 8.2
  • Windows 2012 R3 or later

Supported Data One versions

  • Data One 1.10.0 or later

Emitters

  • DWA Emitter for XFERLOG
    • This emitter can monitor any FTP / FTPS server conforming to XFERLOG logging format (e.g., WU-FTPD and vsFTPD on linux)
    • Please refer to section DWA EMITTER FOR XFERLOG for more details about expected XFERLOG format
  • DWA Emitter for OpenSSH SFTP Server
    • This emitter can monitor OpenSSH 8.0 SFTPServer on Linux. Other versions can be supported under specific conditions
    • Please refer to section DWA EMITTER FOR OPENSSH SFTP SERVER for more details
  • DWA Emitter for IBM Sterling Connect:Direct
    • This emitter can monitor IBM Sterling Connect:Direct 6.0.0. Other versions can be supported under specific conditions
    • Please refer to section DWA EMITTER FOR IBM STERLING CONNECT:DIRECT for more details

DWA Proxies

  • DWA Proxy type for Spazio MFT/S
    Proxied system: Spazio MFT/S v2.x

  • DWA Proxy for IBM MQ
    Proxied systems: IBM MQ v7.x, v8.x, v9.x

  • DWA Proxy for ActiveMQ
    • Proxied systems: ActiveMQ versions embedded in Spazio MFT/S v2.x, ActiveMQ versions embedded in Spazio File Governance v2.x