Using ESRI ArcSDE as deegree WFS backend

(This documentation was provided by Christoph Pollmann, MOSS GmbH via Email; if binding of deegree against SDE gets stable with newer versions, this documentation should go to the WFS documentation)

Although the ArcSDE datastore hasn't a JDBC-Driver it uses a <JDBCConnection> element to define the required connection parameters. An configuration may look like the following example:

   1 <xsd:annotation>
   2    <xsd:appinfo>
   3      <deegreewfs:Prefix>app</deegreewfs:Prefix> 
   4         <deegreewfs:Backend>SDE</deegreewfs:Backend> 
   5         <deegreewfs:DefaultSRS>EPSG:31466</deegreewfs:DefaultSRS> 
   6          <JDBCConnection xmlns="http://www.deegree.org/jdbc">
   7              <Driver>SDE</Driver> 
   8            <Url>testsde.moss.de:5151</Url> 
   9            <User>USER</User> 
  10            <Password>PASS</Password> 
  11            <SecurityConstraints/> 
  12            <Encoding>iso-8859-1</Encoding> 
  13            <SDEDatabase/> 
  14            <SDEVersion>iso-8859-1</SDEVersion>
  15     </JDBCConnection>
  16   </xsd:appinfo>
  17 </xsd:annotation>

Parameter	Value
Driver	not evaluated, but mandatory
Url	used for the SDE server name and instance (port number)
SDEDatabase	database name, if supported by the underlaying DB
SDEVersion	version name, which will be used to store the changes, made via the WFS to avoid data changes in the default version. If the version doesn't already exist, it will be created on the first connect. If You don't want to use versioned objectclasses and featuretypes, You can specify “SDE.DEFAULT” to write directly to the default tables.

1. Known Restrictions:

Below all known restrictions of the actual implementation are listed:

Only ArcSDE instances can be accessed.
Personal Geodatabases are not connectable.
Network topologies are not accessible by the ArcSDE-JavaAPI.

CategoryDeegree2