Here is a concise description of jms without the sales hype. In one page are practical advice, links, and examples.
Topics this page:
Since messaging is peer-to-peer, all users of JMS are referred to generically as clients. A JMS application is made up of a set of application defined messages and a set of clients that exchange them. Products that implement JMS do this by supplying a provider that implements the JMS interfaces.
Messages, as described here, are asynchronous requests, reports or events that are consumed by enterprise applications, not humans. They contain vital information needed to coordinate these systems. They contain precisely formatted data that describe specific business actions. Through the exchange of these messages, each application tracks the progress of the enterprise.
Set a general property in the user context.
jms_set_message_property("Msg1_JMSPriority","JMSPriority", "4"); // 4 is default (range 0-9)
Also supported are JMS headers JMSType, JMSDeliveryMode, JMSTimestamp
Send a message to a queue:
Send and receive a message to/from a specified queue after linking a response message with its request message.
jms_send_receive_message_queue("Send and receive Test Message",
for Performance and Capacity Engineers...
Your first name:
Your family name:
Your location (city, country):
Your Email address:
Top of Page