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_general_property("Msg1_","JMS_MESSAGE_TYPE","TextMessage");
Send with the TextMessage format instead of "BytesMessage" for the BytesMessage format.

jms_receive_message_queue("Receive message", "TestJMSQueue");

long t=1;
char *chr;
// Define a 20 character string holding the # Seconds since 1970.
t=time(&t);
t = t + 100000;
chr = (char*)malloc(20, sizeof(char)); // must be unallocated to avoid memory leak.
sprintf(chr,"%d",t);

jms_set_message_property("Msg1_JMSExpiration","JMSExpiration", chr);

jms_set_message_property("Msg1_JMSMessageID","JMSMessageID", "Msg1");
jms_set_message_property("Msg1_JMSPriority","JMSPriority", "4"); // 4 is default (range 0-9)
jms_set_message_property("Msg1_JMSRedelivered","JMSRedelivered", "true");

Also supported are JMS headers JMSType, JMSDeliveryMode, JMSTimestamp

Send a message to a queue:

jms_send_message_queue

Send and receive a message to/from a specified queue after linking a response message with its request message.

jms_set_message_property("Set JMSCorrelationID to VuserID", "JMSCorrelationID", "VuserID-{VuserID}");

jms_send_receive_message_queue("Send and receive Test Message",

"Test Message",
"weblogic.jms.inqueue",
"weblogic.jms.outqueue");

lr_message(lr_eval_string("{JMS_message}"));