| Author |
Message
|
| serpota |
 Posted: Thu Feb 02, 2012 6:37 am Post subject: |
 |
|
Voyager
Joined: 26 May 2006
Posts: 85
|
| bruce2359 wrote: |
| ...puts your career at risk. |
The chinese symbol of "crisis" has 2 meanings/translations ...
a) risk, danger
b) oportunity, chance
Have a nice day. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Feb 02, 2012 6:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| serpota wrote: |
The chinese symbol of "crisis" has 2 meanings/translations ...
a) risk, danger
b) oportunity, chance |
Ably demonstrated in this example. There's a risk this lash up will collapse in production some time after implementation, a danger that a huge lawsuit will be the last straw for the cash strapped organisation you work for (we started this trying to save WMQ license fees), an oppertunity for a lot of lawyers to get even richer and a fair chance you'll be retired before this all goes down.
Just commute your pension as a lump sum & don't leave an address you're retiring to. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| serpota |
| Posted: Thu Feb 02, 2012 7:02 am Post subject: |
|
|
Voyager
Joined: 26 May 2006
Posts: 85
|
Heard it loud and clear ... and understood ... Thanks, Vitor.
Here is what I am reading right now :
>>> http://activemq.2283324.n4.nabble.com/ActiveMQ-integration-with-WebSphere-MQ-td3550031.html
(copy and paste ...)
ActiveMQ can talk to IBM's MQ via the "jmsBridgeConnectors"
I've tested it in 5.5 successfully.
I defined a remote ConnectionFactory like so:
<bean id="remoteBlueFactory" class="com.ibm.mq.jms.MQQueueConnectionFactory">
<property name="transportType" value="1"/>
<property name="hostName" value="ibmbrokerhost1"/>
<property name="port" value="1414"/>
<property name="queueManager" value="QMGRNAME"/>
<property name="channel" value="UNSECURE.BKR.CHANNEL"/>
</bean>
We saw an issue where ActiveMQ needed to be restarted to send messages "stuck" while the IBM MQ was down, but ...
======================
Cheers. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 02, 2012 7:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| serpota wrote: |
| using "server" interface (not MQ Client API), but cant use MQ product. |
You're using the MQ Client API to do this. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 02, 2012 7:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| serpota wrote: |
| ActiveMQ can talk to IBM's MQ via the "jmsBridgeConnectors" |
Of course it can. Any JMS-aware piece of software can.
| serpota wrote: |
I defined a remote ConnectionFactory like so:
<bean id="remoteBlueFactory" class="com.ibm.mq.jms.MQQueueConnectionFactory">
<property name="transportType" value="1"/>
<property name="hostName" value="ibmbrokerhost1"/>
<property name="port" value="1414"/>
<property name="queueManager" value="QMGRNAME"/>
<property name="channel" value="UNSECURE.BKR.CHANNEL"/>
</bean> |
The definition of a WMQ client connection. Which I think was suggested way back, has it's own issues and is a mile away from what you originally wanted which was a non-IBM queue manager your end for the remote queue manager to talk to over a sender channel.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| serpota |
| Posted: Thu Feb 02, 2012 7:22 am Post subject: |
|
|
Voyager
Joined: 26 May 2006
Posts: 85
|
... Thanks Jeff and Vitor - you are both right ... of course.
I was just reading the forums ... before posting ... as I learned here
jejeje |
|
| Back to top |
|
|
| serpota |
| Posted: Thu Feb 02, 2012 7:28 am Post subject: |
|
|
Voyager
Joined: 26 May 2006
Posts: 85
|
Guess now I can improve my question a bit ... becoming ...
Can we use "MQ Connection Factory" to acces the "MQ Server API" ?
Any pointers, urls, etc .. are welcome.
Maybe I need a JMS forum better ... |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 02, 2012 7:37 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
More accurately, you came to us with a specific, technical solution in mind - an absolute requirement.
Whoever gave you this requirement did not understand the WMQ product, and the products (IBM and other) that can work with WMQ. This person made a fundamental error in judgement.
Unfortunately, this is not all that unusual.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| serpota |
| Posted: Thu Feb 02, 2012 7:42 am Post subject: |
|
|
Voyager
Joined: 26 May 2006
Posts: 85
|
Bruce : you are absolutely right - the man who came to me had no idea of MQ. He had a bussines opportunity they call, replacing a SMS-application MQ-based messaging server with they own server (without MQ). He searches and wants to pay some tech person (maybe me) to connect MQ SRVR channel to JMS ... so here we are.
Sorry we cant use Client API, jejeje. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 02, 2012 7:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| serpota wrote: |
| Can we use "MQ Connection Factory" to acces the "MQ Server API" ? |
As has been said several times in this thread, the only thing that can connect to a channel that is NOT a SVRCONN is another queue manager.
This means that JMS can't do it either! NOTHING ELSE can use the MQ Server API except a queue manager.
Ask him to explain how you can drive a lamborghini without owning a lamborghini, and then you will tell him how to use an MQ server without owning an MQ Server. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 02, 2012 8:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| serpota wrote: |
| Can we use "MQ Connection Factory" to acces the "MQ Server API" ? |
Yes. If you have the MQ server installed (the licensed component that supports a running queue manager).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| serpota |
| Posted: Fri Feb 03, 2012 3:59 am Post subject: |
|
|
Voyager
Joined: 26 May 2006
Posts: 85
|
| mqjeff wrote: |
As has been said several times in this thread, the only thing that can connect to a channel that is NOT a SVRCONN is another queue manager.
This means that JMS can't do it either! NOTHING ELSE can use the MQ Server API except a queue manager.
Ask him to explain how you can drive a lamborghini without owning a lamborghini, and then you will tell him how to use an MQ server without owning an MQ Server. |
Got it, Jeff. Loud and Clear. Thanks alot. |
|
| Back to top |
|
|
| serpota |
| Posted: Fri Feb 03, 2012 4:04 am Post subject: |
|
|
Voyager
Joined: 26 May 2006
Posts: 85
|
| Vitor wrote: |
| serpota wrote: |
| Can we use "MQ Connection Factory" to acces the "MQ Server API" ? |
Yes. If you have the MQ server installed (the licensed component that supports a running queue manager). |
Well, for me, the MQ Server API is represented by "MQM.DLL" ... not by the complete MQ Server product ...
So maybe I can have the DLL without the rest ...
No ? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 03, 2012 4:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The only thing that mqm.dll would allow you to connect to is a queue manager running on the same machine.
You can certainly copy mqm.dll from one machine to another, and run the risk that it might actually work until the wrong moment.
You could indeed perform a full server product install on a machine and not pay a license for that because you are not running a queue manager. But it doesn't let you do anything, because you're not running a queue manager... |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 03, 2012 6:13 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| serpota wrote: |
Well, for me, the MQ Server API is represented by "MQM.DLL" ... not by the complete MQ Server product ...
So maybe I can have the DLL without the rest ...
No ? |
Yes. And what do you think it's going to connect to? It's the server api that connects to the server components. It's the client api that connects to components hosted at any location via the network. It certainly won't allow you to receive traffic sent by a remote queue manager over a sender channel to the host where you're running this lash up.
No matter how much you thrash around like a fish on a hook, it won't change the fact you're caught.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
