Introduction to extending HCL Workload Automation

Provides an overview and introduction to how you can extend HCL Workload Automation.

You can extend HCL Workload Automation by creating plug-ins that add functionalities relevant to your business activities.
  • Creating custom plug-ins to extend HCL Workload Automation.
  • Java jobs that implement a Java project that you create on the target workstation.

Creating custom plug-ins

In the previous versions of the product, you can create a custom plug-in using the Integration Workbench to generate a plug-in project. The Integration Workbench is now deprecated, but you can create custom plug-ins using the Workload Automation, Lutist Development Kit.

Once your custom plug-in has been created, you can publish it on Automation Hub and share it with the Workload Automation community.

Creating new plug-ins, you contribute to improve the integration's world and cover all the business automation needs.

Java jobs

When you define a new scheduling job in HCL Workload Automation or HCL Workload Automation for Z, one of the job types you can choose is "Java". For each Java job you choose to define, you identify:
  • A jar containing the Java classes and methods you want to run on the target workstation (on which the dynamic agent must be installed)
  • A set of parameters to be used as input to those classes and methods
The Java project to be run can do more or less what you want it to, but to make this option effective you must follow a set of rules, which are described in this publication.