JMS Service

A service for polling a JMS queue or topic.

Description/Features

Installation

Following these installation steps, you'll notice we've choosen the activemq as our JMS implementation. If you're using another implementation, change the setting accordingly.

1. Shutdown you Jira installation if running.
2. Configure your application server to use JNDI to point a JMS resource. For example, using Tomcat 4, you must add to your server.xml the following lines under the context configured for Jira:

     <Resource name="jms/ConnectionFactory" auth="Container"
               type="org.activemq.ActiveMQConnectionFactory"/>
     <ResourceParams name="jms/ConnectionFactory">
       <parameter>
         <name>factory</name>
         <value>org.activemq.jndi.JNDIReferenceFactory</value>
       </parameter>
       <parameter>
         <name>brokerURL</name>
         <value>reliable:tcp://localhost:61616</value>
       </parameter>
       <parameter>
         <name>brokerName</name>
         <value>LocalActiveMQBroker</value>
       </parameter>
       <parameter>
         <name>useEmbeddedBroker</name>
         <value>false</value>
       </parameter>
     </ResourceParams>
   

3. Copy the file pronetics-jira-JMS-1.4.jar in the WEB-INF/lib folder of your atlassian-jira installation.
4. Unzip the file services.zip and copy it in the WEB-INF/classes folder of your atlassian-jira installation. Make sure that when you copy the directory, the structure is services/com/pronetics/...
5. Copy the needed libraries for your JMS implementation in the WEB-INF/lib folder of your atlassian-jira installation.
6. Start jira.

Service Configuration

In the services configuration page, create a new service with the class:

com.pronetics.jira.service.services.jms.JmsService

You can consider, provided by this installation, just as an example. It handles an ObjectMessage, expecting a well formed issue in the object of the jms message, and just writes it into jira. You'll probably need to change this handler to fit your needs.

Config parameters

• Consumer Name: The name of the consumer. Used usualy in a durable connection.
• Queue/Topic Name: The name of the queue or topic to poll.
• Is Topic: true if you want to register to a topic, false if you want to connect to a queue
• Transacted: The transacted attribute for a durable connection
• Durable: true if a durable consumer is needed.
• Timeout: the time to listen to the queue after sleeping the Thread
• Time To Pause: the time to block the message polling when the handler issues a pause event.
• Is Listener: true registers the service as a message listener. The false settings is unreliable and experimantal: it just loops in an infinite cycle to poll messages from the queue.
• Auto Acknowledge: toggles the autoacknowledge mode
• Acknowledge After Handling: true acknowledges the message after it has been handled. Il false, the handler must tell if the message must be acknowledged.
• Jms Data Source: the datasource name you defined in the server.xml

Screenshots