To monitor a REST Web application, inspect its statistics. To tune it, modify its properties.
You can monitor a REST Web application using the OpenEdge Management, OpenEdge Explorer or RESTMAN utility.
The following is the list of REST Web application statistics:
Adapter errors — Total number of REST failures
Application errors — Total number of errors related to REST Web applications
Average response time — Average response time of each request response
Failed admin logins — Total number of failed administrator logins
Failed admin requests — Total number of administrator requests that failed due to missing request information
Failed app server connections — Total number of failed AppServer connections in the connection pool
Failed user logins — Total number of failed user logins
Failed user requests — Total number of requests that failed due to missing request information
Max response time — Maximum response time of each request response
Successful admin logins — Total number of successful administrator logins
Successful admin requests — Total number of successful administrator requests
Successful app server connections — Total number of successful AppServer connections in the connection pool for this REST Web application
Successful user logins — Total number of successful user logins
Successful user requests — Total number of successful user requests handled by the selected REST Web application
Creation time — Date and time that counting began for the statistics
Start time — Start date and time of the REST Web application
You use the following RESTMAN utility commands to work with REST Web application statistics:
getstats: Displays the statistics for a REST Web application, such as Number of Successful User Requests and Average Response Time for User Requests. For more information, see RESTMAN getstats (Application).
You can also work with REST Web application statistics using OpenEdge Management or OpenEdge Explorer. For more information on the statistics of a REST Web application, see the OpenEdge Management and OpenEdge Explorer: Configuration manual or the OpenEdge Management or OpenEdge Explorer online help.
If the REST Web application uses a NameServer and is session-free, it has a connection pool, with properties you can set. If the Web service is session-managed, it can be set to store multiple requests to the service or repeat them. For more information, see the Reference to OpenEdge Web Service Properties and the OpenEdge Management or OpenEdge Explorer online help.