This blog will help you understand how as a developer or consumer of an enterprise service you can actually monitor the performance of the service calls and find out where the real bottlenecks are - whether they are in the connection, or in database calls or in the client which is consuming the service.
The steps are : to get the WSDL file of the web service with the endpoint and use it in the consumption client which is a simple SOAP UI 2.0 client used in this case. This has been an idea shared to me by my colleague Peter McNulty whose blogs you have already seen as part of the blog series. You are free to use any tools of your choice. The SOAP UI2.0 client is used to simulate load tests of service ZDEMOBLOG which executes the function implementation ZGETAIRLINEINFO in the ABAP backend. We will then go deep into all layers of the service execution to show how you can monitor the bottlenecks of the service execution if any.
