D
David Cleary
Guest
The overuse of some terms can be confusing, so here is how I like to describe it. A PASOE Instance can have One or more ABL applications An ABL Application can have One or more Web Applications derived from oeabl.war A PASOE instance must have a ROOT application. This ROOT application is an oeabl-based web application by default, but doesn’t have to be. You can undeploy ROOT, and deploy any valid web application in its place. A default PASOE Development Instance contains the following: An oeabl-based web application deployed as ROOT, with a default ABL application name of the instance The Tomcat Manager web application – not an ABL application The OEManager web application – not an ABL application The OEDebuger web application – not an ABL application For a production instance, all that will be there is an oeabl-based ROOT web application that has everything disabled by default. For deploying a REST application, you can choose to deploy the paar file to an existing web application like ROOT, or you can generate a PASOE web application from PDSOE that you can deploy outside of ROOT. If you go that route, you probably want to undeploy ROOT and deploy a web application that does what you require when a client hits you server with no path specified. This can be a login page, a redirect, or something else depending on what you require. Dave
Continue reading...
Continue reading...