An enumeration of the session types that control how multiple users access branch versioned data. Session types—transient and persistent—let you control how multiple viewers and editors access branch versioned feature services. By default, a web map or web scene with branch versioned feature services (a ServiceGeodatabase version) loads as a FeatureServiceSessionType.Transient type; you can change this type to FeatureServiceSessionType.Persistent at the map or scene level when you load the map or scene.

When you switch the ServiceGeodatabase version being used via ServiceGeodatabase.switchVersion(String), a read operation is started on the new version before releasing the previous version. If acquiring a shared lock on the new version fails (for example, if another user is editing the version), an error is raised. This behavior allows you to keep the user connected to the original version when the version they want is not yet available.

For descriptions of additional ways to manage multiple viewers and editors in branch versioned data, such as using multiple tiers of editors, see the ArcGIS Pro discussion on https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/branch-version-scenarios.htm.



See also




Link copied to clipboard

A session is held open as long as tables are actively reading or writing.

Link copied to clipboard

A momentary session is used during queries and edit operations. This is the default session type. The server creates an exclusive lock upon an editor's ServiceGeodatabase.applyEdits() operation and holds the lock only for the duration that it takes that operation to occur. An exclusive lock prevents readers and editors from accessing (connecting to and viewing) the rows affected by the edit in the ServiceGeodatabase version during this time, but they can access (connect to, view, query, and edit) other rows in the ServiceGeodatabase version. Use the transient type when concurrency is more important than data consistency between queries or between concurrent users.