| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Port 7800 with HTTPInput node in V6.1 |
View previous topic :: View next topic |
| Author |
Message
|
| HonestBroker |
 Posted: Thu Sep 06, 2012 3:02 am Post subject: Port 7800 with HTTPInput node in V6.1 |
 |
|
Newbie
Joined: 30 Mar 2011
Posts: 8
|
In WMB v6.1, is it possible to force a HTTPInput node to use the embedded Execution Group HTTP Connector Port - 7800, while still retaining a Broker-wide HTTP Listener on 7080?
I have an Execution Group with SOAPInput and HTTPInput nodes. The SOAPInput nodes are working on 7800, but the HTTPInput node seems to work only when I target 7080 from the client (soapUI).
The V6.1 HTTPInput Node documentation at: http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fac67173_.htm
suggests that you can use the EG embedded listener “If you choose to handle HTTP messages by using the listener that is embedded in the execution group, which is also used for SOAP nodes . . .”. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Sep 06, 2012 4:32 am Post subject: Re: Port 7800 with HTTPInput node in V6.1 |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| HonestBroker wrote: |
| In WMB v6.1, is it possible to force a HTTPInput node to use the embedded Execution Group HTTP Connector Port - 7800, while still retaining a Broker-wide HTTP Listener on 7080? |
No.
| HonestBroker wrote: |
| I have an Execution Group with SOAPInput and HTTPInput nodes. The SOAPInput nodes are working on 7800, but the HTTPInput node seems to work only when I target 7080 from the client (soapUI). |
Yes, that's the way it works. SOAP nodes use the EG level HTTP listener, and HTTP nodes use the Broker level HTTP listener.
I do not think that link points where you meant to point it.
| HonestBroker wrote: |
| suggests that you can use the EG embedded listener “If you choose to handle HTTP messages by using the listener that is embedded in the execution group, which is also used for SOAP nodes . . .”. |
I suspect this is a documentation error. If it were possible to do this in v6.1, the v6.1 documentation would mention the httpNodesUseEmbeddedListener property, which I believe is only valid and active at v7.0.0.0 and later. |
|
| Back to top |
|
|
| HonestBroker |
| Posted: Thu Sep 06, 2012 5:44 am Post subject: |
|
|
Newbie
Joined: 30 Mar 2011
Posts: 8
|
| Thank you for that confirmation and prompt, concise response! |
|
| Back to top |
|
|
| NealM |
| Posted: Wed Sep 12, 2012 2:22 pm Post subject: |
|
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
| HonestBroker, I have a feeling that you somehow got crossed up and got into the info center for the v8.0.0.1 Broker, where you for the first time can take your pick of the broker-wide HTTP Listener or the EG level listener for either SOAP or HTTP nodes. But as said above, not so for v6.1 |
|
| 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
|
|
|
|
