| Author |
Message
|
| ae06425 |
 Posted: Wed Apr 04, 2012 1:05 pm Post subject: qcf using queue manager on federated node |
 |
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
Hi All
I created a WAS profile(node) on server2 and federated it(node) to DMGR on server1
Now we want to define QCF(queue connection factory) using federated node and using queue manager active on server2 and with bindings mode.
somehow this config is not working.
from dmgr console, in the qcf window selecting federated node(as scope) and a queue manager which is active where the nodeagent is active(server2)
getting this when testing connection:
A connection could not be made to WebSphere MQ for the following reason: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2058' ('MQRC_Q_MGR_NAME_ERROR').
mq version is MQ 7.0.1.3
WAS version WAS 7.0.0.13
Solaris 10
I am thinking my queue manager is local to the node(federated) and this should work in bindings mode.
any idea?
thx |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Apr 04, 2012 9:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
Just to make sure we understood you right
- qmgr is running on server 2
- WAS is running on server 2
- federated was is created and running on server 1
- you want to define a qcf with bindings to the federated WAS node on server1
- This should target the qmgr running on server 2
Forget bindings and use a client connection!
I thought that was clear from the start... apparently not! 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ae06425 |
| Posted: Thu Apr 05, 2012 9:32 am Post subject: |
|
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
qmgr is running on server 1
WAS Node profile(nodeagent process) is running on server 2
WAS Node federated to server 1 (addNode.sh from server2)
yes, I want to define a qcf with bindings to the federated WAS node on server1
yes, This should target the qmgr running on server 2
Thx |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 05, 2012 11:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
No, you can not do this.
A bindings connection can only ever talk to a queue manager on the same host. |
|
| Back to top |
|
|
| ae06425 |
| Posted: Thu Apr 05, 2012 12:14 pm Post subject: |
|
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
I have working example in my another environment where node is created and federated from another server to dmgr and qm is active where the node is running.
so using that node(selecting node scope) and the qm, qcf is defined using binding mode from dmgr console.
(qm is local to that node)
exacly same setup I am trying but this one somehow not working.
missing something or there is something else in that other env taht makes it work.
thx |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 05, 2012 12:43 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Again, the major difference between those two cases is the fact that you are using the QCF on the *same machine* as the queue manager.
In the case you keep trying to get working, you are trying to use the QCF on A DIFFERENT MACHINE than the queue manager.
There's no way to make that work with a BINDINGS connection. NONE.
You can define the QCF anywhere you want.
You can only *use* it on THE SAME MACHINE AS THE QUEUE MANAGER, if it uses a BINDINGS connection. |
|
| Back to top |
|
|
|
|
