Cisco Cisco Workload Automation 6.3 User Guide

Defining JMS Jobs

Defining JMS Events

a provider-specific message ID

an application-specific String

a provider-native byte [] value 

Since each message sent by a JMS provider is assigned a message ID value, it is convenient to link messages via 
message ID. All message ID values must start with the 'ID:' prefix. 

(Optional) In the 

 field, choose the message type from the drop-down list. 

Some messaging systems require that a message type definition for each application message be created and that 
each message specify its type. This ensures that the field is properly set for those providers that require it.

CWA supports these message types:

Text Message

Bytes Message

Stream Message

Map Message

From the 

 list, specify whether the consumer or the client will acknowledge any 

messages it receives.

If the Transacted option is selected, this will be ignored.

The following modes are available:

 – The session automatically acknowledges a client's receipt of a message either when the session has 

successfully returned from a call to receive or when the message listener the session has called to process the 
message successfully returns.

 – The client acknowledges a consumed message by calling the message's acknowledge method.

 – This acknowledgment mode instructs the session to lazily acknowledge the delivery of messages.

In the 

 field, enter the body of the JMS message.

Click 

 to add the job.

Defining JMS Events

Using the JMS Adapter, you can define events acting as a “consumer” that can be used for monitoring selected topics 
or queues in the JMS systems. Events are triggered when a message is received for the monitored entity. Data entry 
fields are provided for user to specify the topic or queue to be monitored as well as a selector expression for qualifying 
messages, in standard JMS terms. 

In the 

 pane, select 

to display the JMS Events pane.

Right-click 

and select 

 from the context menu.

The 

 dialog displays.