Use Cases for CA Automic Workload Automation (AWA)

This topic contains several use cases for the AWA bundle.

Use Cases contained:

Use Case 1: File Transfers

An integral part of processing is the transfer of files. The Automation Engine therefore provides an extra object type for this activity. A statistics overview is available for file transfers (as for Job objects) so that the individual executions can be traced.

The steps you would follow are in short:

  1. Create a FileTransfer object.
  2. Define the file(s) to be transferred in its FileTransfer tab.
  3. Set the format of the files to be transferred.
  4. Start the execution of the object, which starts the file transfer(s).

This job creates then several tasks, one for each file transfer that you can then monitor, start, stop or restart, as necessary.

For details refer to the topic Creating File Transfers.

Use Case 2: Maintain the Automation Engine Database

The Automation Engine database shall be archived automatically using a workflow. A dialog should open in which the user can enter the specific settings.

The utilities of the Automation Engine provide the functionality to maintain the database of the Automation Engine. They can be used in batch mode and therefore creating a workflow will automate this database maintenance process.

These are the basic steps you would follow:

  1. As administrator create a static variable, which contains the client number and the values "Y" or "N", depending on whether the step shall be carried out or not.
  2. You then have to create a script, which generates an input dialog. This input dialog receives the relevant information from the user: Client number, settings for archiving, reorganizing and/or unloading the database.
  3. Finally, the Workflow object and Job objects for the workflow will have to be created.
    The workflow should contain a job for each maintenance step.
    In the jobs you have to enter the scripts that determine, if the job is to be carried out and on which client the job should run. The utility will be called in batch mode.
    Alternatively it will be written in the activation report that this particular step is skipped.

Details on setup and configuration you can find in the topic: Database Maintenance with Options

Use Case 3: External Events trigger Reaction

You can have an SAP event trigger a report to the Automation Engine to enable a reaction by the AE. You would use the objects Console Event and Notification and Automation Engine Script elements.

You first have to create and configure the two objects.

The Console Event is used to monitor the SAP event and then trigger the Notification object. The details of the actions and reports are configured via script elements. The Notification then will send a message to a user, which both are specified in the Notification object.

For details refer to: Reaction to External Events