The context path can be changed using the contexPath field in your SOAP binding configuration, e.g.
Based on the URLs you posted, you are good with the context path of "switchyard-esbperformance". The next part of the path is based on the service name, which is taken from the composite service name in your switchyard.xml at
Using the quickstart example I posted above, I could change the last part of the path from OrderService to DirectProxy by using a different name for the composite service:
<service name="DirectProxy" promote="OrderService">
Hold the phones! Ignore what I said about the composite service name. It's the service name from the WSDL you have configured via the wsdl element of the SOAP binding. I just double checked that with my local install.
Do you work for AdroitLogic by any chance? We offered to help out with a much earlier version of this work, when it was being driven within WSO2, but never received a response.
We then started working within the SPEC SOA performance team, of which I am currently chair, to develop a more comprehensive performance suite. Would AdroitLogic be interested in joining the SPEC SOA work? If so have someone drop me an email/pm and I can work with them on this.
No I am not a AdroitLogic employee.. But I think they are active, because in November 2012 I had a short mail communication with Asankha Perera.. concerning one issue.. Maybe try to contact him again.. Hope It will help.