• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

a good scenario for SOAP?

 
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Ranch Hand
Posts: 95
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
timothy zimmerman
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks, I must admit the project seemed a bit over my head so I declined to pursue it but I am still interested in understanding the solution for my own benefit. I think your second approach is the more likely solution. They want to have samll units of the PB app available as web services. I think ultimately they want to move away from PB altogether.
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Also, you need to be careful about what "web enabling" means. Most people use that term to refer to "putting a browser front-end on somthing". SOAP is not useful for that. SOAP is about application-to-application communication over the internet. What makes it different from other application-to-application technologies (like CORBA, DCOM or RMI) is that it's based on XML (since XML has the advantage of being easily readable and parseable), and HTTP (and other protocols like SMTP that all have the advantage of working over the internet through firewalls, etc.)
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
Ranch Hand
Posts: 349
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think "web-enabling" not necessarily have to be related to a browser. It can also be any B2B system that uses the Internet to exchange data.
Faisal
 
Ranch Hand
Posts: 106
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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?


the architecture looks like this:
Web Tier -> Powerbuilder Wrapping -> PowerBuilder Objects -> Legacy
I guess Web Tier is developped in Java Language (JSP/Servlets/EJB). Powerbuilder Wrapping Tier is a layer to make adapter
SOAP is only the protocol between the WebTier and Powerbuilder Wrapping. IMHO, I don't think SOAP will be an improvement. it is usefull if U want to "externalize" the WebTier, what i mean is that if the company wants to provide webservices on their PowerBuilder layer (a sort of wrapping). If I were U, I will just use the standard J2EE technologies (the wrapping will be a EJB layer for example)
... more simple, SOAP is useless for the initial requirement.
Regards
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic