Try OpenEdge Now
skip to main content
Online Help
Introducing OpenEdge REST : Tasks : Deploying ABL REST Web applications : Publishing a REST service
 
Publishing a REST service
You can publish a REST service using the Servers view in your OpenEdge Server perspective. To publish a REST service, create a server instance, associate the REST service to the defined server, and then publish the REST service to the Apache Tomcat Java container. See Associating REST services with an OE Web Server.
Note: After you republish a REST service, the service is enabled by default and becomes available for client requests.
To publish a REST service:
From the Servers view, do one of the following:
*Right-click a server instance, and then select Publish on the context menu.
*Select a server instance, and then click Publish to the server icon on the Servers view toolbar.
This publishes the REST service associated with the selected OE Web Server to the Apache Tomcat Java container. For the published REST Service, a REST Web application WAR file is generated and deployed to the Java container. For example, if you use the Apache tomcat to deploy a REST service, a WAR file with the REST service name is created under the OpenEdge installation directory, $DLC/servers/tomcat/webapps. A separate WAR file is created for each deployed REST service.
For more information about the REST Web application WAR file layout, see the Progress OpenEdge Application Server: Administration guide.
You can disable or enable a deployed REST service from OpenEdge Management and OpenEdge Explorer. For more information about enabling or disabling a REST Web application, see the Progress OpenEdge Management and OpenEdge Explorer: Configuration guide.
You can view the status of the server in the Servers view beside the published REST service. For more information, see Status of OE Web Server and REST service.
After deploying the REST service, if you modify the artifacts of a project related to the deployed service, the status of the respective artifact’s module changes to Republish. You must republish the server manually if you have not set it to republish automatically so that the deployed service reflects the changes.