Multi-db Web Services

J

jozef

New Member
Hi. Just started working with Web Services / proxygen and looking at going ahead with it.

Thing is, we have 31 database on 8 different servers. We're deploying a web service that will look at specific client information in each db. The web service we have developed works fine.

What is the easiest way to deploy it across the 31 db's? I don't to have to run proxygen 31 times for each appserver to produce a Web Service for each db!

Is there some way I can create a single web service and dynamically deploy it against each db?

Does this explanation make sense? I know what I want to say but aren't sure if it's coming out that way!!!
 
You don't deploy a web services against a database. Full stop. You deploy the web service against an AppServer.

Do you have one particular AppServer dedicated to one particular database or do you have one AppServer that needs to connect to different databases depending on the request context?

Heavy Regards, RealHeavyDude.
 
You can override the name of the AppServer instance as well as other parameters after you have deployed the web service. Just right click on the deployed Web Service and click properties.

Heavy Regards, RealHeavyDude.
 
Thanks RHD. Had a 4 day break and just returned to the salt mines today, hence the lack of response.

When I r-click on the deployed web service, all I get is:

EDDashboard.jpg
 
But anyway, is it possible to use a single webservice deployment to connect to multiple appservers (each of which serves a single database) on the same server? Or do I have to proxygen a webservice for each appserver?
 
You need a particular AppServer as single point of entry. Everything beyond that is on you. You could, for example, have a logic on the entry point AppServer that distributes the request to different working AppServer based on the nature or parameters of the request ...

Heavy Regards, RealHeavyDude
 
Cheers. Slowly wading through the learning process. I figure the easiest way is to do what you suggested. Deploy the same web service n times and then change the properties to point at the respective appserver.
 
You're welcome! If you need that flexibility in one entry point Web Service always running on the same AppServer instance then you need to take that into account when you design the Web Service and your environment accordingly. Trying to achieve something like that from the outside in needs more administrative work afterwards.

Heavy Regards, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top