Skip to Content

   lang=”en-us”>Web services are all the hype for some time now (or even behind the curve    already?) and as usual with relatively new technologies everybody thinks    something about them is cool, but nobody has seen real examples of what    makes them cool.

   lang=”en-us”>Let me tell you about two examples that convinced me about Web services.

   lang=”en-us”>In the early days of EJB there was a big issue with beans that once you    wrote one and wanted to test it you also had to write a client for this    bean. After some time, this is not a big issue but it still annoys you. So one of the things I had on my wishlist for SAP NetWeaver Developer    Studio definitely was a testing environment for EJB. For a long time the    guys were too busy to talk about this, and then my solution appeared    from a direction I didn’t expect it.

   lang=”en-us”>The new Web services environment emerged and with it the testing environment    for Web services. Let me show this as a step by step description, so you can    come back when you want to try it:


  1.      lang=”en-us”>Start the Web Service Navigator view from menu Window/Show      View/Other-> Web Services-> Web Service Navigator   

  3.      lang=”en-us”>Select your Web service from the tree and double-click it.       

  5.      lang=”en-us”>You just call the Web service test provided at the description page.   

  7.      lang=”en-us”>Enter appropriate parameters and submit.   

  9.      lang=”en-us”>Check the feedback.   

   lang=”en-us”>I immediately realized that this was all I wanted. Knowing that making a Web    service from an EJB invokes a three step wizard, this is the exact    testing environment I was searching for. (A drawback is that Web services    cannot handle non-serializable results) 

   lang=”en-us”>A second example is what happened during development of SAP    NetWeaver Developer Studio. There was a lot of  ideas where Web Dynpros    could connect and you could see this in the model wizard of Web Dynpro    in the beginning, where it is possible to choose the kind of proxy you    want to generate. In fact the number grew for quite a while, but at a    certain point last year, suddenly the trend turned around and the    number of options decreased. 

   lang=”en-us”>What had happened? Once you start working you will    find out yourself: If you like to call BAPIs from the ABAP world, this is a    nice option. To be on the secure side, unfortunately you have to set up the    system landscape directory – something we ignored for the early versions.    Because of that, more and more people are switching over to use Web services    that the ABAP world provides.

   lang=”en-us”>Of course, this is another layer between two pieces of    software, but how many  times do Web services give you additional productivity at virtually no cost? Now,    that is an improvement isn’t it?

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply