| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS Resource Providers: WAS vs WSAD |
« View previous topic :: View next topic » |
| Author |
Message
|
| paton |
 Posted: Thu Jun 27, 2002 3:58 am Post subject: JMS Resource Providers: WAS vs WSAD |
 |
|
Newbie
Joined: 21 Jun 2002
Posts: 6
|
Hi
I've developed some message driven beans in WebSphere Studio Application Developer, and deployed them into the WebSphere Application Server within the dev environment (which is WebSphere v 4.0.2 Advanced Single Server Edition for Multiplatforms).
Using MQ as the JMS provider, the application runs successfully.
However when I deploy the application on to WebSphere v 4.0.3 Advanced Edition for Multiplatforms (using the exact same MQ), the message driven beans are not started. It seems the application server is not binding the names I have setup under the JMS Providers in the admin console to its namespace. Hence when the Extended Messaging Support Service is started, the JNDI names I have told it to bind to are not available.
I have also done a dumpNameSpace and my JMS Queues and QueueConnectionFactories are not there.
Any ideas?
Thanks
Paul |
|
| Back to top |
|
 |
| araghav |
| Posted: Fri Jun 28, 2002 6:11 am Post subject: MDB on WSAD? |
|
|
Novice
Joined: 21 May 2002
Posts: 12
|
Can you built MDB on WSAD? I myself want to use MDB on WSAD 4.0.2 and so far I unable to find any documentation on this feature. Can you please send me some pointers.
Thanks |
|
| Back to top |
|
|
| paton |
| Posted: Fri Jun 28, 2002 6:47 am Post subject: |
|
|
Newbie
Joined: 21 Jun 2002
Posts: 6
|
You got me excited there. I thought you had a solution to my problem.
Anyway, if you're happy just working on WSAD, and not planning on facing the disappointment of actually deploying to the real app server, the best tut I found was:
http://www7b.software.ibm.com/wsdd/techjournal/0204_minocha/minocha.html
Be warned though: I also found this since my original post [background info, the WepShere's MDBs use the Custom Services]:
"...the Custom Services does not support starting threads, opening sockets or accessing JNDI functions. This means that it is probably innapropriate to use the Custom Services..."
from:
IBM WebSphere Application Server Advanced Edition v4, WebSphere JMS/JTA support for MQSeries Overview, 2nd Edition, April 2002, Hodgson, Kirkham, Murphy, Niederheiser
http://www-3.ibm.com/software/webservers/appserv/doc/was_jmsjta.pdf
Good luck |
|
| Back to top |
|
|
| Rclements |
| Posted: Wed Jul 03, 2002 6:54 am Post subject: |
|
|
Novice
Joined: 20 Jun 2002
Posts: 18
|
We have accomplished a 2pc using JMS, WSAD 4.02, UDB 7.2 and MQ5.2.
We had to get help from IBM, but here are the nuts and bolts.
We used JMSAdmin to register a wsqcf connection factory. This is the JMS wrap of XA connection factory needed for the 2PC.
Since MDB is not supported until WSAD5 or Websphere 5 (it is available as you know in the EE version of 4, we dont have that version), we used the dispatcher method of reading messages from the queues. Essentially, we created a user transaction, did the message read, did some db work, and then wrote to the response queue then committed the user transaction.
Regarding the WSAD project, if you have created your owner server instance, ensure that it has its own server-config.xml configuration and that the admin tool is using it, otherwise, you will need to point the admin tool to update the default server-config.xml file.
If you don't specifically save the JMS provider info to the server-config.xml file being used then the entries will not be found in JNDI
hope this is helpful,
ricardo
[/i] |
|
| 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
|
|
|
|
