For the connection-establishment, deegree, respectively JDBC requires information about the drivers, which are to be used and the user, which would like to open the connection. Normally a password is required as well. In addition, the driver requires the information, which version of the Spatial extension is used. The according section in the configuration-file looks like the following:

<Connection name="oracle spatial">
   <driver>oracle.jdbc.driver.OracleDriver</driver>
   <logon>jdbc:oracle:thin:@127.0.0.1:1521:latlon</logon>
   <user>user</user>
   <password>passwort</password>
   <spatialversion>8.1.6</spatialversion>
</Connection>
            

The attribute "name" is supplied for general information und is not yet analysed. With the <driver> element the server is informed, which JDBC driver is needed for the connection-establishment (in this case a Class 4 driver). <logon> specifies the driver-type and address that is used to connect to the database, and the instance, of the database. If the preset Class 4 driver is used, just address, port and instance have to be adjusted.

The <user> and <password> elements are self-explanatory. However, if no password is needed for the connection, the element is still required. With the element <spatialversion> the version of the Spatial Extension integrated in the database is communicated to the driver. This version-number does not have to be equal to the version of the Oracle Database!

The configuration file contains references to the responsibilities and exact formats of the results from a GetFeature request. These apply to each accessible FeatureType, described by the configuration-file of a Datastore. For each known output-format, the WFS can handle and the Datastore serves, the configuration-document must contain an entry.

Thus, it is stated which class is responsible for formatting the results. In the case of an oracle database there are the three classes mentioned. If new output formats are implemented by the user, a corresponding class has to be created and declared for each of these formats in the configuration document in the datastore. The classes have to implement the interface org.deegree.services.wfs.DataStoreOutputFormat.

When declared in this manner the response schema is defined by the database schema in the case of GML 2 or XML output. The user has the possibility to exchange the data model by one of his own. For this reason, in the <GML2 ...> and <XML ...> elements it is possible to define a filter initiating and describing the re-formatting.

...
<OutputFormat>
   <GML2 responsibleClass="org.deegree_impl.services.wfs.oracle.DataStoreOutputGML">
      <Param name="FILTER" value="file:///$deegreewfs_home/xml/myGMLModel.xsl"/>
      <!-- URL where an application can find the schema of the feature type -->
      <SchemaLocation>file:///$deegreewfs_home/xml/myGMLSchema.xsd
   </GML2>
   <XML responsibleClass="org.deegree_impl.services.wfs.oracle.DataStoreOutputXML">
      <Param name="FILTER" value="file:///$deegreewfs_home/xml/myXMLModel.xsl"/>
      <!-- URL where an application can find the schema of the feature type -->
      <SchemaLocation>file:///$deegreewfs_home/xml/myXMLSchema.xsd
   </XML>
   <FEATURECOLLECTION 
   responsibleClass="org.deegree_impl.services.wfs.oracle.DataStoreOutputFC">
   <!-- URL where an application can find the schema of the feature type -->
      <SchemaLocation>file:///$deegreewfs_home/xml/myFCSchema.xsd
   </FEATURECOLLECTION>
</OutputFormat>
...

Within the <GML2> respectively <XML> elements a parameter (element) is defined whereas the name of the parameter (name) FILTER and its value are links to the XSLT stylesheet generating the requested data model by transforming the input schema. Attention should be paid to the case that the data schema transformed by a filter (XLST stylesheet) has to be conformant to the OGC GML 2.1.1 specification if GML 2 is the declared output format. Due to the fact that the FEATURECOLLECTION is binary coded there is no filter provided at the time. Additionaly a XML schema is defined for each output format describing its structure.

As mentioned above, deegree WFS is able not only to handle FeatureTypes based on a "flat" table. As a basic principle any complex schema is addressable represented as 1:1, 1:n and m:n relations between tables. For the WFS being able to resolve the relations, it has to be informed about them within the configuration file of a datastore for each of the FeatureTypes the datastore it is responsible for.

The following example shows the structure of the schema description of a Datastore:

<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>

