| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to connect to IIB cloud using MQ config end point |
« View previous topic :: View next topic » |
| Author |
Message
|
| Kumar J |
 Posted: Wed Mar 23, 2016 2:23 am Post subject: Unable to connect to IIB cloud using MQ config end point |
 |
|
Newbie
Joined: 15 Apr 2009
Posts: 2
|
Hi All,
I am trying to implement a POC to connect to WMQ queue manager present on my laptop from sample message flow application deployed in IIB cloud integration node.
I am getting error while trying to enable MQ Client Connection from IIB cloud console to MQ queue manager present in my local laptop.I observe logs as captured below.
"BIP8013E: Integration node 'IIBSWITCH_NODE' does not exist.
An integration node can be used only if it has already been created.
No user action required.
BIP8013E: Integration node 'IIBSWITCH_NODE' does not exist.
An integration node can be used only if it has already been created.
No user action required.
BIP8225E: 'IIBSWITCH_NODE' is not a known component.
The name provided is not a known component.
Provide a different component name.
BIP8225E: 'IIBSWITCH_NODE' is not a known component.
The name provided is not a known component.
Provide a different component name. "
I am not giving integration node name as 'IIBSWITCH_NODE' anywhere explicitly and this name is automatically taken, but error is being thrown.
Below are the steps i performed.
1. Created a MQ Client Connection configuration with details as
- MQ policy Name
- Host - IP address of my laptop
- port of WMQ queue manager listner
- Queue manager Name
- Channel name
- No security is enabled on queue manager and hence username/password details were not provided.
2. Downloaded agent configuration file "iib-agent.json"
3. executed command in IIB console
iibswitch create agentp /config "Filepath"\iib-agent.json
and got response in console as
Creating iibswitch, please wait...
iibswitch created and started.
4. But when trying to validate the agent from IIB cloud console using
"Test agent connection and configuration" > "Test Agent", i am getting error as
"Unable to detect agent. Ensure you have completed the above steps and test the agent again. See troubleshooting for more help."
5. As per trouble shooting steps, when investigated in log file "C:\ProgramData\IBM\MQSI\common\log\IIBSWITCH_log.txt",
IBM documentation regarding the same is not clear with steps for troubleshooting.
Any help to resolve this issue is highly appreciated.
Regards,
Kumar Shanmugam J
Last edited by Kumar J on Mon Mar 28, 2016 1:31 am; edited 1 time in total |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Mar 23, 2016 4:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well, looking as this is cloud communications, I would not feel happy without specifying a username/password.
Don't care if the qmgr does not make use of it.
I do hope you did not have channel auth or connauth running on that qmgr...
The IIBSWITCH_NODE is up and running before you test the connection, right?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Kumar J |
| Posted: Mon Mar 28, 2016 1:29 am Post subject: |
|
|
Newbie
Joined: 15 Apr 2009
Posts: 2
|
I have not created Integration Node 'IIBSWITCH_NODE' manually.
I did not see anywhere in the document asking for Integration node 'IIBSWITCH_NODE' to be created.
Security on the queue manager is not enabled and hence username/password are not needed during initial testing.
Please advide whether 'IIBSWITCH_NODE' need to be created manually? if yes, where can i find the steps and configuration for this integration node. |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Mar 31, 2016 12:06 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
| Please advide whether 'IIBSWITCH_NODE' need to be created manually? |
No, it is created for you when you run "iibswitch create..." Try to delete the one you have, and try again, making sure you specify the path to your config file correctly - it should use "windows path format" on Windows - which means c:\temp\agentp.json, rather than c:/temp/agentp.json for example.
Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
