You can use the Servers view to view the current status of an PAS for OpenEdge instance and its associated ABL REST services.

The Servers view allows you to manage the PAS for OpenEdge instances. This view displays a list of all your PAS for OpenEdge instances and ABL REST services that are associated with that PAS for OpenEdge instance.

Access the Servers view by selecting Window > Show View > Servers from the main menu.

The following table lists the possible statuses:

Status Description
[Stopped] The PAS for OpenEdge instance is stopped and not connected to the PAS for OpenEdge container. You cannot deploy ABL REST service and ABL REST Web applications to the PAS for OpenEdge container.
Note: Select Start on an PAS for OpenEdge instance context menu to start the PAS for OpenEdge instance.
[Starting] The PAS for OpenEdge instance is in the process of connecting to the PAS for OpenEdge and is beginning the server process.
[Started] The PAS for OpenEdge instance is successfully connected to the PAS for OpenEdge. Both the PAS for OpenEdge instance and PAS for OpenEdge are ready to deploy services.
[Started, Synchronized] Both the PAS for OpenEdge instance and its associated ABL REST services are in sync. ABL REST services are copied to a location on the webapps folder. For example, in case of PAS for OpenEdge, the ABL REST services are published to the webapps folder in your OpenEdge installation directory, $WRK/<pas_instance>/webapps. A separate .WAR file is created for each deployed ABL REST service.
[Stopped, Synchronized] The PAS for OpenEdge server instance is in stop state. Both the PAS for OpenEdge instance and its associated ABL REST services are in sync.
[Started, Republish] Either the server or the associated services, or both have changed. When the server is restarted, the modified services are also republished.
Note: The status appears as Republish beside the modified ABL REST service. Select Republish on the PAS for OpenEdge instance context menu to republish the ABL REST service.
[Synchronized] [Not Published] Both the PAS for OpenEdge instance and its associated ABL REST services are in sync. The ABL REST service is not deployed to the PAS for OpenEdge container and disabled for client access.
[Synchronized] [Published] Both the PAS for OpenEdge instance and its associated ABL REST services are in sync. The ABL REST service is deployed to the PAS for OpenEdge container and enabled for client access.
Note: When an ABL REST service is deployed to a PAS for OpenEdge container, the deployed ABL REST service is enabled by default and will be available for client access.
[Synchronized] [PAS for OpenEdge server is not started] Both the PAS for OpenEdge instance and its associated ABL REST services are in sync. But, the PAS for OpenEdge instance is not started. Right-click the PAS for OpenEdge instance, and then select Start on the context menu to start the PAS for OpenEdge server.
[Republish] Indicates that a ABL REST service is modified and must be re-deployed to the PAS for OpenEdge container.
[Not Published] Indicates that the PAS for OpenEdge instance is started but the Publish changes immediately check box was not selected on the Provide ABL Web App deploy details page while creating the ABL REST project. Select Publish on the PAS for OpenEdge context menu to publish the ABL REST services having the status as Not Published.
Note: Before you publish or republish the ABL REST services to the PAS for OpenEdge container, ensure that the selected PAS for OpenEdge instance is started. You can start or stop the PAS for OpenEdge instance from the Servers view using the Start and Stop option on the PAS for OpenEdge instance context menu or from the Servers view toolbar.