| Author |
Message
|
| In_love_with_MQ |
 Posted: Tue Mar 21, 2006 2:23 am Post subject: can j2c give same usage as listener port (MQ6.0 BROKER) ? |
 |
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
"J2EE 1.4 supports JMS API implementations that use the J2EE Connector Architecture (J2C). A JMS provider with this implementation, such as the Default Messaging provider in WebSphere Application Server V6, has an MDB associated with its JMS destination using an activation specification. However, the implementation of JMS in WebSphere MQ V5.3 is not built with the connector architecture , so the association is made instead with a listener port, the same as in WebSphere Application Server V5."
Requirement : To implement pub sub via jms on WAS 6.0 using MQ 6.0.
We had suggested our client to use the MDB using listener ports . But we found that usage of listener ports on WAS 6.0 is replaced by "ACTIVATION SPEC"(j2c) which as per docs uses default message provider .
But the above article says that it is not in combination with MQ .
Can i mplement the same functionality ie "JMS pub sub via MQ 6.0 broker using listener ports " ..can activation spec provide the same fucntionality using MQ 6.0 broker .... |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Mar 21, 2006 4:42 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
My advice to you: Read up on the WAS manual and UNDERSTAND the meaning of the activation spec. Best training write one and make sure it works...
This will really make you understand the differences and maybe allow you to bridge the knowledge gap.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| In_love_with_MQ |
| Posted: Tue Mar 21, 2006 5:25 am Post subject: Hi |
|
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
Hi saper ,
I had a look in the pdfs but there is no mentioning that it could be used with Websphere MQ .
Is it possible to have activation spec in combination with Websphere MQ ? |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Mar 21, 2006 8:33 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| I don't understand what you are saying, but you definitely can setup an MDB (deployed in WAS 6) to listen to a specific MQ queue (WMQ 6). |
|
| Back to top |
|
|
| In_love_with_MQ |
| Posted: Wed Mar 22, 2006 1:32 am Post subject: Hi |
|
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
Hi Vennila ,
I know that we can . I have already set up a WAS 6.0 MDB to listen to a MQ QUEUE using the Listener port concept of WAS .
But WAS 6.0 has a new concept called "activation spec" which as per guide uses the default message provider .WAS 6.0 has given listener port still for backward compatibility .
What i am asking is How to setup using activation spec as i cannot see any explanation on how i can use my pub sub requirement using MQ 6.0 using "ACTIVATION SPEC" and Not "Listenet Port" .
If anybody has implemented this kindly throw some light ......
Note : I have already read the pdfs and i am posting here after reading the pdf . |
|
| Back to top |
|
|
| jangochi |
| Posted: Wed Mar 22, 2006 3:19 am Post subject: |
|
|
Novice
Joined: 10 Jan 2005
Posts: 14
Location: UK
|
So the question is: "Is it possible to implement pub/sub using MQv6 by using activation spec in WAS 6 instead of listener ports(supported in WAS v5)?"
I believe the answer is 'no'. I think the activation spec is supported only for default messaging. For the other messaging providers(MQ and generic), listerner ports may be the only option when using MDB. Since I haven't implemented this setup personally, I can't confirm this for sure. Maybe someone with hands on can do that. |
|
| Back to top |
|
|
| In_love_with_MQ |
| Posted: Thu Mar 23, 2006 1:29 am Post subject: Hi |
|
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
Has any body implemented this  ...... if so please do guide !!!! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 23, 2006 4:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
First implement the default JMS Engine in WAS 6.0 and play around with it.
Create your own activation class and play around with it.
UNDERSTAND the concepts behind and see what it would take.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| briancop |
| Posted: Thu Mar 23, 2006 7:22 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2005
Posts: 28
Location: Hursley, UK
|
jangochi is correct. Activation spec is a JCA feature and is used to configure plugins of various types into J2EE app servers. For the default messaging provider in WAS 6, activation spec is the way to configure your MDBs. But when using MQ as the JMS provider in WAS, JCA is not used, so activation specs are not supported.
So the question for you is whether you want to move to using the default messaging provider with activation specs, or keep using MQ configuring your MDBs the way you do today. From your previous postings you seem to already have MDBs working with MQ as the JMS provider, so I'm not sure why you want to change anything. |
|
| Back to top |
|
|
| In_love_with_MQ |
| Posted: Thu Mar 23, 2006 8:00 am Post subject: Hi |
|
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
Hi ,
Thanks for the confirmation .
The reason is that the developers are arguing that "Listener Port" is an old way of doing things and "activation spec" is what is new way .
And also EJB 2.0---> spec says that they support only "activation spec".
So since ours is a new system build , they want to use the latest concepts than which is old ones .
But even then if Mq CONNECTIVITY is not supported , then there is no need in trying this .
But if that is case , in future will MQ be taken out of WAS and the default messaing rules the WAS world ???? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 23, 2006 8:05 am Post subject: Re: Hi |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| In_love_with_MQ wrote: |
| they want to use the latest concepts than which is old ones . |
| In_love_with_MQ wrote: |
| in future will MQ be taken out of WAS and the default messaing rules the WAS world ???? |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jangochi |
| Posted: Thu Mar 23, 2006 8:08 am Post subject: Re: Hi |
|
|
Novice
Joined: 10 Jan 2005
Posts: 14
Location: UK
|
| In_love_with_MQ wrote: |
And also EJB 2.0---> spec says that they support only "activation spec".
|
This is true, but unfortunately no support for MQ as message provider!
| In_love_with_MQ wrote: |
But if that is case , in future will MQ be taken out of WAS and the default messaing rules the WAS world ???? |
Can anyone ruleout this possibilty?  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 23, 2006 1:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
In the J2EE environment the SIBus JMS engine is the way of the future as it gives you a number of enhanced capabilities and provides you with a reliable link to MQ (set up as a foreign bus with qmgr to qmgr channels).
Think about all the advantages of having your thread pool and commit logic handled at container level, from inside a WAS Cluster with a number of clients doing reading and writing to queues accross the network.
If you are operating a WEB Site chances are that you do have a highly available DB around anyway. So extending this service to the SIBus and the JMS engine is of little extra cost.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
