JMS Connector

The JMS Connector is used for invoking asynchronous workload that has, or is exposed via, a JMS interface

It supports the following message exchange patterns:

• Publish
• Request / Reply

The types of workload that might have a JMS interface are message-based workloads that are associated with enterprise messaging environments.

A JMS workload could include, but is not limited to:

Application Container Interfaces

Your organization may have asynchronous workload deployed to application containers such as WebSphere, BEA, JBoss AS, or Oracle AS (and many others). These containers provide JMS services, such as queues and topics, that allow access to the deployed workload by your enterprise scheduler or other applications. This allows them to be included as part of your scheduled business processes.

Middleware

Middleware workload and processes are often asynchronous and are exposed via JMS queues or topics by the middleware software. They usually are the main interface for messaging operations. Using the JMS interface, the middleware workload, processes, and downstream targets of the middleware can be driven by your enterprise scheduler as part of a scheduled business process.

Universal Command Agent for SOA: JMS Connector does not provide the queue or topic infrastructure. You must have a JMS provider with queues or topics configured to use the JMS Connector operations.