Defining workload applications
You can use workload applications to standardize a workload automation solution so that the solution can be reused in one or more Tivoli Workload Scheduler environments thereby automating business processes.
Workload applications are defined in a Tivoli Workload Scheduler environment, referred to as the source environment, using the Workload Designer graphical user interface accessible from the Dynamic Workload Console. You create a new workload application template and then add one or more job streams to it. To reproduce the workload automation solution in another Tivoli Workload Scheduler environment, the workload application template is exported and then after some manual customizations, it can be imported in the target environment.
- A definitions file
- An XML file, workload applicationtemplatename_Definitions.UTF8.xml, that contains the definitions of all the exported objects. These definitions will be deployed in the target environment so as to populate the target database with the same objects existing in the source environment.
- A mapping file
- A mapping file, workload applicationtemplatename_Mapping.UTF8.properties, required to address those objects that are dependent on the topology of the environment and that cannot be reproduced without some manual customization. The target user will modify the file replacing the names of the objects in the source environment with the names that these objects have in the target environment.
- A reference information file
- A reference information file, workload applicationtemplatename_SourceEnv_reference.txt, containing the definitions of the workstations used in the workload application template and other information that can be useful to correctly map the source environment into the target environment so as to make the workload application run.
Workload applications are managed with the wappman command-line user interface. To import a workload application into a target environment, the customized mapping file and the definitions file are passed to the wappman command as input so that all of the objects are automatically created in the Tivoli Workload Scheduler database of the target environment. See wappman command for the complete command syntax and usage.