Deploying a REST application using Pacific Application Server in OpenEdge 11.6 - Forum - OpenEdge Deployment - Progress Community

Deploying a REST application using Pacific Application Server in OpenEdge 11.6


Deploying a REST application using Pacific Application Server in OpenEdge 11.6

This question is not answered


in OpenEdge 11.6

I am trying to deploy an ABL application (NewApplication )  using the Pacific Application Server  in Web Applications. I am able to deploy it(browsing the file and uploading it via the browser), it appears in the Web Applications after deploying it, however when clicking on the list of ABL applications i only see ROOT, and the ROOT doesn't have my paar file, it's the default generated application. 

I would like to know how to i make my application the default? Does it have to do with paths? or is there a command for me to run to send my NewApplication into the ROOT and merge etc?

All Replies
  • Hi,
    Just a quick check, have you started the server after deploying WebApplication?
    AFAIK, When you start the server then only newly deployed webapps will be loaded into the server context and then they will be displayed under list of Web Applications.
  • Yes, i started it,

    for example, if in the beginning i create a new Pacific application server called oepas1, then that appears on the list of ABL applications, however when i click on it i see ROOT, but if before i click on the oepas1 i click on Web Applications then i see manager, oemanager, ROOT, and NewApplication.

    i need it to show NewApplication when i click oepas1 so that i can configure it, enable rest, and add database parameters etc.

  • The “NewApplication” is an ABL  application (within the PAS instance). I don’t believe there’s any way to create a new ABL application from PDSOE (you need to use  tcman deploy with the optional last parameter).
    To see the options for tcman, in proenv type “pasman help deploy” or, in the instance’s bin directory, type “tcman help deploy”. They boths how the same info.
  • 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.
  • To add to what Dave says …
    An ABL Web Application can have
    One or more ABL Services. These ABL services are represented by a PAAR file (rest transport), WSM file (SOAP transport) or a Web handler (WEB transport).