Solved: wrapping web service without change of endpoint an... - Page 2

sjm2000 · 08-08-2016 10:17 PM

Dear All,

Currently we expose our webservice which connects to backend database like the diagram below

We would like to change the architecture with apigee Edge on premise like below .

The use cause is for we use apigee on premise for this particular scenario for analytics mostly.

Secondly main reason is i do not want all the consumers to change the end point/wsdl path, for accessing the webservice.

However please note we do not have Baas installed and web service might require to work as-is for database connections.

Is it feasible? 🙂

Regards

Report Inappropriate Content

Hello @Sujith Mathew,

Couple of questions:

1. How the DB is exposed ?

2. How the WebService would talk to the Apigee Edge ?

By looking at the proposed architecture, I feel it is possible to develop an Apigee Proxy which would basically talk with the northbound WebService and integrate with the SoundBound DB.

But to do so, we need to understand in detail the answer of two questions I raised. If we know how the Northbound interface would look like, what would be the security considerations, quota, throttling, cache etc, then we can design the NorthBound part of the API Proxy.

Additionally, if we know how the DB is exposed for the API to consume, then we can try to set this DB node as an target server (provided it is possible, where in the DB is also exposing a well defined format to interact with, a lister IP and port and a DB service, which would work on the request and send a response).

In this way, we should be able to abstract the DB from the Web Service.

Hope this helps.!

View solution in original post

wrapping web service without change of endpoint and wsdl