If the idea is to just web enable the legacy "powerbuilder" app (b2c), then SOAP is not required , my initial thoughts would be to web enable powerbuilder - via powerbuilder 8.0 ( ? ) - for obvious cost reasons .
Secondly you can webservice enable the powerbuilder app if there is a need to partner with vendors or other partners who would utilize the services ( b2b - ecommerce scenario )
Depending on the business functionality present in the PB app, the decision needs to be taken as to , how viable it will be to webservice enable the app .If its the crux of biz app , then one idea would be to typically weservice enable PB using webservices toolkit provided by PB and expose them to be consumed by your
EJB running on an internal App server for instance , which would then expose the functionality to the world for performance ( machine and app perf related not SOAP / webserv reasons )
The beauty of this architectural
pattern is that your app server controls the webservices internal to your organization , lets say for instance you need to webservice enable a M$ app that is part of another branch or whatever , then your app server with J2ee components would work like a controller .
Hope this helps -
Originally posted by timothy zimmerman:
I was approached by a customer who had an existing legacy applictaion and wanted to take it and make it a 'web application'
Basically they wanted to take some business logic which existed in PowerBuilder objects and make that logic available via a web interface preferrably using java.
This seems like it might be just the type of thing you would ue SOAP for? I am slightly familiar with SOAP so I am not sure of the details or the exact pieces necessary to make this work though.
Some type of ORB I suppose for the PowerBuilder pieces and then an app server for the jave pieces?
Thanks
------------------
My ramblings @
http://javarecon.tripod.com