| Author |
Message
|
| mca |
 Posted: Fri Aug 26, 2016 7:13 am Post subject: <Resolved>IIB Web URI port |
 |
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
We upgraded our Linux server from WMB v8 to IIB v10. We have three IIB nodes running on the server and i assigned 3 ports for URI administration. BRKR1=4414; BRKR2=4415 & BRKR3=4416
mqbrkr@Dev /home/mqbrkr >mqsilist
BIP1353I: Integration node 'BRKR1' with default queue manager 'QMGR1' is running.
BIP1284I: Integration node 'BRKR2' with default queue manager 'QMGR2' and administration URI 'http://DEV:4415' is running.
BIP1284I: Integration node 'BRKR3' with default queue manager 'QMGR3' and administration URI 'http://DEV:4416' is running.
mqbrkr@Dev /home/mqbrkr >mqsireportproperties BRKR1 -b webadmin -o HTTPConnector -a
HTTPConnector
uuid='HTTPConnector'
port='4414'
mqbrkr@Dev /home/mqbrkr >mqsireportproperties BRKR2 -b webadmin -o HTTPConnector -a
HTTPConnector
uuid='HTTPConnector'
port='4415'
mqbrkr@Dev /home/mqbrkr >mqsireportproperties BRKR3 -b webadmin -o HTTPConnector -a
HTTPConnector
uuid='HTTPConnector'
port='4416'
I am able to connect to BRKR2 & BRKR3 using IIB v10 toolkit, but i am not able to establish connection to BRKR1. I did the same exact steps for these three IIB nodes. Can someone tell me what i might be missing on BRKR1?
Last edited by mca on Mon Aug 29, 2016 9:51 am; edited 1 time in total |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Aug 26, 2016 10:29 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Did you restart BRKR1 after defining the port?
_________________
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 |
|
|
| vishBroker |
| Posted: Sun Aug 28, 2016 7:53 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
In the toolkit, go to the Integration Node and open the webAdmin Interface.
Note the URL that gets opened.
check - whether it is HTTP and HTTPS ? If your port NOT listening over HTTPS and you are using HTTPS in the URL - it will not show anything. In that case, change the protocol.
you can also try and use IP address instead of name to make sure, it is not an issue with network. |
|
| Back to top |
|
|
| mca |
| Posted: Mon Aug 29, 2016 6:00 am Post subject: |
|
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
We restarted the Broker few times after the port assignment.
Also, for us to check the Web URI port, the issue is...we are not able to connect the toolkit to Integration Node (BRKR1) to find out if it is HTTP or HTTPS. We are able to connect to other integration nodes (BRKR2 & BRKR3) on the same server, but not BRKR1.
When i do mqsilist, the BRKR1 doesn't show administration URI not running as listed below. Does this have to do anything with toolkit not able to connect to Broker ?
mqbrkr@Dev /home/mqbrkr >mqsilist
BIP1353I: Integration node 'BRKR1' with default queue manager 'QMGR1' is running.
BIP1284I: Integration node 'BRKR2' with default queue manager 'QMGR2' and administration URI 'http://DEV:4415' is running.
BIP1284I: Integration node 'BRKR3' with default queue manager 'QMGR3' and administration URI 'http://DEV:4416' is running. |
|
| Back to top |
|
|
| vishBroker |
| Posted: Mon Aug 29, 2016 6:27 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
Run following command
C:\Program Files\IBM\IIB\10.0.0.5>mqsireportproperties IIBNODE -b webmin -o server -a
--
output =>
server=''
uuid='server'
enabled='true'
ldapAuthenticationUri=''
enableSSL=''
BIP8071I: Successful command completion.
--- |
|
| Back to top |
|
|
| mca |
| Posted: Mon Aug 29, 2016 6:42 am Post subject: |
|
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
mqbrkr@Dev /home/mqbrkr >mqsireportproperties BRKR1 -b webadmin -o server -a
server=''
uuid='server'
enabled='false'
ldapAuthenticationUri=''
enableSSL='' |
|
| Back to top |
|
|
| vishBroker |
| Posted: Mon Aug 29, 2016 7:24 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
Now you know, why it is not running.
Enable it.
C:\Program Files\IBM\IIB\10.0.0.5>mqsichangeproperties TESTNODE_vpandit -b webadmin -o server -n enabled -v true
BIP8071I: Successful command completion.
And try again after restarting the node. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Aug 29, 2016 8:49 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
If this is the reason you can't access the WebUI then you need to add these commands (to show, to set and to show again) to the scripts that you use to create the broker in the first place.
What? not have any scripts?
Now is the time to create them and put them unser source control.
Properly annotated scripts will save you time and an awful lot of stress in the future.
Plus you will have some neat scripts in your toolbox for the future.
_________________
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 |
|
|
| mca |
| Posted: Mon Aug 29, 2016 8:59 am Post subject: |
|
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
I reassigned the port and enabled the listener to "true" and restarted the integration node. It worked.
Thank you so much for your help in this issue. |
|
| Back to top |
|
|
|
|
