M
Michael Jacobs
Guest
Paul, You are being mislead by the information contained in the server monitor's 'REST service URL'. It confused me also. The URL field's value will not physically exist in the web server ( at least not in any of my REST projects ) Like Irfan said, the 'oerm' web application is a remote management agent (displayed as 'restmgr1') and does not contain any of the REST services you create in your project. When you create a REST service in your project and the development studio publishes your service (using 'restmg1') it does so by creating a new web application and deploying it to the web server using the REST service interface's name. From the screen shot I see the name of your REST service interface is 'testRestService', which will produce and deploy a web application named 'testRestServcie'. The URL to access your new REST service web application would be: http://localhost:8980/testRestService I generally do an initial manual test to see if the web application ended up where I would expect it and will it start and run: a) do a GET on 'http://localhost:8980/testRestService and see if it will return anything b) do a GET on ''http://localhost:8980/testRestService/rest/' and see if anything is returned You want to get a 200 response from b) before proceeding further. Do note that b) can return success, but does not mean that your REST web application is actually able to connect to the AppServer. For AppServer connection testing you have to access one of your web application's resources that is mapped to a class/procedure in the AppServer. Try that and see if you get further.
Continue reading...
Continue reading...