| Author |
Message
|
| gpklos |
 Posted: Wed Dec 01, 2004 7:35 pm Post subject: jmsadmin problem-Here's one I haven't seen a solution to yet |
 |
|
Centurion
Joined: 24 May 2002
Posts: 108
|
I am trying to get MQ JMS (5.3) to work with WAS 4.06. Basically I am running MQ on W2K and WAS is on a separate box. So basically I am trying to run JMSADMIN on my W2K PC. I tried to setup the JMSADMIN.config so it would update the JNDI on WAS 4.06, which is a separate box. I used the following.
INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
SECURITY_AUTHENTICATION=none
PROVIDER_URL=iiop://dusty.ussteel.com:1999/
I figured this would go to the box dust.ussteel.com:1999. Except when I run the JMSADMIN it fails on the INITIAL_CONTECT_FACTORY because it can't find the com.bim.websphere.naming.WsnInitialContextF class. This class isn't on my machine especially since I don't have websphere on my machine. From what I have read I don't need websphere on my machine especially since I can update a JNDI on another box, via PROVIDER_URL=iiop://dusty.ussteel.com:1999/
Any explanation or help would be appreciated. I've looked over documentation here and on ibm's site, but haven't seen this problem yet.
Thanks,
Gary |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Dec 02, 2004 5:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You are looking for a wrapper class that was used in older versions and that is part of WAS ?
WAS 5.x does not use this wrapper class anymore...
5.3 has been optimized to run with WAS 5.x
Anyways read up (using Java appendixes). Can't remember if the wrapper was supposed to be used for 2 phase commit. With MQ being on a different box than WAS this ain't happening anyway....
Use a standard QCF def and don't forget to set all the client attributes...
Enjoy  |
|
| Back to top |
|
|
| gpklos |
| Posted: Fri Dec 03, 2004 5:12 am Post subject: jmsadmin problem-Here's one I haven't seen a solution to yet |
|
|
Centurion
Joined: 24 May 2002
Posts: 108
|
Thanks for the reply. I will keep all that in mind. Unfortunately I'm stuck using WAS 4.06 for now. That part is out of my control. I am going to try and get the jar files that are necessary for me to run the JMSAdmin as a client.
Thanks again!
Gary |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Dec 03, 2004 7:20 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I did this a while back.
These are the jar files I got from WAS 4 and put in in the CLASSPATH which JMSAdmin can see
websphere.jar
ns.jar
iwsorb.jar
ibmorb.jar
I am not sure if all of them are needed. The actual class that JMSAdmin is looking for is is websphere.jar. |
|
| Back to top |
|
|
| gpklos |
| Posted: Wed Dec 08, 2004 4:18 am Post subject: jmsadmin problem-Here's one I haven't seen a solution to ye |
|
|
Centurion
Joined: 24 May 2002
Posts: 108
|
Thanks, I added the jar files as you specified and that actually worked. Thanks a lot for your help!! It is amazing that I didn't find that documented somewhere. I figured lots of people have done it.
Gary  |
|
| Back to top |
|
|
|
|
