Try OpenEdge Now
skip to main content
Application Migration and Development Guide
Migrating AppServer and WebSpeed Applications : ABL application code migration : Migrating client connections to PAS for OpenEdge : Migrating REST URLs
Migrating REST URLs
There is no real 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, except to allow access to the default ROOT OE 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:
After migrating the same ABL code to the asbroker1WebAppl.war OE ABL Web application on a PAS for OpenEdge instance, you would use this URL:
Note: This example uses the same WAR file name as in the previous example of a classic AIA URL migration (see Migrating 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 OE ABL Web application on PAS for OpenEdge as long as they can all ultimately access the same server ABL code base.
You could also rename the OE 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 above), or after migrating the ABL code to the default ROOT OE ABL Web application, you could use this URL:
Note that OpenEdge ABL has no native REST CONNECT( ) method at this time. However, you can test a REST connection through a browser.
For more information on creating and connecting to both REST Web services and Data Object Services, see the sections on these services in OpenEdge Development: Web Services.