Embrace operational control with channel management
Align consistent messaging with your workload automation strategy.
Trigger actions
Orchestrate message-based application services.
Initiate exchanges
Automate messages sent to the enterprise service bus.
Control channels
Optimize resource management and control of the message bus.
Modernized enterprise message handling
Tidal’s adapter for JMS makes it possible to define and execute jobs within your enterprise messaging architecture. You can use Tidal jobs to send a message to the bus and even define JMS events so that a message received by Tidal triggers other messages or triggers other activities within your broader scheduling environment.
In addition to automating messaging, integration with Tidal offers resource management and control mechanisms for the message bus:
- Create new channels
- Stop and start channels
- Suspend and resume channels
What the adapter enables
The JMS adapter for Tidal empowers your automation environment to interact seamlessly with enterprise messaging systems. It allows you to send messages to a JMS-compliant message bus and define triggers that initiate downstream jobs when specific messages are received. The result is true event-driven automation, where business events and message exchanges dynamically shape your workflows in real time.
How it works
Adding a JMS job
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 job entry 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.
Defining JMS events
Using the JMS adapter, you can define events acting as a “consumer” that can be used to monitor 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 the user to specify the topic or queue to be monitored, as well as a selector expression for qualifying messages in standard JMS terms.
More Tidal integrations
Automation fabrics are the future
How will your business thrive with an automation fabric powered by Tidal?
Tidal and JMS integration FAQs
-
What is Java Message Service JMS?
Java Message Service (JMS) is a Java API that enables applications to create, send, receive and read messages asynchronously. It allows distributed components in enterprise systems to communicate via messaging, typically using a message broker. JMS supports two primary messaging models: point-to-point (queues) and publish-subscribe (topics), helping to decouple systems and ensure reliable message delivery.
-
What is a JMS adapter?
A JMS adapter is a software connector that integrates applications or systems with a JMS-compliant messaging provider. It enables workload automation platforms or integration tools to send and receive messages through JMS queues or topics, often used to trigger automated processes, pass business events or monitor system health across distributed environments.
-
What is the difference between Kafka and JMS?
While both Kafka and JMS enable message-based communication between systems, they differ significantly in design and use cases.
- JMS is a Java-specific API that abstracts messaging systems like IBM MQ or ActiveMQ. It supports transactional messaging, guaranteed delivery and is well-suited for enterprise applications with strict reliability requirements.
- Apache Kafka is a distributed event streaming platform that handles high-throughput, real-time data feeds. It stores messages on disk and allows multiple consumers to read them at different times, making it ideal for event sourcing, log aggregation and data pipelines.
In short, JMS is a messaging standard and Kafka is a platform. JMS emphasizes transactional messaging and tight integration with Java EE. Kafka is optimized for scalability and real-time data processing.