| Author |
Message
|
| mca |
 Posted: Tue Apr 23, 2013 7:25 am Post subject: Ports used by webservice flow |
 |
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
We are building infrastructure to our new WMB project, where the front end is Datapower.
There are 12 message flows deployed on 12 Execution Groups on MB which all use SOAP Input Node. Each web service (Message Flow) is listening on separate port # ranging from 7843-7854 defined on EG.
Now DP guys want us to limit the port #'s on WMB for their communication. To do this, which option is better from the below.
1. Configure one Port # at Broker level so that all Web service flows running on Multi-EG use the same port.
2. Have a kind of URI mapping at Broker level and when a request comes in, Broker does a look up, assign the port and invokes the respective web service flow.
I am not sure if the above can be done, but it was put on table and i want to know the better option for us. Thanks in advance. |
|
| Back to top |
|
 |
| mapa |
| Posted: Tue Apr 23, 2013 9:28 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
1. This is possible first in WMB8. You can then define and enable the "Broker-wide HTTP listener". (See infocenter for V
2. I would prefer using a HTTP proxy (that can do loadbalancing if you have multiple brokers, also an option for point 1)
You can in WMB7 make sure to bind a specific port for each EG so that you don't get them in random order between environments. (See Execution group http listener in Infocenter) |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Apr 23, 2013 9:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
In v8, you can also export the config of a broker in terms of SOAP and HTTP endpoints as either a plugin.conf for the was plugin IBM HTTP Server or for a plain Apache HTTP Server.
So you can just install a local Apache server on a broker machine or nearby and export the broker config any time you make significant deployments or changes, and all the DP urls just point to the Apache server URLs. |
|
| Back to top |
|
|
| mca |
| Posted: Tue Apr 23, 2013 10:04 am Post subject: |
|
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
| We are running WMB v8.0.0.2 |
|
| Back to top |
|
|
| mapa |
| Posted: Tue Apr 23, 2013 10:33 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Oh, neat, thanks for the tip.
| mqjeff wrote: |
In v8, you can also export the config of a broker in terms of SOAP and HTTP endpoints as either a plugin.conf for the was plugin IBM HTTP Server or for a plain Apache HTTP Server.
So you can just install a local Apache server on a broker machine or nearby and export the broker config any time you make significant deployments or changes, and all the DP urls just point to the Apache server URLs. |
|
|
| Back to top |
|
|
| mca |
| Posted: Wed May 01, 2013 7:13 am Post subject: |
|
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
We contacted IBM MB SME and he said since we are using SOAP nodes we cannot use one Broker wide listener and need separate EG listeners.
The second approach to consider is DP sending SOAP message to MB on one port and we put HTTP server (we prefer HTTP over apache as we use HTTP server in house) before MB and it does the routing to different EG adding the port # based on URL (webservice) it received.
Is this a good approach or will there be any overhead with this? If not best approach, we can ask the DP to communicate directly on different ports instead of one and we taking the extra effort. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 01, 2013 7:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
|
|
