ArcGIS Enterprise Admin (EAEP) flashcards

33 cards. Read the term and the definition here. The deck at the top of this page is optional.

Base deployment components

Portal for ArcGIS, ArcGIS Server, ArcGIS Web Adaptor, and ArcGIS Data Store. All four are required for a base ArcGIS Enterprise deployment.

Hosting server role

The federated ArcGIS Server site designated to host portal layers. Only one site can be the hosting server at a time.

Web Adaptor function

A reverse proxy that forwards requests to Portal or Server under a context path and can enforce authentication before requests reach the component.

Federation

Registering an ArcGIS Server site with the portal so the server trusts portal tokens. After federation, the site is managed through portal identities.

ArcGIS Data Store types

Relational store for hosted feature layers, tile cache store for hosted scene and tile layers, and spatiotemporal store for feature tracking services.

Highly available portal

Two or more portal machines behind a load balancer with a shared content directory and replicated configuration store.

Initial administrator account

The first portal administrator, created during portal creation. It cannot be renamed or deleted, only disabled after another administrator exists.

WebContextURL setting

The externally reachable URL of the portal, including the Web Adaptor path. It governs generated links and OAuth redirects.

Data store configuration

Run the configuredatastore utility against the hosting server, specifying store type and data directory, after installing ArcGIS Data Store.

Upgrade order

Upgrade Portal first, then ArcGIS Server, then ArcGIS Data Store, then Web Adaptor, following the release-specific upgrade path.

Named user licensing

Portal licenses are assigned to named users through organization settings. The portal license determines available apps and capabilities.

Server license file

ArcGIS Server requires its own license file, separate from the portal license, and licensing is by edition such as Standard or Advanced.

Enterprise identity stores

Portal can use LDAP, Active Directory, SAML 2.0, OpenID Connect, or PKI, configured in the Portal Administrator Directory under security.

Portal roles and privileges

Built-in roles are Viewer, User, Publisher, and Administrator; custom roles combine privileges from general, content, and analysis categories.

Sharing levels

Owner, Organization, Groups, and Everyone. Everyone-level sharing is anonymously accessible only if the organization permits anonymous access.

SAML configuration inputs

An identity provider metadata file, a service provider certificate, and matching assertion consumer service URLs. Clock skew between IdP and portal causes failures.

Token scope by host

Federated servers accept portal tokens, while non-federated servers use their own tokens or primary site administrator credentials.

Certificate trust requirement

HTTPS is required for federated servers and SAML/OIDC. Certificates must be trusted by clients and include the fully qualified domain name in WebContextURL.

Administrator Directory exposure

Portal and Server Administrator Directory endpoints bypass content sharing rules, so restrict their network access at the perimeter.

Hosted feature layer storage

Hosted feature layers require a relational ArcGIS Data Store. Data is written to the store, not to the server's local directories.

Registered data stores

Enterprise geodatabases, folders, and big data stores registered with a federated server so services reference data in place.

Overwrite publishing

Republishing a hosted feature layer from a source with matching name and schema preserves the item ID and dependent maps.

Portal content directory

Stores item data and thumbnails. It must be on shared storage in a highly available portal and included in backups.

Sharing versus service permissions

Sharing an item controls portal visibility, while the underlying service's permissions control direct REST access to that service.

Publish privilege

Creating services requires the Publisher role or a custom role with the publish privilege, plus a designated hosting server.

Tile cache data store use

Hosted tile layers and hosted scene layers use the tile cache data store, not the relational store used for hosted feature layers.

Log levels

Levels range from SEVERE through FINE and VERBOSE. Higher levels increase log volume, so raise them only for limited periods.

Data store backup utility

The backupdatastore utility creates ArcGIS Data Store backups. A relational store backup is required to restore hosted feature layers.

Portal site export

The export site operation in Portal Administrator Directory backs up configuration and content. Restore requires the same version.

Service instance limits

Instance counts and maximum instances per service, along with SOC processes and JVM heap sizing, are primary performance tuning levers.

Query record limits

Maximum records returned and query limits on map and feature services affect client performance. Tiling reduces load for large datasets.

Post-maintenance checks

After upgrades or configuration changes, verify federation status, data store registration, and that the hosting server is still designated.

ArcGIS Monitor

A separate product used alongside built-in logs. Server Administrator Directory also exposes REST request counts and response times.