<DatastoreConfiguration name="iso19115" type="GMLDB">
  <Connection name="iso19119">
    <driver>oracle.jdbc.driver.OracleDriver</driver>
    <logon>jdbc:oracle:thin:@131.220.106.104:1521:latlon2</logon>
    <user>aUser</user>
    <password>aPassword</password>
  </Connection>

  <FeatureType name="ISO19119">
    <OutputFormat>
      <GML2 responsibleClass="org.deegree_impl.services.wfs.gml.GMLDBDataStoreOutputGML">
      <SchemaLocation>
         file:///$deegreewfs_home/xml/iso19119GDIFull.xsd
      </SchemaLocation>
      </GML2>
      <XML responsibleClass="org.deegree_impl.services.wfs.gml.GMLDBDataStoreOutputXML">
      <Param name="FILTER" 
         value="file:///$deegreewfs_home/xml/ISO19115.xsl"/>                
      <SchemaLocation>
         file:///$deegreewfs_home/xml/iso19119GDIFull.xsd
      </SchemaLocation>
      </XML>
    </OutputFormat>
    
    <MappingField>
      <Property name="test" type="DOUBLE"></Property>
      <DatastoreField name="Andreas.ISO19119.test" type="DOUBLE"></DatastoreField>
    </MappingField>
    <MappingField>
      <Property name="idMd" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119.idMd" type="VARCHAR"></DatastoreField>
    </MappingField>
    <MappingField>
      <Property name="ServiceType" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119.ServiceType" type="VARCHAR"/>    
    </MappingField>
    <MappingField>
      <Property name="ServiceTypeVersion" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119.ServiceTypeVersion" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="DataCoupling" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119.DataCoupling" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="geographicBox" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119.geographicBox" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="Title" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119.Title" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="Abstract" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119.Abstract" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="creationDate" type="DATE"></Property>
      <DatastoreField name="Andreas.ISO19119.creationDate" type="DATE"/>
    </MappingField>
    <MappingField>
      <Property name="revisionDate" type="DATE"></Property>
      <DatastoreField name="Andreas.ISO19119.revisionDate" type="DATE"/>
    </MappingField>
    <MappingField>
      <Property name="IsoDocUrl" type="DATE"></Property>
      <DatastoreField name="Andreas.ISO19119.IsoDocUrl" type="DATE"/>
    </MappingField>
    <MappingField>
      <Property name="ISO19119Full" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119.ISO19119Full" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="FKKewords" type="INTEGER"></Property>
      <DatastoreField name="Andreas.ISO19119.FKKewords" type="INTEGER"/>
    </MappingField>
    <MappingField>
      <Property name="FKOrgName" type="INTEGER"></Property>
      <DatastoreField name="Andreas.ISO19119.FKOrgName" type="INTEGER"/>
    </MappingField>
    <MappingField>
      <Property name="keyword" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119Keywords.name" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="thesaurus" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119Keywords.thesaurus" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="organisationName" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19119OrgName.name" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="FKGeoDesc" type="INTEGER"></Property>
      <DatastoreField name="Andreas.ISO19115.FKGeoDesc" type="INTEGER"/>
    </MappingField>
    <MappingField>
      <Property name="code" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19115GeogrDesc.name" type="VARCHAR"/>
    </MappingField>
    <MappingField>
      <Property name="/ISO19115/idMD" type="VARCHAR"></Property>
      <DatastoreField name="Andreas.ISO19115.fileidentifier" type="VARCHAR"/>
    </MappingField>
        
    <MasterTable name="Andreas.ISO19119" targetName="ISO19119Tab">
      <!-- name of the table column that stores the id of a feature -->
      <IdField number="true" auto="true">ID</IdField>
      <!-- references to related tables: 
          tableField -> name of the field that references another table
          replaceable -> if true the 'simple' content of field will be replaced by 
           'complex' content build from the related table targetTable -> name of the 
           table that is referenced by the column named at field targetField -> 
           field of the referenced table that references specific rows. -->
      <Reference tableField="FKKeywords" replaceable="true"
                targetTable="Andreas.ISO19119Keywords" targetField="ISO19119"/>
      <Reference tableField="FKOrgName" replaceable="true" 
                targetTable="Andreas.ISO19119OrgName" targetField="ISO19119"/>
      <Reference tableField="ID" replaceable="false" 
                targetTable="Andreas.ISO19119_19115_JoinTab" targetField="ISO19119"/>
      <!-- name of a column(s) that contains geodata (GML) -->
      <GeoFieldIdentifier>geographicBox</GeoFieldIdentifier>
    </MasterTable>
    <RelatedTable name="Andreas.ISO19119Keywords" targetName="descriptiveKeywords"
             jointable="false">
      <IdField number="true" auto="true">ID</IdField>
    </RelatedTable>
    <RelatedTable name="Andreas.ISO19119OrgName" targetName="organisationName" 
            jointable="false">
      <IdField number="true" auto="true">ID</IdField>
    </RelatedTable>
    <RelatedTable name="Andreas.ISO19119_19115_JoinTab" 
            targetName="ISO19119_19115_JoinTab" jointable="true">
      <IdField number="true" auto="true">ID</IdField>
      <Reference tableField="ISO19115" replaceable="true" 
            targetTable="Andreas.ISO19115" targetField="ID"/>
    </RelatedTable>
    <RelatedTable name="Andreas.ISO19115" targetName="ISO19115" jointable="false">
      <IdField number="true" auto="true">ID</IdField>
      <Reference tableField="FKGeoDesc" replaceable="true" 
            targetTable="Andreas.ISO19115GeogrDesc" targetField="ISO19115"/>
      <Reference tableField="FKKeywords" replaceable="true" 
            targetTable="Andreas.ISO19115Keywords" targetField="ISO19115"/>      
    </RelatedTable>    
    <RelatedTable name="Andreas.ISO19115GeogrDesc" targetName="geographicDesc" 
            jointable="false">
      <!-- name of the table column that stores the id of a feature -->
      <IdField number="true" auto="true">ID</IdField>
      <!-- name of the table column that stores a geometry feature -->
      <GeoFieldIdentifier>geographicBox</GeoFieldIdentifier>
    </RelatedTable >        
    <RelatedTable name="Andreas.ISO19115Keywords" 
         targetName="iso19115descriptiveKeywords" jointable="false">
      <!-- name of the table column that stores the id of a feature -->
      <IdField number="true" auto="true">ID</IdField>      
    </RelatedTable >
  </FeatureType>
