| Author |
Message
|
| smdavies99 |
 Posted: Tue Nov 04, 2014 1:02 am Post subject: IIB Explorer Funny! |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Configuration details
Windows Server 2008R2, WMQ 7.5.0.4, IIB 9.0.0.2.
Two VM's in an MSCS config with an Active/Passive setup.
The Qmgr and Broker were upgraded from WMQ 7.0.1.8/Broker 7.0.0.4.
Now for the funny (or where can I bang my head next)
System A (Where the broker was created originally) IIB Explorer shows the broker when running and I can control it (stop/start flows etc) through the GUI.
BUT:::
Under the 'MQ Explorer Content' tab when the Broker is selected, it shows the hostname as
localhost(169.254.1.183)
But the broker is connected and just before the connection, the connection details showed the actual IP address (10.0.0.41) but as soon as the connection was made, it was seemingly obfuscated.
Now, on node 2, IIB Explorer can't connect to the broker (sorry Integration node) at all. The hostname is
localhost(169.254.2.126)
and the connection status is
Disconnected
But there is no option to connect to the broker at all.
If I define a remote connection (and set the appropriate security) I can connect as a remote broker but frankly I'm stumped. There seems no way to edit the connection properties anymore. Boo Hiss!
If I export the config to a .broker file, change the IP address to 127.0.0.1 and import it again, It connects.
Does anyone know where I can 'fix' the connection details in the IIB Explorer workspace (or elswhere)?
you can't erase the connection that does not work either.(wothout deleting the broker as well).
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Nov 04, 2014 6:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Right.
So IIB Explorer thinks you have a broker locally. So it tries to use a bindings connection.
It thinks you have a broker locally because it does discovery at startup to find all of the local brokers. You can't edit the ip addresses of these, because they have none, and because they're rebuilt each time you start up.
Your best bet is to create a workspace that has remote connections to both IP addresses in it. Then use this same workspace on both machines. (ideally by making a copy of it - not by mounting it on a shared disk).
Then you can use the locally discovered bindings connection if the broker is running on the local machine, rather than being in standby. You can use the remote connection if you happen to be on the machine that the broker is running in standby on.
Note, also, that IIBExplorer may end up using two different connections - one JMS and one plain Java - depending on if you're using the stats/monitoring stuff. |
|
| Back to top |
|
|
| ramires |
| Posted: Tue Nov 04, 2014 6:54 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Nov 04, 2014 7:09 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
[ramires]
No. The various mqsi* commands work on both nodes.
[mqjeff]
You do propose a workaround that could. However, that does not explain the local connection working then the QMGR/Broker are running on one node and not the other.
i.e.
Node A - QMGR + Broker + MQExplorer + IB Explorer all ok
Node B - QMGR + Broker + MQExplorer ok IB Explorer not connecting locally.
All WMQ Operations work fine.
I deleted the workspace and when I started the MQ/IB Explorer up again, it re-created everything and the same problem persists.
Back with say V6.1 you could edit the connection properties. Now it seems that you can't do that any longer (unless you use remote connections) which is a bit of a shame.
Note that this does not happen with non migrated QMGR's & Broker.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 04, 2014 7:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
That sounds almost like a permissions error on Node B.
Does it change if you launch MQExplorer from a shell that has mqsiprofile applied? (this shouldn't strictly be necessary, but...) |
|
| Back to top |
|
|
| ramires |
| Posted: Tue Nov 04, 2014 7:31 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
I had the same situation you have on Node B , Explore not connecting locally and connecting via a client connection.
The workaround IT01744 it easy to check
And in my case was with 8.0.0.4 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 04, 2014 7:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
smdavies99 is running IIB v9.0.0.2.
The APAR you mention is supposed to be included in 9.0.0.2.
It's possible he didn't update the IIBExplorer to 9.0.0.2? It is a separate FP installer, I believe... ? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Nov 04, 2014 8:54 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
smdavies99 is running IIB v9.0.0.2.
The APAR you mention is supposed to be included in 9.0.0.2.
It's possible he didn't update the IIBExplorer to 9.0.0.2? It is a separate FP installer, I believe... ? |
Spot on Jeff. What fooled me was that in the list of things installed as shown in the control panel under the IIB, it shows V9.0.0.2 whereas with IIB Explorer it stays at 9.0.0.0 even after the installation of 9.0.0.2.
Thanks.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
