Defining and managing cross dependencies

HCL Workload Automation cross dependencies help you to integrate and automate job processing when:
  • The workload is spread across different scheduling environments, because some of the activities run at different sites or involve different organizational units or require different skills to be run.
  • Even if most of the batch workload is managed locally, none of these environments is completely isolated from the others because they frequently interoperate to exchange or synchronize data and activities.
More specifically, the cross dependency feature is key when you need to synchronize activities between different scheduling environments in an easy way so that you can:
  • Define in one scheduling environment dependencies on batch activities that are managed by another scheduling environment.
  • Monitor the status of the remote predecessor jobs as if they were running in your local environment.
Additionally, you can control the status of these dependencies by navigating from a unique user interface across the different scheduling environments.

This chapter describes how you define and use cross dependencies.

It contains the following sections:
Note: Depending on your needs and requirements, you can choose between internetwork dependencies and cross dependencies to establish a dependency between a job running on the local engine and a job running on a remote HCL Workload Automation engine. See Defining dependencies for a description of the differences between these two types of dependencies.