| Author |
Message
|
| mathilda |
 Posted: Mon Jun 21, 2010 2:27 am Post subject: Migration from WMQ JMS to WMQ java |
 |
|
Novice
Joined: 16 May 2007
Posts: 16
Location: Sofia, Bulgaria
|
Hi , i have lots of functionality for WMQ but with JMS.
Now i read for WMQ java, but i don't found nothing about listener mechanism .
My questions are:
- what about listener with WMQ java - can i use Listener like JMS architecture or must write thread and get combination.
- what about setTargetClient - is this property only for WMQ jms?
- about durable subscription - is it any special differences wit WMQ jms?
Regards
_________________
On any given Sunday you're gonna win or you're gonna lose. The point is
- can you win or lose like a man? |
|
| Back to top |
|
 |
| calanais |
| Posted: Wed Jun 23, 2010 12:13 am Post subject: |
|
|
Apprentice
Joined: 12 Mar 2010
Posts: 32
|
Hello - assuming the latest WMQ 7.0.1 classed for Java
1) There is not JMS style listener mechanism - a separate thread and get combination will be needed
2) JMS typically adds in a RFH2 header to MQ messages. Therefore this option was present to prevent this from happening. Could go into more detail about when RFH2 headers where added but probably another discussion thread!
3) A durable subscription is a subscription that lasts past the lifetime of the client... what specific thing are you concerned about here?
Matthew |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 23, 2010 11:10 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What are you looking at specifically. You do know that you can run a JMS program in stand alone mode with minimal modifications... no need to rewrite everything in Java base... except may be when needing multiphase commit... and not having access to a J2EE compliant transaction manager... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mathilda |
| Posted: Thu Jun 24, 2010 12:49 am Post subject: |
|
|
Novice
Joined: 16 May 2007
Posts: 16
Location: Sofia, Bulgaria
|
calanais, with JMS subscriber is create with special durable subscriber to identify.
Maybe have difference with Java MQ.
fjb_saper, my problem is very complex - i have JMS adapter that support lots of JMS providers.
And may model is JMS oriented , but Java MQ isn't JMS 
For the moment is too difficult for me, to migrate form JMS to Java MQ - but i need functionality that is missing in JMS - segmentation .
But i will lose listener and knowledge base of JMS 
C'est la vie
In other words - i read documentation i try to understand what i will have with Java MQ and what lose , because at the moment i have working JMS functionality for WMQ and my target mislestone with JAVA MQ should be to have same behavior - Lsitener ( not JMS listener, but ..), durable subscription, message selector, grouping and segmentation .
Regards
_________________
On any given Sunday you're gonna win or you're gonna lose. The point is
- can you win or lose like a man? |
|
| Back to top |
|
|
| calanais |
| Posted: Thu Jun 24, 2010 12:52 am Post subject: |
|
|
Apprentice
Joined: 12 Mar 2010
Posts: 32
|
|
| Back to top |
|
|
| mathilda |
| Posted: Thu Jun 24, 2010 1:09 am Post subject: |
|
|
Novice
Joined: 16 May 2007
Posts: 16
Location: Sofia, Bulgaria
|
Hi Matthew,
you're right for grouping - this is not problem on both "styles".
My current urgent problem is segmentation, because in my current implementation i realized segmentation on application level - groupID and seqID.
But if i received only grouping message or grouping messages with meesage that is segmented in that group, i can't distinguish messages and segments, because in JMS messages are missing flags and properties.
This is my reason to migrate to Java MQ.
Regards
_________________
On any given Sunday you're gonna win or you're gonna lose. The point is
- can you win or lose like a man? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 24, 2010 2:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| JMS messages are missing flags and properties |
Don't quite remember that. However look up the MQ to JMS mapping. For the flags I'm sure they are mapped in some way... maybe not the way you expected... but you might need to use IBM specific properties like JMSX_IBM something... Check the Using java manual...
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mathilda |
| Posted: Tue Jun 29, 2010 4:56 am Post subject: |
|
|
Novice
Joined: 16 May 2007
Posts: 16
Location: Sofia, Bulgaria
|
fjb_saper, you're right, but for segmentation in JMS message there isn't properties about segment, segmentation allowed or last segment.
This information is useful, because when trying to make application segmentation with JMS using grouping i can't distinguish that message is segment or only part of group, without using custom properties.
This i problem when i receive.
But when i send JMS message with grouping and sequence number, other side can't undarstand that this message is segmented.
Regards
_________________
On any given Sunday you're gonna win or you're gonna lose. The point is
- can you win or lose like a man? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 29, 2010 1:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
JMD supports message grouping. It does not support segmenting.
So you need to use grouping to "segment" your messages on both ends.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
