Enterprise geodatabase

Read	Yes
Write	Yes - Only SQL Server supports all CRUD operations (create, read, update and delete). Other databases only support reading.

JMap Server can read Enterprise geodatabases from ESRI (ArcGIS 10.0 and later, JMap Server validates the EGDB version) to extract spatial and attribute data to be used as a spatial data source. The connection to the database must already be configured. See Creating Databases for more information.

The spatial data source supports value domains. Relationships defined in the enterprise geodatabase (EGDB) are also supported, but can only be exploited by using external tools.

The data source attributes will correspond to the table columns. To associate the data from other tables, a view can be created in the database and then be configured as a layer in JMap. The data source attributes will then correspond to the columns returned by the view.

Database	Select the database connection to be used to extract the spatial data and attributes. The connection is a standard database (Oracle, SQL Server, etc.). It must already be configured in JMap Admin.
System tables schema	Select the database schema where the metadata tables are located.
Schema	Select the database schema in which the table (or view) containing the feature class will be read.
Layer	Select the feature class to be read. Each table in the database corresponds to a different layer.
Id field	Select a field that contains unique identifiers. Only integer fields are listed. The field is usually called OBJECT_ID.
Geometry field	Select the field that contains the geometries.
Creation time field	(Optional) If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained.
Modification date field	(Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained. This field is used to manage transaction conflicts. It must be present in the attributes of editable layers in order for the feature to be enabled.
Author field	(Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change. If no field is selected, the data can still be edited, but this information will not be maintained.