Author |
Message
|
mpong |
Posted: Fri Sep 02, 2016 2:10 am Post subject: HTTPInput Node on IIB 9 and 10 |
|
|
Disciple
Joined: 22 Jan 2010 Posts: 164
|
I have a flow which starts with HTTPInput node. After deploying the flow in IIB V 9.0.0.4 in local machine I am able to call the service from the local browser.
http://localhost:7080/Test
Similar flow is deployed on IIB 10.0.0.3 in another machine but I am unable to call.
http://localhost:7080/Test
[quote]This site can’t be reached
localhost refused to connect.
Search Google for localhost 7080 Account
ERR_CONNECTION_REFUSED[/quote]
Please suggest. |
|
Back to top |
|
 |
adubya |
Posted: Fri Sep 02, 2016 3:23 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011 Posts: 377 Location: GU12, UK
|
Do you have an MQ queue manager associated with your IIB10 setup ?
IIB10 is the first version of broker which doesn't require MQ as a prerequisite but certain IIB capability does require an associated MQ queue manager.
The broker wide HTTP listener (which I'm assuming you're using as it's default port is 7080) is such a capability and does require a queue manager to operate.
From the Infocenter
Quote: |
The integration node listener requires access to system queues on the queue manager specified on the integration node, so you must install WebSphere® MQ Server if you want to use an integration node listener. However, if you use HTTP nodes or SOAP nodes with the integration server embedded listener, WebSphere MQ is not required. |
Integration node listener == broker wide listener
Integration server embedded listener == an execution group listener
So MQ isn't a prereq if you're using execution group listeners. _________________ Independent Middleware Consultant
andy@knownentity.com |
|
Back to top |
|
 |
vishBroker |
Posted: Fri Sep 02, 2016 8:16 am Post subject: Re: HTTPInput Node on IIB 9 and 10 |
|
|
Centurion
Joined: 08 Dec 2010 Posts: 135
|
mpong wrote: |
I have a flow which starts with HTTPInput node. After deploying the flow in IIB V 9.0.0.4 in local machine I am able to call the service from the local browser.
http://localhost:7080/Test
Similar flow is deployed on IIB 10.0.0.3 in another machine but I am unable to call.
http://localhost:7080/Test
Quote: |
This site can’t be reached
localhost refused to connect.
Search Google for localhost 7080 Account
ERR_CONNECTION_REFUSED |
Please suggest. |
Are your IIB v9 and IIBv10 on the same box?
Then how would you know - which one is listening onto 7080 port?
Anyhow - if you are getting the error - check HTTP response code..it should be 5xx something.
Run mqsireportproperties IIBNodeName -e EGName -o HTTPConnector -r => This will tell you the ports the EG is running on and what is the URI.
You might be hitting the wrong URI. |
|
Back to top |
|
 |
Vitor |
Posted: Fri Sep 02, 2016 8:34 am Post subject: Re: HTTPInput Node on IIB 9 and 10 |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
vishBroker wrote: |
Are your IIB v9 and IIBv10 on the same box?
Then how would you know - which one is listening onto 7080 port? |
mpong wrote: |
Similar flow is deployed on IIB 10.0.0.3 in another machine but I am unable to call. |
_________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
vishBroker |
Posted: Fri Sep 02, 2016 8:41 am Post subject: Re: HTTPInput Node on IIB 9 and 10 |
|
|
Centurion
Joined: 08 Dec 2010 Posts: 135
|
Vitor wrote: |
vishBroker wrote: |
Are your IIB v9 and IIBv10 on the same box?
Then how would you know - which one is listening onto 7080 port? |
mpong wrote: |
Similar flow is deployed on IIB 10.0.0.3 in another machine but I am unable to call. |
|
Oops !! Not a good catch this time.
javascript:emoticon(' ')
My bad!! |
|
Back to top |
|
 |
|