| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ME01 and "Non-Local" Queues |
« View previous topic :: View next topic » |
| Author |
Message
|
| fordcam |
 Posted: Tue Apr 26, 2005 9:03 am Post subject: ME01 and "Non-Local" Queues |
 |
|
Apprentice
Joined: 28 Mar 2002
Posts: 35
Location: MGIC
|
Apologies in advance for my ignorance about JMS, as this is pretty new to me.
I'm hoping to use ME01, the WMQ Initial Context, in order to use MQ as my JNDI repository. I've installed it, along with MS0B (Java PCF classes). It actually worked the first time, and I was able to connect to the queue manager.
But when I did a "dis ctx" I was surprised to see just the queue manager's local queues displayed. I looked at the README a little closer and found that "a com.ibm.mq.jms.MQQueue object for each non-system, local queue on the queue manager."
I'd prefer to use ME01 if possible, because I like the idea of letting the queue manager be the repository, partly because I'm in charge that way. If I use LDAP, I need to get two other groups involved. It's also appealing to automatically have all of my local queues be JMS objects without any further work. But if a remote queue can't be a JMS object, I may not be able to go this route.
Any pointers? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Apr 26, 2005 9:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Use the JNDI repository of the container that your JMS applications are going to run inside.
If they are *all* running as standalone applications, then put a file based repository on a networked drive location.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fordcam |
| Posted: Tue Apr 26, 2005 9:51 am Post subject: |
|
|
Apprentice
Joined: 28 Mar 2002
Posts: 35
Location: MGIC
|
| jefflowrey wrote: |
Use the JNDI repository of the container that your JMS applications are going to run inside.
If they are *all* running as standalone applications, then put a file based repository on a networked drive location. |
Are there technical reasons for this, or is it more of a philosophical guideline?
The container they will run in is Weblogic, and there are a few reasons why I would like to avoid using WLS as the JMS repository. One is that, just like with LDAP, we'd need to get a new group involved every time an object needs to be defined. I can define a new MQ queue in a flash, but getting the WLS guys on board is no easy task. The other thing I have to consider is that MQSeries is likely to be here after Weblogic is gone. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 26, 2005 10:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Having no experience with WLS, I'd say it's more of a philosophical guideline.
That said, you may run into difficulties trying to use a different JNDI context within WLS.
I don't know the ME01 support pack either.
On the other hand..
The only things that will need to use JNDI resources are J2EE applications. The JNDI objects will only be need to be created once for the initial application deployment (and changed when necessary - only for MQ network changes or app changes - not often). Most shops consider the creation of JNDI entries to be part of the application deployment - and allow the MQ administrator to be ignorant of that side of the house. The MQ Admin just needs to create the queues before deployment time and not worry about the JNDI at all. So if you're the MQ admin, you shouldn't need to care about the JNDI. If you're the app deployer, you should either have the ability to create the JNDI resources yourself... or be able to point the finger at the other people who are keeping you from doing your job. And if you're the architect or app developer, you should allow your infrastructure people to handle this..
If WLS goes away, then you'll need to redeploy the apps in the "new thing". And thus, it's not a lot of additional work to create new JNDI resources.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Apr 26, 2005 1:54 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| I'm hoping to use ME01, the WMQ Initial Context, in order to use MQ as my JNDI repository. |
Not a good idea.
Using the support pac, if I create a QCF or Q, it will create real MQ objects and I don't think that you want to happen that. |
|
| Back to top |
|
|
| fordcam |
| Posted: Tue Apr 26, 2005 2:30 pm Post subject: |
|
|
Apprentice
Joined: 28 Mar 2002
Posts: 35
Location: MGIC
|
| vennela wrote: |
| Quote: |
| I'm hoping to use ME01, the WMQ Initial Context, in order to use MQ as my JNDI repository. |
Not a good idea.
Using the support pac, if I create a QCF or Q, it will create real MQ objects and I don't think that you want to happen that. |
But I'm planning to go the opposite way. I'm planning to continue to just administer MQ, creating queues in the normal fashion (runmqsc/PCF). ME01 will automatically make available a JMS object each time I create a queue. It would eliminate the need to create a QCF or Q objects.
I'm an MQSeries administrator, so I'm looking at this through an MQSeries administrator's eyes. It's just my nature. But we've got literally thousands of MQSeries queues, and have just one MDB (soon). So I'd like to make this as easy as I can. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 27, 2005 3:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Again, leave it up to the person who's job it is to deploy the application into WLS to create the JNDI entry.
If that person is you, then your company needs to hire a WLS admin, you sound very busy as an MQ Admin alone.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Apr 27, 2005 9:20 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| I'm an MQSeries administrator, so I'm looking at this through an MQSeries administrator's eyes. It's just my nature. But we've got literally thousands of MQSeries queues, and have just one MDB (soon). So I'd like to make this as easy as I can. |
Moreover if the reason for creating jndi resources is to setup an MDB, then what you are trying to do may not work at all. Because for an MDB, you need to setup a listener port (in WAS we do that, I don't know about WLS, but I am guessing it would be the same). If you have to create a listener port, then you need a QCFs, Qs etc which should be within the context of WLS.
So,
| Quote: |
| Again, leave it up to the person who's job it is to deploy the application into WLS to create the JNDI entry. |
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
