Viewing non durable Topics in heremes

[baiju]

Hi,

I have two topics defined, a durable one and a non durable one (in webmethods)
I am able to browse the durable one through hermes. Is there any way we can browse the non-durable one in hermes 1.8 ?

thanks
Baiju

[Colin]

I think you'll have to carefully read the release notes for the JMS provider and see how it maps JMS concepts to webMethods.

I don't have a webMethods install to test with - i would imagine if you set up a separate connection factory thats got a volatile client group you should be able to watch the non-durable messages as they get published.

Colin.

[baiju]

Thanks Colin.

These are the connection factories available in my set up

hermes.JNDIConnectionFactory
hermes.JNDIQueueConnectionFactory
com.wm.broker.jms.TopicConnectionFactory
hermes.JNDITopicConnectionFactory
hermes.providers.file.FileConnectionFactory
com.wm.broker.jms.QueueConnectionFactory
hermes.NullConnectionFactory
com.wm.broker.jms.ConnectionFactory
com.wm.broker.jms.QueueConnectionFactory
com.wm.broker.jms.TopicConnectionFactory
com.wm.broker.jms.QueueConnectionFactoryAdmin
com.wm.broker.jms.TopicConnectionFactoryAdmin
com.wm.broker.jms.ConnectionFactoryAdmin

Which one should I choose to subscribe a NON-VOLATILE topic to view the content of messages being published?
What are the parameters required to be set up?

[I managed to discover all durable topics (as internal webmethod queues) & view messages successfully using hermes.JNDIQueueConnectionFactory and with parameters

binding - BrokerJMS_Subs
initialContextFactory - heremes.ext.wme.WMEInitialContextFactory
provider url - (specific to mine)]

Thanks in advance
Baiju

[Colin]

I think you should use com.wm.broker.jms.TopicConnectionFactory and configure it with the volatile client group.

You're on new ground here, when I used to use Hermes with webMethods it was only ever in the queue domain to browse client queues. I did not manage to get topics to work when I tried it 6 months ago.

There are a whole host of gotchas with the webMethods idea of what a JMS provider should do, the implementation is far from perfect and has a sorry history. Hopefully its improved recently - good luck!

Colin.