Services
Manage and monitor your GIS services.
| Service | Status | Sharing | Owner | Actions |
|---|
My content
What you own, and what other people have shared with you.
| Layer | Where | Status | Sharing | Last change | ||
|---|---|---|---|---|---|---|
Maps
Maps you saved, and maps other people shared with you. A map puts layers from several services together, with filters, and anyone it is shared with opens it as you left it.
| Map | Owner | Sharing | Last change |
|---|
Publish a service
Compose a service from tables in the databases this server is pointed at, then publish it. Nothing is served until you press Publish, and a service is published whole — its layers and its groups arrive together or not at all.
Data sources
Where layers read from. Only an administrator registers one — ADR-018, and the reason is that a source is a credential for somebody else's database.
| Name | Connection | Layers |
|---|
A PostGIS database this server reads from, or a folder of GeoParquet files it reads in place. Registering a database stores the credential, sealed, because the server connects again every time somebody opens a map on it; a folder stores only its path. Nothing is published by registering — you choose the tables or files afterwards.
Settings
What this whole server does unless a service sets its own.
Query results
How many features a query returns when it does not ask for a number, and the
most it returns when it does — ArcGIS's maxRecordCount, which every service
document gives. Larger pages mean fewer requests and heavier responses. A service that sets
its own page size on its Limits page keeps it; empty here means the server's default.
Map ground
The basemap under the data on every map this server shows: the console, the viewer, and ArcGIS clients that use the portal's default basemap. Choose your own vector tile services, such as an OpenStreetMap extract you imported. With none chosen, maps use OpenStreetMap's public tiles.
People who chose their own ground in the viewer keep it.
Drawing order, top first
Operations
The store, the runtime, the caches, and which routes are governed.
Platform store
The store holding the catalogue, and the first thing to read when
nothing works. While it is unreachable the server keeps serving layers that were
shared public in its last answer, for a bounded window, and refuses
everything else — so a store outage looks like every private layer disappearing at
once, not like the server being down.
Runtime
This process, now. GC pause as a share of wall-clock is the number the performance gate found decisive — it stays invisible at concurrency 1 and it is what sets the ceiling.
Caches
Tiles held on disk, and table shapes remembered from the data source. Sharing and started/stopped are deliberately never cached.
Datastore
By owner, largest first
Sizes as PostgreSQL reports them. No quota is set: this is what is on disk, not a limit.
Every route this server answers, and what decides who may reach it. The number that matters is ungoverned: ADR-018 condition 5 says it is zero, and this is where that claim is checked rather than asserted.
Publishing a layer creates the service that holds it, and unpublishing the last one leaves the container — so an estate accumulates services with nothing in them, each advertised in the directory as a FeatureServer with no layers. Nothing records which were made on purpose, which is why this is a list and a button rather than something that happens by itself.
| Service | Folder | Sharing |
|---|---|---|
| Not read yet. | ||
| Route | Methods | Governed by |
|---|
Logs
What this server and its studio have been doing.
Administration is the audit trail — every action that changed something, who did it, and from where. Requests is one row per HTTP request, with its status and how long it took. Studio viewer is what the map viewer reported from a browser, which is where a failure that never reached the server shows up. Server warnings is what this server itself reported — a layer it could not read, a source it could not reach — held in memory since it last started.
| When | What | Who | From | Resource |
|---|
Domains
Lists and ranges of values that fields on many layers share. A field chooses one on its layer's Fields page; its values are changed here, and a change reaches every field that uses it.
| Domain | Values | Used by | Owner | Actions |
|---|
Groups
A set of members, and the services shared with them. What is shared with a group is readable by its members and by nobody else.
| Group | Confers | You are | Owner | Members | Services |
|---|
What it is for
Recently shared
Facts
| Service | Kind | Reaches members | Shared | ||
|---|---|---|---|---|---|
| Member | Standing | Joined |
|---|
Anonymous view
What a caller with no credential actually sees of your content.
What a caller with no credential actually sees of your content, by asking.
Every request in this table leaves the Authorization header off; the address
comes from your own listing, because you cannot ask what a stranger sees at a URL you were
unable to find.
| Layer | Shared | Service | Layer | Count | Reality against intent |
|---|---|---|---|---|---|
| Not run yet. | |||||
404 does not mean missing. It is the same answer for a layer that does not
exist and one that exists and is not shared with you, and that is deliberate. So the column to
read is the last one, which compares what answered against what the catalogue says you
intended. Two disagreements are marked: something shared private or
organization that answered anyway, and something shared public that
did not.
Roles
What members may do. Every role's privileges can be changed except the administrator's, whose authority is a property of the server rather than a set of rows.
| Role | Description | Privileges | Members |
|---|
Sign-in
Where people can sign in besides a password on this server: an OpenID Connect or SAML 2.0 provider such as Microsoft Entra ID, AD FS, Keycloak, Okta or Google, or an LDAP directory such as Active Directory. Their groups there can decide their role and groups here.
| Provider | Address | First sign-in | Accounts | Actions |
|---|
Apps
Apps that sign people in to this server through OAuth — a web app with an app ID, or ArcGIS Field Maps. A person signs in on this server's own page, and the app receives a code only at an address registered here.
An address must be https://, http://localhost, a
custom scheme such as my-app://auth/, or
urn:ietf:wg:oauth:2.0:oob. A code is never sent anywhere else.
| App | App ID | Returns to |
|---|
Members
Who has an account, and what each of them may do.
A new member
The server picks the password, not you. You see it once, on this screen, and you pass it on. It is marked as needing replacement, so their first act after signing in has to be setting their own — nothing else answers until they do. There is no invitation e-mail because this server cannot send a message at all.
| Member | Role | User type | State | Owns | Since |
|---|
There is no delete, and the Owns column is why. A member owns content: removing the row would orphan every service that names them as its owner, and the sharing rules read that to decide who may see what. Disabling stops the sign-in and leaves the ownership standing.
—
Layers
Service timeouts
Worker processes
An empty box takes the server's configured default, shown as the placeholder. That is not the same as typing the default in: a typed copy stops tracking the setting.