Status of OE Web Server and REST service

You can use the Servers view to view the current status of an OE Web Server instance and its associated REST services.

The Servers view allows you to manage the OE Web Server instances. This view displays a list of all your OE Web Server instances and REST services that are associated with that OE Web Server 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 OE Web Server instance is stopped and not connected to the Apache Tomcat Java container. You cannot deploy REST service and REST Web applications to the Apache Tomcat Java container. Note: Select Start on an OE Web Server instance context menu to start the OE Web Server instance.
[Starting]	The OE Web Server instance is in the process of connecting to the Apache Tomcat and is beginning the server process.
[Started]	The OE Web Server instance is successfully connected to the Apache Tomcat. Both the OE Web Server instance and Apache Tomcat are ready to deploy services.
[Started, Synchronized]	Both the OE Web Server instance and its associated REST services are in sync. REST services are copied to a location on the Web applications folder. For example, in case of Apache Tomcat, the REST services are published to the Web applications folder in your OpenEdge installation directory, $DLC/servers/tomcat/webapps. A separate WAR file is created for each deployed REST service.
[Stopped, Synchronized]	The OE Web Server instance is in stop state. Both the OE Web Server instance and its associated 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 REST service. Select Republish on the OE Web Server instance context menu to republish the REST service.
[Synchronized] [Not Published]	Both the OE Web Server instance and its associated REST services are in sync. The REST service is not deployed to the Apache Tomcat Java container and disabled for client access.
[Synchronized] [Published]	Both the OE Web Server instance and its associated REST services are in sync. The REST service is deployed to the Apache Tomcat Java container and enabled for client access. Note: When a REST service is deployed to a Apache Tomcat Java container, the deployed REST service is enabled by default and will be available for client access.
[Synchronized] [OE Web Server is not started]	Both the OE Web Server instance and its associated REST services are in sync. But, the OE Web Server instance is not started. Right-click the OE Web Server instance, and then select Start on the context menu to start the OE Web Server.
[Republish]	Indicates that a REST service is modified and must be re-deployed to the Apache Tomcat Java container.
[Not Published]	Indicates that the OE Web Server instance is started but the Publish changes immediately check box was not selected on the Define AppServer content module page while creating the REST project. Select Publish on the OE Web Server context menu to publish the REST services having the status as Not Published.

Note: Before you publish or republish the REST services to the Apache Tomcat Java container, ensure that the selected OE Web Server instance is started. You can start or stop the OE Web Server instance from the Servers view using the Start and Stop option on the OE Web Server instance context menu or from the Servers view toolbar.