Part 3 of Blog Series: An in depth look at enterprise SOA : Service Implementation in ABAP.
You can generate both client and server proxies in ABAP to send or receive messages, client proxies are generated from outbound interfaces whereas server proxies use inbound interfaces. In this narrated recording, we will take the ManageVendor service interface (wsdl) that was modeled previously in the Service Modeling with the ESR and create a server proxy object, add the business logic (implementation) for the 2 methods Create_Vendor and Search_Vendor, and finally create a runtime configuration for the proxy using http basic authentication along with a quick test using WS Navigator.
Although I didn’t show it in the recording, it’s easy to create multiple endpoints for the same service definition to allow for different runtime behaviors. Another nice feature that was not shown in the video is how easy it to regenerate the proxy if the modeled interface in the ESR were to change. The proxy interfaces and classes will be overwritten but the implementing class will remain intact so you don’t lose the code that you wrote. The last step is to use transaction WSPUBLISH to publish our web service (service definition and endpoint) to the Services Registry. We’ll cover more about the Services Registry later in this series as well as consuming services in ABAP and Java. We’ll feature creating Java server proxy next in the series.