You can publish an ABL Service(s) using the Servers view in your OpenEdge Server perspective. To publish an ABL Service, you must create a server instance, associate the ABL Service with the defined server, and then publish the associated ABL Service to the PAS for OpenEdge container shipped with Progress OpenEdge.

When you install Progress Developer Studio for OpenEdge, PAS for OpenEdge server is installed and configured with Progress OpenEdge. Before you publish to the PAS for OpenEdge server, you must start it. For more information, see Start and stopping PAS for OpenEdge server.

Note: The ABL Service are published as separate .WAR files when you deploy them using the Publish option from the Servers view. If you want to deploy the ABL Services as a single WAR file, you must export them as a .WAR file. For more information, see the Export an ABL Web Application.

To publish a ABL Service:

  1. From the Servers view, select the relevant server instance of the ABL Service that you want to publish.
  2. Do one of the following:
    • Select Publish on the server instance's context menu.
    • Select a server instance, and then click the Publish to the server icon on the Servers view toolbar.

This publishes the selected ABL Services to the PAS for OpenEdge container. For a published ABL Service, a separate WAR file is generated and deployed to the PAS for OpenEdge container. For example, an ABL Service published to the PAS for OpenEdge instance, that is shipped with OpenEdge, a WAR file with the selected ABL Service name is created in your OpenEdge installation directory, $WRK/<pas_instance>/webapps. A separate WAR file is created for each deployed ABL Service.

You can view the server’s status in the Servers view beside the published ABL Service’s node.

After deploying the ABL 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.