Author |
Message
|
mq_c22 |
Posted: Tue Jul 08, 2014 12:32 pm Post subject: |
|
|
Novice
Joined: 08 Jul 2014 Posts: 14
|
Can you please share sample code?
Is it possible to define which include WMQ Queue Manager and JMS Queue Manager?
So that QR will receive message from Q1 through cluster definition? |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jul 08, 2014 12:41 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mq_c22 wrote: |
Can you please share sample code? |
You don't want sample Java code from me!
There are any number of samples supplied with the product or available on the web that will suit you. Remember you're just reading from one queue and writing to another.
mq_c22 wrote: |
Is it possible to define which include WMQ Queue Manager and JMS Queue Manager? |
Define where?
mq_c22 wrote: |
So that QR will receive message from Q1 through cluster definition? |
I thought you said above:
mq_c22 wrote: |
There is no connectivity either cluster or physical between these two queues |
So no, if there's no connectivity between the two queues of course you can't use the cluster. If you could use the cluster you wouldn't need code as discussed above. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 08, 2014 12:43 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You keep using "JMS Queue" and "JMS Queue Manager" as if they were meaningful in and of themselves.
Either the Weblogic server is acting as a JMS Provider, and the queue QR is hosted by that JMS Provider, or it's actually MQ that is acting as the JMS Provider and hosting all queues.
If it's the first, then there's no way to have an MQ queue manager move a message to a non-MQ queue manager.
If it's the second, then there's no need to move the message, because you're already reading it from the right queue.
JMS provides a set of standards for applications to use, it does not provide any implementation of those standards.
There's no such thing as a generic JMS queue or a generic JMS queue manager. |
|
Back to top |
|
 |
mq_c22 |
Posted: Tue Jul 08, 2014 12:52 pm Post subject: |
|
|
Novice
Joined: 08 Jul 2014 Posts: 14
|
Requirement is to move Message from WMQ queue to JMS queue in Weblogic server .
What is the solution? |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Jul 08, 2014 12:56 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
mq_c22 wrote: |
Requirement is to move Message from WMQ queue to JMS queue in Weblogic server .
What is the solution? |
You'll have to create or buy a JMSBridge...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 08, 2014 1:02 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
fjb_saper wrote: |
mq_c22 wrote: |
Requirement is to move Message from WMQ queue to JMS queue in Weblogic server .
What is the solution? |
You'll have to create or buy a JMSBridge...  |
Or configure WebLogic to use WMQ as a JMS provider, and then change the JNDI that the application uses to point at the right thing. |
|
Back to top |
|
 |
mq_c22 |
Posted: Tue Jul 08, 2014 1:19 pm Post subject: |
|
|
Novice
Joined: 08 Jul 2014 Posts: 14
|
In the 2nd option are you suggesting Weblogic Foreign JMS Server Configuration With MQ Series. Where remote JNDI name will be the queue names which are on the MQ side. Right?
Between JMS Bridge and this Foreign JMS server configuration which option is better? |
|
Back to top |
|
 |
IanAlderson |
Posted: Wed Jul 09, 2014 2:19 am Post subject: |
|
|
Novice
Joined: 23 Apr 2014 Posts: 17
|
If you are looking at using the Message Bridge that is part of the Weblogic product, then you are bridging from an external JMS transport (MQ in this case) to internal queueing inside the Weblogic server. This is what I take you to mean when you are saying "JMS queue".
I would ask what benefit you think you are getting by using the Weblogic JMS queues as an intermediate store when messages are originating on MQ?
If you do consider using the bridge then look carefully at the Quality of Service (QoS) and Batch Size. Both of these can affect performance. In fact, if your requirement is not to lose a message and you select a QoS of "Exactly Once" then you are asking Weblogic to ensure that no messages are lost (something MQ is already providing for you) then I have found the Weblogic queueing can be a bottleneck. I have seen a project that was using the bridge as an intermediate hop and because of performance issues they switched to a purely MQ messaging to remove this bottleneck (QoS of exactly once and batch size of 1!).
You need to assess your own application requirements and make your own decision on which best suits your needs. But one more thing to be aware of is that your MQ Admins will generally have no visibility of Weblogic queues and troubleshooting messaging issues will therefore need 2 different groups of people/skills.
Personally if you don't have a compelling reason to use internal weblogic queues then using MQ as the single message transport (configured as a foreign JMS provider) is simpler and let weblogic take care of the application.
But certainly you need to consider your own requirements, do your own testing and not rely on advice from a forum.
Good luck. |
|
Back to top |
|
 |
mq_c22 |
Posted: Wed Jul 09, 2014 4:18 am Post subject: |
|
|
Novice
Joined: 08 Jul 2014 Posts: 14
|
Thanks for the details. It helps. |
|
Back to top |
|
 |
|