Yes, port and webapp path are configurable. You can either manipulate
the parameters in the wps_config.xml (attributes of the Server-element,
quite at the bottom of the file) or set them via the Admin Console.
Yes, my port and path are configured correctly in wps_geotools_config.xml and the process executes correctly (from server logs). The problem is with the schema that is generated. I am using the client library in a workflow engine, which is then deployed on a server (same machine to the wps, but different application server and obviously a different port). The client library creates WPS requests according to the workflow, however when I try and parse a result on the workflow side, I get the file not found error.
It is as if the schema is being put in the /schema directory of the workflow engine, but the client libraries are looking for the generated schema in the /wps/schema directory.
I think I found the reason for this issue. The folder to store the schemas is located via the WPSConfig class of the 52n-wps-commons library. This lib is needed for the client api as well, i.e. the library will exist in the WEB-INF/lib folder of the workflow engine. Somehow the path of this WPSConfig class must be used to store the schemas. I am not sure how this could happen though, as you said you are using a different application server for the WPS. I will try to conduct some experiments to prove this behavior.
Unfortunately, I have come to a point where this work around will not work.
I am now using a reverse proxy so that the WPS is served through apache (mainly for security reasons). This in turn causes a problem with the schema folder, when I execute a client request, the client seems to be looking for the schemas folder at:
when I need it to look for
Where is this path defined please? I have changed wps_config.xml to port 80: