| Author |
Message
|
| HenriqueS |
 Posted: Tue Oct 20, 2009 12:22 pm Post subject: MQ Explorer and JMS administration issues |
 |
|
Master
Joined: 22 Sep 2006
Posts: 235
|
Hello folks,
I´ve been trying to use the JMS Administraiton panels provided within MQ Explorer (6.0.2.6).
I am trying to talk with WAS 6.1, so I setup a new
After dealing with several missing classes and supplying the proper jar files, I got stuck with the following situation:
1) The queue definitions contained on WAS do not show. All containers 'Destination' are empty.
2) When I try to browse a 'clusters' container, I see the 'jms' group, when trying to expand it expecting to see the listing of defined queues I get the following:
| Code: |
com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [ Root exception is java.lang.NoClassDefError]' for the object 'SML_CF'.
|
I googled for the above message and got nothing.
Anyone knows a tutorial to configure MQ Explorer to browse WAS MQ definitions? It is being a PITA for me... |
|
| Back to top |
|
 |
| Sam Uppu |
| Posted: Tue Oct 20, 2009 12:32 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
WAS doesn't contain MQ queues. MQ manager will contain the queues. WAS contains JMS queues for which you can't use MQExploer to browse.
You need to configure WAS to talk to MQ.
1. Install MQ client on WAS machine if WAS is remote to MQ manager.
2. Define the queue connection factory and queue destinations.
3. Point the MQ_INSTALL_ROOT environmental variable pointing to MQ client libraries location.
4. Logoff and relogin to the WAS admin console. Restart the WAS server to take the environmental changes to take effect.
This should work.
Thanks. |
|
| Back to top |
|
|
| HenriqueS |
| Posted: Tue Oct 20, 2009 4:46 pm Post subject: |
|
|
Master
Joined: 22 Sep 2006
Posts: 235
|
| Sam Uppu wrote: |
WAS doesn't contain MQ queues. MQ manager will contain the queues. WAS contains JMS queues for which you can't use MQExploer to browse.
|
Sorry if I did mislead you, but I know that WAS may contain pointers , that are 'MQQueue' objects pointing to real base queue names on MQ. You are saying that such queue 'pointer' definitions are not visible under MQ Explorer through the JMS Administration panels?
| Quote: |
You need to configure WAS to talk to MQ.
1. Install MQ client on WAS machine if WAS is remote to MQ manager.
2. Define the queue connection factory and queue destinations.
3. Point the MQ_INSTALL_ROOT environmental variable pointing to MQ client libraries location.
4. Logoff and relogin to the WAS admin console. Restart the WAS server to take the environmental changes to take effect.
This should work.
Thanks. |
My WAS already talks to the MQ installation (in fact its a remote, client connection MQ install).
The fact is that I am not allowed to deal with the WAS web console admin tool, I am a MQ-only guy (WAS is on other shoulders), so I was trying to at least be able to browse queue definitions on WAS using the JMS Administration panels made available on MQ Explorer. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Tue Oct 20, 2009 6:37 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| Quote: |
| I was trying to at least be able to browse queue definitions on WAS using the JMS Administration panels made available on MQ Explorer. |
I am not sure whether this is possible with MQExplorer. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 21, 2009 1:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Sam Uppu wrote: |
| Quote: |
| I was trying to at least be able to browse queue definitions on WAS using the JMS Administration panels made available on MQ Explorer. |
I am not sure whether this is possible with MQExplorer. |
You need a J2EE client to WAS and a JNDI explorer... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| HenriqueS |
| Posted: Wed Oct 21, 2009 6:18 am Post subject: |
|
|
Master
Joined: 22 Sep 2006
Posts: 235
|
Let me see...so I may browse with MQ Explorer JMS Admin panels only queues 'Destinations' that are attached to the 'Default messaging provider' and not the ones attached to the 'WebSphere MQ messaging provider' ?
That´s somewhat bizarre... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 21, 2009 9:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The JMS panels in MQ Explorer are only for exploring JNDI definitions, not for browsing the contents of any containers that are pointed to by those definitions.
If those definitions happen to point to real MQ Queues, you can create a Queue Manager definition in the OTHER parts of MQ Explorer and view the contents of the queues on that queue manager.
You can not use MQ Explorer as a generic message browser for any random JMS Provider. |
|
| Back to top |
|
|
| polypdp |
| Posted: Wed Oct 21, 2009 10:33 pm Post subject: is possible in local. bindings |
|
|
Newbie
Joined: 21 Oct 2009
Posts: 2
|
| I tried all ways, the only solcución I've found is to copy the file. Bindings of the remote machine, and copy on the local machine MQExplorer. |
|
| Back to top |
|
|
| HenriqueS |
| Posted: Thu Oct 22, 2009 12:00 pm Post subject: |
|
|
Master
Joined: 22 Sep 2006
Posts: 235
|
I think I am not talking about 'browsing contents of containers'. I am talking about the pointer and its atributes by themselves.
Let me make it clear. Below is my Jython script:
| Code: |
import java
lineseparator = java.lang.System.getProperty('line.separator')
newjmsp = AdminConfig.getid('/Cell:BcWasCell/JMSProvider:WebSphere MQ JMS Provider')
template = AdminConfig.listTemplates('MQQueue').split(lineseparator)[0]
name = ['name', 'MYQUEUE']
jndi = ['jndiName', 'jms/MYQUEUE']
baseQN = ['baseQueueName', 'MYQUEUE']
mqqAttrs = [name, jndi, baseQN]
print AdminConfig.createUsingTemplate('MQQueue', newjmsp, mqqAttrs, template)
AdminConfig.save()
|
So, I am not being able to see anything about 'MYQUEUE' while browsing with the JMS admin panels from MQ Explorer.
| mqjeff wrote: |
The JMS panels in MQ Explorer are only for exploring JNDI definitions, not for browsing the contents of any containers that are pointed to by those definitions.
If those definitions happen to point to real MQ Queues, you can create a Queue Manager definition in the OTHER parts of MQ Explorer and view the contents of the queues on that queue manager.
You can not use MQ Explorer as a generic message browser for any random JMS Provider. |
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 22, 2009 1:07 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Okay.
You should be able to configure the JMS Admin functions to connect to the WAS JNDI Initial context, and then browse the different portions of the JNDI tree.
But you may need a full WAS admin client or application client installed and you may need to add *a lot* of classes to the classpath.
It seems like you've gotten close but are still missing some classes.
I'd thought there was full discussion of some of this somewhere, but I'm not finding the devWorks article I thought I knew about. |
|
| Back to top |
|
|
|
|
