HCL Workload Automation, Version 9.4

Managing catalogs and services

Creating, editing and deleting catalogs and services.

Before you begin

To manage catalogs and services, you must have the following role:
Required role
TWSWEBUIAdministrator, TWSWEBUIBusinessDeveloper

About this task

To start working with the Self-Service Catalog you must create some services that are associated to HCL Workload Automation job streams. You can then collect similar services into a catalog. Catalogs and services are associated to Dashboard Application Services Hub roles, so that only users having those roles can see and use them. Tap User, in the top right corner, to display details about your user name and roles. Complete the following steps to create and manage catalogs and services:

Procedure

  1. Create a new catalog, which is a collection of similar services, as described in Creating a new catalog.
  2. Create one or more services, which are associated to HCL Workload Automation job streams that are run when the service is submitted, as described in Creating a new service. If you are creating a service that runs on a distributed engine, then the Variable Validation section displays a list of variables if the job stream selected has a variable table associated to it. You can specify variable validation criteria for each variable to standardize the input value.
  3. Gather similar services into the same catalog to make them easier to find, as described in Adding services to a catalog.
  4. Optionally, at any time, you can modify the created objects. For more information about how to do it, see: Editing catalogs and Editing services. For example, when editing a service, you can change the engine and job stream associated to it or make the service temporarily inactive to prevent users from submitting it.
  5. From the Dynamic Workload Console, associate the users who are going to use the Self-Service Catalog to Dashboard Application Services Hub roles to allow them to access the application.
  6. From the Dynamic Workload Console, share the engines used to run the services, with the Dashboard Application Services Hub roles associated to those services, to allow these users to actually submit the services.
  7. Associate catalogs and services to Dashboard Application Services Hub roles to allow only the required users to see and use them, as described in Defining users and roles.