| Author |
Message
|
| paustin_ours |
 Posted: Thu Aug 11, 2016 1:09 pm Post subject: http listener port |
 |
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
on v10.0.0.5 i just deployed a flow to an execution group. the integration service wsdl points to 7800 as the port number but the execution group has assigned 7801 to its listener. i dont have embedded listeners turned on.
According to the inforcenter, my first http flow deployed on EG1 gets assigned 7800, second flow deployed to EG 2 gets assigned 7801
when i test the integration service and send a message from toolkit how it is working? how does the http call go to 7801 instead of 7800 like it is mentioned in the wsdl?
when i try from SOAPUI, i had to point to 7801 specifically for it to work
please enlighten me. thanks in advance
http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bc43700_.htm |
|
| Back to top |
|
 |
| paustin_ours |
| Posted: Thu Aug 11, 2016 1:17 pm Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
| i guess when i turn on recording and point to EG2, it knows to send the request to 7801 instead of 7800. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 11, 2016 10:38 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
From memory, the PORT as specified in the WSDL is ignored by broker. The actual specific port settings for the HTTPListeners (broker or EG) take precidence.
This is IMHO the right way to do it.
The configuration of the Broker itself should be the master.
_________________
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 |
|
|
| paustin_ours |
| Posted: Fri Aug 12, 2016 3:59 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
but what if you give the wsdl to a client and they use the port in the wsdl and the broker flow is deployed to an EG and it assigns a different port to it?
how me as a client know to connect to the right port to send me requests. hopefully i am not missing something quite obvious. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 12, 2016 4:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The provider always gives you the URL.
If it happens to match the URL in the WSDL, great.
If it doesn't, they still tell you the right one.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Aug 12, 2016 4:20 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
The provider always gives you the URL.
If it happens to match the URL in the WSDL, great.
If it doesn't, they still tell you the right one. |
The provicer will often give you TWO URL's. One for testing and one for Prod. The same WSDL would be used for both. The URL they give you includes the Port. You might have the same IP/FQDN bit a different port for the two systems. It all depends upon how the provider sets things up.
I don't see what the issue is really.
Using the PORT to override the actual broker would be a real PITA. Imagine having to test every version of the WSDL because you would have one for Dev, one for Test, one for System Test, One for Pre Prod and one for Prod rather than one WSDL and you let the configuration of the broker control the rest.
_________________
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 |
|
|
|
|