</DatastoreConfiguration>

The name of the FeatureType has to correspond with the capabilities document. First of all the main table of the FeatureType is declared within the <MasterTable> element in the database.

According to the declaration of the formats the mapping for the feature type will be declared. These describes through which name (PropertyName) a database field is accessible within a request. It also will be declared with this name within the result to a GetFeature request - if no FILTER is defined. If the property names are defined a Xpath expressions (e..g. /Type/SubType/PropertyName) the '/' will be substitued with '.' withn the the to a GetFeature request (<Type.SubType.PropertyName>). For each mapping also the datatype of the property and the associated database field will be declared. Permissible are all values defined within the class java.sql.Types (see table below) and the type GEOMETRY. In future releases of deegree WFS through this information a mapping between different datatypes shall be performed.

Next, tables relatet to these elements follow (<RelatedTable>). Both the main table and the relational tables can, but do not have to, imply declarations allowing the WFS to set further tables in relation to it. Only the declaration of the ID field in the main table is obligatory; the attribute "number" specifies if this is a numeral field. The attribute "auto" shows if the value of the field is automatically set by the database.

Relations to other tables are arranged by the definitions of foreign keys <Reference>. Initially, it is defined which field of the table is linked to another table via the attribute "field". The attribute "replacable" determines whether the field of the table in the reply schema should be replaced with the content of the relation. A new field (property) is added to hold the content of the relation, if replaceable = false is set. This can be useful if a field (e.g. ID) relates to multiple tables. In this case it would not be possible to replace the field ID with the content of the relations, as this can be only be done with one relation. Besides, the ID field is mandatory for the WFS. Please note that field names are handled case insensitive by deegree WFS.

Next "targetTable" determines the table the key is targeted at. The target field is declared with "targetField". In the above mentioned example the FKKeywords field of the main table relates to the field ISO19119 of the table ISO19119Keywords.

Not only the main table can relate to other tables in this manner, even relationally connected tables (<RelatedTable>) can possess relations to further tables. This can be seen in the example with the tables ISO 19119_19115_JOIN and ISO19115. Using this technique arbitrarily complex schemas can be realised.

Following the description of the relational FeatureType schemas the document is provided which contains the XML schema definition of the FeatureType and which will be accessed in the case of DescribeFeatureType request. Please note that all schema definitions within deegree WFS should use the same prefix for the namspace (<xs:schema ...>).

Furthermore, when using Oracle Spatial, it must be declared in which spatial coordinate system the geometries of the FeatureType are stored. Although Oracle Spatial can internally represent spatial coordinate systems, the name conventions used there do not correspond with the used authority code combinations (e.g. EPSG:4326, EPSG:23032, XYZ:1234) as preferred by OGC.

In principle it is possible to describe various FeatureTypes in the configuration document and provide thus access to the same instance of the datastore via several ways. It should be paid attention to the fact that the definition of the filter applies to each FeatureType defined on within the configuration document.