0

How can I get all messages from a JMS topic in Tibco?

I know that I can use a topic subscriber, but it wouldn't fit exactly my needs. I want to start a process only once a day that will read all messages from a topic and process them. I cannot have both a timer and a topic subscriber in the same process.

I tried with "Wait for JMS Topic Message", but it seems that it gets only one message, no matter how many I have in the topic.

Adrian Ber
  • 20,474
  • 12
  • 67
  • 117

3 Answers3

2

I would try going a different direction. You could implement this using 2 separate processes.

One process, a topic subscriber (with a durable) which receives all messages. This process starter should be disabled by default (so the listener is not active).

The second process is a timer, which will activate the first process through Hawk (Engine Command). So every time the subscriber gets activated, it will start processing events.

The problematic part here is the deactivation of the topic subscriber after it is done. For that you need a separate logic, when to deactivate the subscriber. This could also be done by a separate timer or some Hawk Rule which fires, when the subscriber has no more messages.

jens walter
  • 13,269
  • 2
  • 56
  • 54
1

I think the best solution will be to bridge the JMS topic to a queue and use the "JMS Queue Receiver" activity at the start of your process.

Once you start the instance once a day, it will connect and process all the messages in the queue.

Chukwuemeka Onyenezido
  • 329
  • 2
  • 5
  • I was thinking to this solution but I wanted to avoid the bridging. – Adrian Ber Jan 05 '17 at 13:19
  • If it is only one topic and one queue, creating a single bridge shouldn't be too much of a problem. If multiple topics and queues maybe you can batch create them. I know bridges get a bad rep (for some reason) but they generally do not cause any problems. – Chukwuemeka Onyenezido Jan 10 '17 at 15:05
  • I choose a different way of doing things, but your answer seems to be the best, so I accepted it. – Adrian Ber Jan 24 '17 at 14:17
0

A much more natural solution (if it can be implemented) is to just implement a Topic Subscriber (or a Queue subscriber if the Topic is bridged to a Queue) and let the BusinessWorks Engine spawn Job instances whenever a message gets published.

This allows to spread the workload much more evenly than to get all the messages from either a Topic or a Queue.

trankas
  • 11
  • 1
  • 3