Registering a new service

To create a new job for a service, register it via add Service first.

service en

Specify the name, type and URL of the service.

  • The Name can be chosen freely. The name will be displayed in the list of monitored services on the management page where it can also be used for sorting and filtering.

  • The HTTP address contains the service URL without any added requests (e.g. http://www.example.com/servletPath).

  • The Type can be selected from a list:

Esri related services Safe FME con terra & other services OGC & INSPIRE

  • Portal for ArcGIS

  • ArcGIS Server Health Check

  • ArcGIS Server (REST)

  • ArcGIS MapServer (REST)

  • ArcGIS FeatureServer (REST)

  • ArcGIS Geometry service (REST)

  • ArcGIS Geoprocessing service (REST)

  • ArcGIS Geocode service (REST)

  • ArcGIS ImageServer (REST)

  • ArcGIS MapServer/KML (REST)

  • ArcGIS Server (Soap)

  • ArcGIS Geocode service

  • ArcGIS GeoData service

  • ArcGIS Geoprocessing service

  • ArcGIS Globe service

  • ArcGIS Image service

  • ArcGIS MapServer/Mapping

  • ArcGIS MapServer/FeatureServer

  • ArcGIS MapServer/Mobile Data Access

  • ArcGIS MapServer/Network Analysis

  • ArcGIS Search service

  • Direct Connect Enterprise Geodatabase

  • FME Flow API v4

  • FME Flow API v3

  • security.manager WAS

  • security.manager PDP

  • security.manager WSS (enforcement point)

  • con terra Generic Ping interface

  • map.apps instance

  • map.apps based application

  • con terra generic ping

  • con terra smart.finder

  • Elasticsearch Cluster

  • Other

  • INSPIRE View Service

  • INSPIRE Discovery Service

  • INSPIRE Feature Download Service

  • OGC WMS

  • OGC WMTS

  • OGC WCS

  • OGC WFS

  • OGC WFS-G

  • OGC CSW

  • OGC WPS

  • OGC WTS
The Type selection influences the available example requests and the way the server response is evaluated.

How is a service monitored?

Each check of a service’s availability via a monitoring job is based on a request to the service and the subsequent verification of the response. The response is usually checked in the following order:

  1. The HTTP endpoint is accessible (connection can be established)

  2. Check of the HTTP status code (e.g., 200 OK)

  3. Optional: Check of the response time (e.g., max. 2 seconds)

  4. Check of the response content (e.g., for specific values or patterns, depending on the service type)

  5. Optional: Additional user-defined checks via expectations