Auditing and Reports

Comprehensive reporting functions track all processes and user activities and write reports and logs. As long as the Automation Engine is active, data on the executions is written and reports are logged. They are kept in the system until they are explicitly removed by a reorganization run. Thus, the Automation Engine provides full auditing capabilities.

Stored Information

• Job Execution

  • Title
  • Name
  • Object version
  • Execution queue
  • Run ID
  • User
  • Passed parameters
  • Target Agent
  • Target user context
  • Target process ID
  • Activation, start and end timestamp
  • Runtime
  • Return status
  • Return code
  • Processor utilization

  In addition, the following information is audited:

  • Issued commands
  • Responses returned by target systems
  • Post processing tasks
  • Runtime metrics
• Task starts and restarts (activation time)

• Modification at runtime including changes done by monitors and status.

  In the case of JCL modifications, the JCL is not written to the revision report. It can be viewed in the object.

• Task abortion
• System changes
• Object creation and renaming
• Source and target folders when moving objects

• Time of imported and transported objects.

  The contents of the .xml and transport files are not written to the revision report.

• Deleted an restored objects

• Object modifications (priority, start type, etc.)

  Exceptions:

  • Modifications made using Automation Engine scripting language.
  • Status modifications of sync objects.
  • Contents of variable objects.
  • Modifications of Calendar objects.
• Accesses of any kind
• User login and logoff

See also:

• Security Concept in AWA
• System Hardening