| Author |
Message
|
| fabyos |
 Posted: Fri May 15, 2009 12:10 pm Post subject: MQ6 remote + DB2 8.2 with AMI |
 |
|
Apprentice
Joined: 15 May 2009
Posts: 37
|
Hi,
Sorry If I missplaced this post on the wrong area...
I've recently configured WMQ V6 with a database DB 8.2 using AMI.
I've installed the AMI administrator and enabled the MQ Functions... I successfully test a MQSend and MQReceive...
However, the configuration is MQ + DB2 on the same machine...
Is possible to configure this remotelly? So, I could have in a machine A MQ + Broker, and Machine B DB2 8.2, and have some functions/procedure/trigger on DB2 that send messages to MQ remotelly on another machine.
I'm trying to configure a Policy to do this on client channel name and clienttcp server address..
but no response...
this error is showed..
----------------------------
SQL0443N Routine "DB2MQ.MQSEND" (specific name "MQSND3") has returned an
error SQLSTATE with diagnostic text "rc=49:amSesOpen". SQLSTATE=38H01
----------------------------
This is because the Queue Manager is not found on a remoe server...
Someone have done something like this? Or its impossible? |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Fri May 15, 2009 12:23 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi fabyos,
Do you have an MQ Client on the Db box ? Are you able to access the Queue manager from the box atleast ?
Regards. |
|
| Back to top |
|
|
| fabyos |
| Posted: Fri May 15, 2009 1:09 pm Post subject: |
|
|
Apprentice
Joined: 15 May 2009
Posts: 37
|
Hi elvis_gn,
Yes I have a MQ installed on the same machine with DB2. Actually, this is a PoC. I've already tested two Queue Managers on different machines exchanging messages, by configuring a channel, listener and transmission and remote queues.
What i tried to do, is use this test, to have a DB2 MQ Function to send a mensage to a remote MQ on other machine.
I've founded this post:
http://www.ibm.com/developerworks/data/library/techarticle/wolfson/0108wolfson.html
And figure out that is not possible to have the following architecture
Machine A
DB2 (only)
Machine B
WebSphere MQ (only)
and
Machine A ---- MQSEND('message') ---> Machine B
Correct me if i am wrong..
The post put the following configuration:
Machine A
DB2 + MQ
Machine B
MQ
So,
DB2-- MQSEND(...) --> MQ_ON_A -- remote --> MQ_ON_B
There is another configuration for this implementation? |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Fri May 15, 2009 9:57 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi fabyos,
Yes, you cannot have just DB2 on the machine A and connect to MQ on another...but having said that, you do not need to install the server version of MQ on the machine A, all you need is the client version which provides you with the necessary jars to connect to a remote MQ...and the client version is free of cost (which is sometimes the concern of customers).
Regards. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun May 17, 2009 6:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| elvis_gn wrote: |
Hi fabyos,
Yes, you cannot have just DB2 on the machine A and connect to MQ on another...but having said that, you do not need to install the server version of MQ on the machine A, all you need is the client version which provides you with the necessary jars to connect to a remote MQ...and the client version is free of cost (which is sometimes the concern of customers).
Regards. |
Read necessary binaries and jars. The full client supports more languages than just java. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| fabyos |
| Posted: Wed Jun 03, 2009 5:56 am Post subject: |
|
|
Apprentice
Joined: 15 May 2009
Posts: 37
|
I'm recoverying this topic because I didnt made AMI work with DB2 w/o WMQ Server.
My new cenario is DB2 8.2 + WebSphere MQ V6.0.2.6 Client for Windows.
Just to accomplish this, I'm using a VM with WMB 6.1.0.3 + WMQ 6.0.2.6 Server for Windows.
I've created a server connection channel and have a TCP listening to port 1414.
I've edited de amt.xml on <IBM_INSTALLATION>\WebSphere MQ\amt directory...
I created a Policy setting:
| Code: |
Connection Name: QMGR
Connection Mode: Real
Connection Type: Client
Trusted Option: Normal
Client Channel Name: EXTERNAL
Client TCP Server Address: vm:1414 |
The EXTERNAL is the channel I've created as a server connection to WMQ Server on VM.
Someone have already made it work? AMI have a log file?
Another question, IBM says that AMI is discontinued and dont recommend it uses. Unfortunally I need this to work with AMI+DB2+MQ. There is another options to accomplish this? |
|
| Back to top |
|
|
| fabyos |
| Posted: Wed Jun 03, 2009 8:23 am Post subject: |
|
|
Apprentice
Joined: 15 May 2009
Posts: 37
|
After some trials, I'm now able to do a remote connection with AMI + DB2, accessing another QMGR hosted on another machine.
However, I was only able to do it with a machine running
DB2 8.2 + WMQ6.0.2.6 Server AND CLIENT
Without the client I was getting exceptions... I didnt change anything in my previous AMT.xml except that I change the server from
vm:1414 to vm(1414)
| Quote: |
Connection Name: QMGR
Connection Mode: Real
Connection Type: Client
Trusted Option: Normal
Client Channel Name: EXTERNAL
Client TCP Server Address: vm(1414) |
Before installed the client version with server I could accomplish the connection, after it I have tried setting the environment variable MQSERIES following the sintaxe for it
channel/protocol/connectionName
in this case: EXTERNAL/TCP/vm(1414)
But I'm still using MQ Server, but now I know that its possible to use AMI sending messages to a remote QMGR.
My second follow was trying this with a machine that have only DB2 8.2 and WMQ 6.0.2.6 Client for windows. I've installed AMI.
But, now I have this problem:
MQM.dll not founded...
when running enable_MQFunctions...
Browsing the internet I founded that MQM.dll is used to communicate with remote QMGR...
On my previous configuration (WMQ Server+Client) there is a mqm.dll on bin folder, but with only client there isnt....
Am I missing something? And I am still looking for an alternative way to use AMI, since its not recommended anymore...[/quote] |
|
| Back to top |
|
|
| fabyos |
| Posted: Wed Jun 03, 2009 9:11 am Post subject: |
|
|
Apprentice
Joined: 15 May 2009
Posts: 37
|
I did a workaround to accomplish the configuration of MQFunctions..
But it isn't fix my problem because it just validate that a DB2 + MQ Client works uniquelly, but its not enough to have a AMI configuration running properly...
I created a ODBC configuration on a machine with DB2 + WMQ Server to access the DB2 instance... using this data source I was able to run enable_MQFunctions from that machine to produce the DB2MQ functions...
| Code: |
| enable_MQFunctions -n DATA_SOURCE -u DB_USER -p DB_PWD |
But, this is a kind of requirement that I cant afford to...
Any ideas? |
|
| Back to top |
|
|
|
|
