• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Websphere JMS Queue Bridging  RSS feed

 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Posting on behalf of a friend. Urgent help required...

============================================================================
I require suggestions on bridging 2 JMS queues set up on 2 different IBM Websphere 6.0 servers.

In my application I have a MDB listening to a local JMS queue and an external application which will post messages on to their own JMS queue. Now bridging has to done between these two JMS queue.

We have configured JMS Q using Default messaging under JMS Providers and not WebSphere MQ. Kindly suggest as to how do I go about bridging them.
Can the bridging be done only by configuring JMS provider using Websphere MQ and not through Default messaging?
I also wanted to know if my MDB can be configured to directly listen to the external application?s JMS queue thus avoiding bridging?

============================================================================
 
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You won't be able to ask questions for your friend any more because I have closed your account.

When you re-register, please pay attention to the naming rules.

Dave
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!