1. Web service navigator is being used for testing web services but a lot of people don’t use it’s full potential (yes, it seem to have some). In this short article I’d like to discuss about two very rarely but quite helpful functions of that tool. Imagine you’re doing a WS test for a typical PI scenario:
a) you’re created a WS in PI
b) you put the address of PI’s WS in the navigator which creates a callable input
c) you insert parameters and execute the scenario
if it works you’re happy and you can inform someone that it worked.
Now the question:
What happens if you want to store a test case of this execution ?
a) You can give someone the URL for the WSDL and send the parameters together with that – you need to do that for all of your WS calls
b) You can create a test case in wsnavigator for all of your tested web services and send the test case file (XML) to someone of append to documentation
Let’s have a look at the automated – second approach as it’s very easy and quick to do.
After you execute your scenario you just need to add it to the test scenario – “Add to test scenario” button and you should do it for all web services you want to test.
Next you need to do to the “Test scenario” tab and from there select “Editor” and export your scenario. It will be exported with all the parameters necessary for executing your WS call.
Once someone else would like to execute the scenario, it needs to be imported to wsnavigator again (in the Test scenario tab -> Editor – Import) and it can be executed. Once you try to execute it you will see that all parameters are already filled in and the WS can be retested very quickly.
The method mentioned above is the easiest way to store all test scripts in case you don’t have any alternative tool for testing web services.
2. What if we created a WS on a J2EE engine which does not have wsnavigator so we’d like to use wsnavigator of our local PI server for example? This can also be done and all you need to do is to populate a so called “white list”. You can do that in http://pihost:port/nwa/middleware-settings . From that link you need to select wsnavigator and put the host of the J2EE engine on which the web service is deployed and you can now access it from your local wsnavigator.
Those two tips are pretty simple but as per my experience not a lot of people are using the “full” potential of our simple tool – wsnavigator. Hope that this small SAP tool will now be even more widely used in PI WS scenarios as this is the tool that is available for everyone who’s working with PI (not like any other alternative SOAP testing tools from different vendors).