| Author |
Message
|
| MQGuy2000 |
 Posted: Tue Feb 15, 2005 6:44 pm Post subject: Help using JMSAdmin |
 |
|
Centurion
Joined: 20 Jul 2003
Posts: 131
|
I am new to mq and JMS. I need to write a standalone application using JMS.
I need help with how to configure JMSAdmin with WSAD.
What is the initial context/ provider url that I should specify in JMSAdmin.config
Your help is greatly appreciated.
Thanks in advance |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Feb 15, 2005 6:52 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
I need help with how to configure JMSAdmin with WSAD.
What is the initial context/ provider url that I should specify in JMSAdmin.config |
Configuring JMSAdmin with WSAD is not documented. Also, if you do it that way, they are not persistent. Every time you reboot your WAS Server insode WSAD, you have to reconfigure them.
However, you can use WSAD's admin console to configure JMS Resources easily and they are persistent. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 16, 2005 5:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| vennela wrote: |
| Every time you reboot your WAS Server insode WSAD, you have to reconfigure them. |
He said
| MQGuy2000 wrote: |
| a standalone application using JMS |
That means that it's not a servlet based application, and therefore not running in WAS.
The Using Java manual should have all of the needed information, if you look in the section on building a JMS connection during runtime, and look at the section on using JMSAdmin.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Feb 16, 2005 10:30 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Jeff:
I didn't understand what you mean to say.
Actually with WSAD4 and WAS4, I could use JMSAdmin with the following values to create the JNDI objects, and use the same values in standalone JMS applications running outside of WAS.
| Code: |
INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
PROVIDER_URL=iiop://localhost:1099 |
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 16, 2005 12:04 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm just saying that: You are correct that using JMSAdmin to create JMS entries in WAS is not a good idea, BUT he is not using WAS and so it doesn't matter.
And in fact, even using the WebSphere Initial Context factory may not be correct - as there may not be a WAS instance that has the JNDI objects he wants to use.
But the Using Java manual does document how to configure JMSAdmin in the four supported Initial Contexts.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| MQGuy2000 |
| Posted: Wed Feb 16, 2005 12:52 pm Post subject: |
|
|
Centurion
Joined: 20 Jul 2003
Posts: 131
|
Thank You Jefflowrey and Vennela. I will try with the leads you gave. Your help and time is greatly appreciated. I will post my questions again if I encounter any problems.
Thanks again. |
|
| Back to top |
|
|
|
|
