Auditing justification and reporting

From the Dynamic Workload Console, administrators can enforce a policy by which each user making a change to an object must provide a justification for the change. From the Dynamic Workload Console, administrators perform the following steps:

1. From the navigation toolbar, click Administration.
2. In the Security section, select Auditing Preferences.
3. For each displayed engine, you can enable the justification policy. After enabling the justification policy, decide which fields (Category, Ticket, and Description) are required.
4. Optionally create a new category to be added to the default ones in the lower section of the panel.
5. Optionally click on Ticket required to specify the address of the ticketing server and the specific syntax supported on the server, for example: https://ticket.server.com/tickets/{$ticketnumber}, where:

   https://ticket.server.com/tickets/

   is the ticketing server sample address

   {ticketnumber}

   is the ticket number to be provided by the user

After the justification policy is enabled, the justification panel is displayed each time a user performs a change in the Workload Designer however, the justification will not be documented in the file. Justification can be viewed in the database. All other related changes are stored for auditing purposes in the HCL Workload Automation database, in a file or in both, depending on the value you set in the auditStore global option.

For more information about enabling the storage of auditing information from the command line, see the following commands:

• Setting up the composer command-line program
• Setting up the conman command-line program
• Setting global options
• wappman