Hi
Thanks for the reply.
Don't you see this as a drawback with the soap UI? In the operating systems like Unix, one user might not have access on other user's space or it may not be secure to give such access.
Definitely I do not want to go with non recommended option.
However I am sure before installing soapUI pro, we were using core soapUI on the same machine and that soapUI use to update soapui-settings.xml file in the /opt folder. That time also we had moved default created file from /user into /opt directory. Similar action with soapUI pro is not working. It created a fresh file under /user space and updated global properties. It is not at all using the same file which is at /opt folder.
From your answer I can understand that soapui-settings.xml file is user based but the question remains how it was working for us with core version of the soapUI.
Thanks