Why web services ?
Web services promise to overcome the limitations of existing technologies (such as RFCs) for the following reasons:
- Web services are defined independently of programming platforms and languages.
- Web service definitions are expressed in XML syntax, making it easy to develop and offer the tools for defining services based on XML.
- Web services, as their name suggests, can easily be executed over the Internet, making it possible to establish distributed business scenarios in an ad hoc fashion.
- Web services can be developed in any programming language, including Java, ABAP, or C#.
Web services can be published in a common directory based on the UDDI (Universal Description, Discovery, and Integration) standard
Technical aspect for Web Service Implementation
Basic steps are:
- Modeling the web service interface (Signature).
- Define web service (functionality).
Two approaches are:
a) Using RFCs and b) Using ESR
- Using RFCs:
- Modeling: On ECC, using transactions SE37/SE80 create a RFC Enabled function module and specify its import, export, Exceptions and table parameters.
- Defining: Form the necessary functionality in source code.
- Publish: 1 > Convert you RFC into web service as follows:
- While being in navigator (SE80) , right click on Function module entry and click on create – web service
- In the opened wizard , go on specifying the following details:
- Create Service: specify web service name
- Choose Endpoint : specify function module name
- Configure Service : specify profile and tick on deploy
- Then using the transaction code ‘wspublish’, publish the web service which will make it available in Service registry to be used by consumer.
- Using ESR:
- Modeling: In the Enterprise service Repository (ESR) define the interface for web service. Go to transaction se80 and click on Enterprise service browser, activate the generated proxy for interface.
- Defining: Select the method from the interface and write code inside.
- Publish: Web service can be published in Service Registry using wspublish.
Web services Standards:
- The SAP Web Application Server implements the following basic Web services standards: extensible Markup Language (XML),
- Simple Object Access Protocol (SOAP),
- Web Service Definition Language (WSDL),
- Universal Description, Discovery, and Integration (UDDI).
- The ABAP Workbench offers a powerful environment where one can publish, search for, and call Web services.
In case you need assistance in SAP Enterprise Services, please contact us. Please send us your questions, comments or assistance request, and our team would be glad to assist you.
Please send us your questions, comments or assistance, and our team would be glad to assist you.
By Nikhil Joshi. (on behalf of SAP Consulting Team)
SAP :: Streamlined
We offer variety of services including SAP ECC ,SAP HR,SAP BW,SAP CRM, SAP SCM,SAP BPM, Business Objects, SAP ABAP Development, SAP BASIS and SAP NetWeaver consulting. We have expertise in providing implementation,development, SAP Migration and SAP support services to SAP customers across diverse industries at a global level.
Have a question on SAP? Write to our SAP Architect.
(We promise a no-obligation consulting reply)