I was not very familiar with WSO2 Carbon at that time. I had just started playing with it. WSO2 Web Services Application Server (WSAS) looked more than attractive to me to play with.
In the Admin Console of WSAS, we have Add Axis2 Service option in the left hand side panel. I uploaded our aar using that Add option. A success message appeared as expected. Then I clicked the List Menu for deployed services. There I clicked Try this service option for the MsgBoxService. I was taken to the Try the MsgBoxService service. Wonderful! It has a nice GUI with textboxes to input the values. Getting the output instantly, I was walking through WSAS to see more. Found something under the monitor menu. SOAP Tracer!!! I configured the Configuration Status to ON. A warning says “Tracing will have a performance hit. Use with caution.” Who cares? I will not overuse this functionality however. Then I went back to try the service. After trying all the four operations, I came back to the SOAP Tracer. Wow… It has all! SOAP messages for both the request and the response. Then it took me just minutes to copy-paste those SOAP messages for the four operation requests, into the respective SOAP/XML-RPC Request of Jmeter.
The conclusion of the performance analysis was not much difficult after that. Just adding a variable in place of the input value, a counter to have about 1000 users each user as a thread, timer, Loop Controller to send 10 msg for each user’s msgbox, and finally Graph results to see the performance of each operation visually.





0 comments:
Post a Comment