How to publish an OpenEdge Web Service – an overview

In one of my previous article we talked about the accessing a non-progress web service from progress OpenEdge® ABL.

Refer to the article Accessing non Progress® Application via WebService (URL: ultirags.com/Accessing-non-Progress-Application…) for more information. During this webinar, few participant requested for a tutorial on the publishing an OpenEdge® web services.

This article describes how to publish an OpenEdge® Web Service. I had heard about AppServer® with the release of Progress® v8. But, I got an opportunity to work on AppServer® only with OpenEdge® 10 release!

In OpenEdge®, a Web service is usually an AppServer® application that is accessible to a client application through a Web server.

In OpenEdge®, you could:
• Create new Web services that you build as ABL (Advanced Business Language) applications and deploy on an AppServer®.
• Expose existing AppServer® applications as Web services.
• Create an interface to your Web services and deploy it on a Web server.
• Create the client-side applications that interact with your Web services.

OpenEdge® includes support for Web services that are based either on SOAP (Simple Object Access Protocol), or on REST (Representation State Transfer).

Click on the URL (ultirags.com/how-to-publish-an-openedge-web-ser…) to download document that describes Steps to publish your own Web Service in OpenEdge®.

A special note of thanks to SKIL (www.skilglobal.com) and PUG, India (www.pugindia.org) for providing me with an opportunity to deliver a webinar on this topic.

The document in this article is enough for someone to get started publishing OpenEdge® web services. However, I would make the recorded session of the webinar available soon. Thank you for reading and your patience.

Author(s):
Raghuraman Kadambi, PMP®
www.skilglobal.com
Copyrights and Trademarks:
• Progress®, AppServer® and OpenEdge® are registered marks of Progress Software Corporation, USA
• PMP® is registered mark of Project Management Institute, USA
• All other registered trademarks and copyright material referenced in this article belongs to their rightful owners.