As far as I know it’s done the same way as it’s done in any other web container, I.e. by specifying the web app context and the rest URL. The context is by default the same as the war file name, if I’m not mistaken.
I did tried accessing the web application the same way, but ended up in a page “Not Found” error.
For example, the context of the webApp is MyWebApp which has a jsp page called home.jsp.
I can see the .war file present in the MWS / Portlet-WebApplications. But when i access it like http://(actual Url):8686/MyWebApp/home.jsp" , we are getting the above error.
This web app has been tested working fine in Tomcat and not sure if the web.xml needs any specific changes for MWS.
That’s weird, I did access a usual server that way (not a Jsp page though). Maybe some necessary mapping is not present in web.xml? Or could it be that some Mws wide access rule gets active? In my case, I didn’t have to define any special rules to make the application accessible. Sorry for not being able to help more.