Creating RA JMS Agent Receiver Jobs
You create RA JMS Agent Receiver Jobs by selecting a Connection object and a queue or topic. You can then define the message and specify other settings.
To create an RA JMS Agent Receiver Job:
- Add a Job object of type JMS > RECEIVER and select your RA JMS Agent Solution Agent object in the Host field on the Attributes page.
- Open the JMS Receiver page.
- Fill-in the fields on the right side of the screen.
- Connection
- Queue/Topic
- Select one of these names.
- Select one of these names and edit it.
- Type in a custom name.
- Dynamic Queue/Dynamic Topic
- There are messages on the queue or topic.
- A message consumer is listening on the queue or topic.
- Subscriber Properties Durable
- Subscriber Properties Shared
- Topic is selected above.
- A JMS 2.0 provider is selected in the Connection object.
- Subscriber
- Identify an existing subscriber.
- Name a subscriber to create.
- Topic is selected above.
- The Shared Subscriber or Durable Subscriber boxes below are checked.
- Client ID
- Topic is selected above.
- The Shared Subscriber or Durable Subscriber boxes below are checked.
- Include Message Headers and Properties
- Include Message Payload
- Timeout
- Fail Job on Timeout
- Fail Job on Unexpected Message Type
- Receive Multiple Messages
- Maximum Runtime
- Maximum Messages
- Optionally filter the messages to be received. For more information, see Defining Filters for RA JMS Agent Receiver Jobs.
- Optionally specify report settings for the Job. For more information, see Specifying Report Settings for RA JMS Agent Receiver Jobs.
- Optionally define parsings for the RA JMS Agent Receiver Job headings, properties and message. For more information, see Defining Parsings for RA JMS Agent Receiver Jobs
- Click Save to save the Job.
A JMS Connection object.
Use the radio button control to select a Queue or Topic for your Job. The drop-down lists for the Queue or Topic fields include the queue or topic names defined in the selected Connection object. You can:
These editable value fields can include object variables in the format &<variable name>. The values of these object variables will be replaced at runtime.
Supported by TIBCO EMS and Apache ActiveMQ providers. When checked, if you enter a queue or topic name that does not exist, the RA JMS Agent will create the queue or topic for you. That queue or topic will exist as long as:
This field can also be used to enter the physical name of the queue or topic rather than the JNDI registered name. For example, if you have a queue or topic name that's hidden and you only want others to use the physical name that is not available through JNDI look-up.
Designates the subscriber as a durable subscriber. This checkbox is only active when Topic is selected above. When this box is checked, Subscriber Name and Client ID become required fields.
Designates the subscriber as a shared subscriber. This checkbox is only active when the following are true:
Currently, TIBCO EMS is our only supported JMS 2.0 provider.
The name of the durable or shared subscriber. This field is used to either:
This field is only active when the following are true:
The name for the unique client ID that is used for durable subscriptions. This field is only active when the following are true:
When checked, the RA JMS Agent includes all headers and properties of the message in the Job report.
When checked, the RA JMS Agent includes the message payload in the Job report.
When this checkbox and the Include Message Headers and Properties in the Job Report checkbox above are both checked, the headers, properties, and message payload are all saved to the same Job report.
When the message is a bytes message, and this box is checked, a message is written to the Job report with the number of bytes.
The number of seconds to wait for a message before the Job times out. The default timeout is set in the Agent definition.
Specifies whether the Job should abort upon its first timeout or allow the Job to finish successfully without receiving the message.
If checked the Job should abort on receiving messages with a different type than defined in the parsing section if any parsings are defined.
If checked, the Job can receive multiple messages from its queue or a topic. If you check this box, you must specify a value for Maximum Runtime, Maximum Messages, or both.
Specifies the number of seconds for the maximum runtime. This and the Maximum Messages field are only active when the Receive Multiple Messages checkbox is selected above. Once a Job reaches its maximum runtime or maximum messages, the Job will finish normally.
The seconds specified in the Timeout field apply to each message.
Specifies the maximum number of messages that can be received within one Job execution. This and the Maximum Runtime field is only active when the Receive Multiple Messages checkbox is selected above. Once a Job reaches its maximum runtime or maximum messages, the Job will finish normally.
The seconds specified in the Timeout field apply to each message.