The only difference between the classic OpenEdge AppServer and PAS for OpenEdge regarding the URLs used to connect to and access OpenEdge REST and Data Object Services, is allowing access to the default ROOT ABL web application on PAS for OpenEdge.

For example, a URL to access an OpenEdge REST web service for the classic AppServer using the OE Web Server might be the following:

http://host:port/CustomerMaint/rest/CustomerSvc/CustConnect

After migrating the same ABL code to the asbroker1WebAppl.war ABL web application on a PAS for OpenEdge instance, you would use this URL:

http://host:port/asbroker1WebAppl/rest/CustomerSvc/CustConnect
Note: This example uses the same WAR file name as in the previous example of a classic AIA URL migration (see Migrate AIA URLs to use the APSV transport), instead of using a file name that might match the original REST web application for the classic AppServer on the OE Web Server (CustomerMaint.war). This is to illustrate that all three web connection transports can be supported in a single ABL web application on PAS for OpenEdge as long as they can all access the same server ABL code base.

You could also rename the ABL web application to the file name of the original REST web application for the classic AppServer (CustomerMaint.war), and use a URL almost identical to the original (shown in the previous example), or after migrating the ABL code to the default ROOT ABL web application, you could use this URL:

http://host:port/rest/CustomerSvc/CustConnect

Note that OpenEdge ABL does not have a native REST CONNECT( ) method at this time. However, you can test a REST connection through a browser.

For more information about creating and connecting to both REST web services and Data Object Services, see the topics on these services in Develop ABL Services.