In order to receive messages from a JMS queue or to subscribe to a JMS topic you must configure and deploy an instance of the JMS transport into a fulcrum.

The fulcrum module must provide a specific configuration, specific JMS client jars to connect to the configured JMS message broker, and services which can handle any requests generated by the JMS transport.

For more details on configuration see the JMS Guide.

Deployment

• Place your vendor-specific JMS client jars in the /lib directory of the fulcrum.
• Define the JMS configuration in ffcpl:/etc/JMSConfig.xml in the fulcrum.
• Add the transport class org.ten60.nekernel.jms.JMSTransport to the transport section of the fulcrum module configuration. See Transport Development Guide for more details.

Handling requests

The transport will issue active URI requests with a base URI of either jms-queue-transport:[logical JNDI queue name] or jms-topic-transport:[logical JNDI topic name]. In addition the following arguments are attached:

body	a representation of the message body
header	an NVP (name value pair list) or canonical XML form for the JMS header fields. The following header fields are returned: JMSCorrelationID, JMSDeliveryMode, JMSExpiration, JMSMessageID, JMSPriority, JMSRedelivered, JMSTimestamp, JMSType and JMSReplyTo (returned as a destination URI)
properties	an NVP (name value pair list) or canonical XML form for the set of properties on the message.

Message-Driven-Services

As shown above the JMS transport will issue active URI requests of the form

jms-topic-transport:[JNDI topic name]+header@[...]+body@[...]+properties@[...]

Generally you will configure a module to present a service which will map requests which match the unique jms-x-transport scheme and the JNDI topic or queue name. The service may then process the body, headers and property arguments as appropriate.