To communicate statically with a message queue means, that the connection to a queue is defined in the component diagram (and not dynamically within action script). Once a JMS session has been opened by a service by sending or receiving a message, this session stays open and is used for further send or receive operations as long as the service is running. Listeners maintain their own JMS session. See JMS Connection and Session Pooling for more information on connections to a JMS.

Example Files (Builder project Add-ons/JMS):

<your example path>\Add-ons\JMS\uml\simpleStatSendReceive.xml <your example path>\Add-ons\JMS\uml\simpleStatSendReceive_Depl_ActivMQ.xml <your example path>\Add-ons\JMS\uml\simpleStatSendReceive_Depl_WebLogic.xml <your example path>\Add-ons\JMS\uml\simpleStatSendReceive_Depl_GlassFish.xml <your example path>\Add-ons\JMS\uml\simpleStatSendReceive_Depl_GlassFish_FileJNDI.xml

Sending

The sending of messages to a JMS provider is done by the use of the <<JMSAdapter>>. The figure below illustrates the basic structure of an activity diagram using it. The JMS connection settings are specified in the component diagram.

Figure: Activity Diagram for Sending a JMS Message Statically

The <<JMSAdapter>> action can be defined by the help of the Action Wizard.

For sending messages to a JMS provider the following parameters are applicable to the JMS adapter action:

• messageString or messageBlob
• jmsStringMessage or jmsBlobMessage (For more details on the JMS Header see JMS Message Header Fields.)
• sendParameter (For more details see chapter JMS Send Parameter.)