Cisco Cisco Workload Automation 6.3 User Guide

www.cisco.com

Defining 

JMS Jobs 

Overview

You can start creating and scheduling JMS jobs once you have:



added the runtime users required to run jobs.



defined your JMS connection(s).

Both of the above tasks are described in 

You can then create a JMS job using the context menu within the Jobs pane. You can also edit, copy and delete an 
existing JMS job. If you add a JMS job to a CWA job group, items common between the job group and the JMS job are 
inheritable. However, unless the parent group has a JMS adapter assigned to it, you must clear the 

 option 

and choose an appropriate JMS connection on the 

 tab.

Selecting the option to 

 from the CWA 

 pane displays the 

dialog.

This chapter describes these topics:





Adding a JMS Job

A CWA job is a set of instructions about how, when and where to perform an automated task. For a JMS job, all 
scheduling criteria are available. The only difference between a JMS job and a standard operating system job is that you 
specify a JMS request instead of a command, program or script. In the job rule definition, as with other jobs, you can 
specify a short name for the job (job alias), where to run the job (agent), the days and the times to run the job, the 
dependencies needing to be satisfied before it can run and other runtime criteria. 

A job or job group definition can be added to the production schedule either manually on demand or automatically 
through a calendar. Each entry of the job into the production schedule is called a job instance. A job instance is an 
occurrence of the job definition at a specific time. Job instance history can be reviewed for auditing purposes. Some 
properties of jobs are described below.

From the 

 pane, select 

 to display the 

 pane.