DWA Emitter for IBM STERLING CONNECT:DIRECT
Prerequisites
This emitter supports monitoring of IBM Sterling Connect:Direct 6.0.0 on distributed platforms (non-z/OS).
Actual detection of Connect:Direct (C:D) file transfer events is performed by accessing C:D Server statistics at runtime using C:D Java API.
C:D Java API jar must be provisioned by the customer on the machine where DWAgent is installed, this jar (usually named CDJAI.jar) is part of IBM Sterling Connect:Direct product installation and it is not distributed with DWAgent.
To include C:D Java API jar into DWAgent CLASSPATH you must create this environment variable DWAGENT_EXT_CP and set its value to the jar file name including its absolute path, then you must export it / make it in the environment where DWAgent is started.
IBM Sterling Connect:Direct versions different from 6.0.0 may be supported as well, depending on C:D Java API compatibility guarantees provided by IBM Sterling across versions.
Given that C:D Java API supports remote connections, DWAgent can also be installed on a machine different from the one where the monitored C:D Server is running.
Configuration reference
DWA Emitter for C:D for distributed platforms -- Prefix emitter.cdmini[<label>].*
nodeName port userId password
Hostname (nodeName), port and credentials to be used when connecting to a C:D instance to retrieve statistical records.
connectTimeoutSeconds
Connection timeout to be assumed when connecting to a C:D instance to retrieve statistical records.
startStatisticsFromDate
Optional start date and time in YYYYMMDD-HHMMSS format starting from which old statistical records will be processed by DWAgent the first time it is started. When this parameter is blank, the assumed default timestamp is the date and time DWAgent is started up for the first time.
additionalRecordIDs=IFED,RJED,RTED
Used to emit event also for non-file transfer operations in this list: if statement (IFED), Run Job (RJED) and Run Task (RTED) operations.
Last updated