| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Maintaining a generic webservice provider message flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| PEPERO |
 Posted: Sun Jan 27, 2019 2:24 am Post subject: Maintaining a generic webservice provider message flow |
 |
|
Disciple
Joined: 30 May 2011
Posts: 177
|
Hi all;
We've designed and implemented a generic web service provider message flow to represent about 100 web services (a webservice with about 100 different operations) each of which has different input/output message models in the message set project.
We are using version 7.0.0.1 of WMB hosted on a Zseries IBM Mainframe machine and there are some internal & external stackholders to our system for these webservices for which they could request a different subset of these operations. The solution that we have used to isolate the required operations for each stackholder is to make a bar file with the desired message models and since we use a generic message flow project , we have to deploy each built bar file onto an isolated execution group.
I want to know what would be the best practice to substitute this expensive solution. I thought to make a pattern or either using the namespaces but in my oponion those solutions could increase our maintaining costs. |
|
| Back to top |
|
 |
| timber |
| Posted: Sun Jan 27, 2019 1:25 pm Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
So you have
- one generic web service
- 100 different operations
- N clients, each of which is allowed to access a subset M of the operations
That sounds very much like an API management problem. Have you considered using API Connect? You could deploy one copy of the web service (or perhaps multiple web services...maybe all 100 in a single WS is not ideal?). API connect would manage the sign-up process, authenticate and authorize clients, and monitor how many calls each client makes. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 28, 2019 6:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| timber wrote: |
| That sounds very much like an API management problem. Have you considered using API Connect? You could deploy one copy of the web service (or perhaps multiple web services...maybe all 100 in a single WS is not ideal?). API connect would manage the sign-up process, authenticate and authorize clients, and monitor how many calls each client makes. |
It's also likely to be cheaper, more agile and easier to administer than a solution hosted on z/OS.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PEPERO |
| Posted: Mon Jan 28, 2019 6:54 am Post subject: |
|
|
Disciple
Joined: 30 May 2011
Posts: 177
|
| thanks for the given solution |
|
| 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
|
|
|
|
