HCL Workload Automation, Version 9.4

Administrative tasks

Administrative tasks required to work with the Application Lab

Administrative tasks are those activities required to enable users to create and work with Application Lab.

Users can create, schedule, run, and monitor simple business processes connected to a single Dynamic Workload Console engine. The processes run on dynamic agent workstations. The processes contain any number of steps to comprise a complete business process. When the process is saved from the Application Lab user interface, a job stream corresponding to the process is saved to the HCL Workload Automation database containing a number of jobs that correspond to the number of steps defined in the process. These objects are also accessible to the administrator from the Dynamic Workload Console. Administrators can identify the job streams and jobs created by users in the Application Lab because their names are prefixed by an environment ID that Administrators define when configuring access to the Application Lab in the security file. When Application Lab users require more sophisticated scheduling capabilities, Administrators might be required to modify the corresponding job stream in the Dynamic Workload Console.

You define the working environment ID for the end users. The working environment is identified by a two-letter prefix which you define in the HCL Workload Automation security file, as described in Granting authorization to users in the security file. Because several users access the same working environment, it is a good practice to create a separate Process library for each user to prevent concurrent access to the same resources. Also, when installing the agents for a specific working environment, consider you must name them with the same <environment_id> prefix you define for the working environment.

The Application Lab is a simple, easy-to-use graphical user interface that connects to an existing Dynamic Workload Console . It connects to a distributed engine connection that is either shared or configured in single sign-on. Users access the Application Lab through a URL that Administrators compose and communicate to the users.

There are a number of tasks that require the intervention of the Administrator to enable users to create and work with processes in Application Lab: