Win a copy of Machine Learning for Business: Using Amazon SageMaker and JupyterE this week in the Jython/Python forum
or Object Design Style Guide in the Object-Oriented programming forum!
  • 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:
  • Campbell Ritchie
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
  • Knute Snortum
Sheriffs:
  • Liutauras Vilda
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Joe Ess
  • salvin francis
  • fred rosenberger

Communication between Websphere MQ 6.0 and Websphere Application Server ND 6.1

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I have an application that picks up messages from the Websphere MQ queue, processes them and puts the messages back into the same queue. I just wanted to know how to configure the Websphere JMS Provider in the Websphere Application Server 6.1 and how to configure the queue manager (channels, listeners etc.) in Websphere MQ 6.0.
While browsing through the IBM Website I found two ways of communicating with Websphere MQ.
1. Using the Websphere MQ Link.

2. Using the Websphere MQ JMS Provider.

However, I havent been able to decide upon the method required for my application.
Currently, Websphere MQ and Websphere Application server reside on the same physical machine. However this might not be the case in future.
Request you guys to throw some light on this aspect.

Regards
Gautam
 
If you look closely at this tiny ad, you will see five bicycles and a naked woman:
Level Up Your Code with a Pro Java IDE
https://www.jetbrains.com/idea
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!