Difference between revisions of "CDO Server Configuration"

Revision as of 09:27, 14 November 2007

Example XML

This section shows an example XML configuration file for the CDO server. It must be located in the folder that you declared via system property net4j.config. The subsequent section explains the used XML Elements. You can also click directly on the links in the XML file to navigate to the respective descriptions.

 01  <?xml version="1.0" encoding="UTF-8"?>
 02  <cdoServer>
 03  
 04    <acceptor type="tcp" listenAddr="0.0.0.0" port="2036">
 05      <!--
 06      <negotiator type="challenge" description="/temp/users.db"/> 
 07      -->
 08    </acceptor>
 09  
 10    <repository name="repo1">
 11      <property name="overrideUUID" value="1ff5d226-b1f0-40fb-aba2-0c31b38c764f"/>
 12      <property name="supportingAudits" value="true"/>
 13      <property name="verifyingRevisions" value="false"/>
 14      <property name="rememberingKnownTypes" value="false"/>
 15      <property name="currentLRUCapacity" value="10000"/>
 16      <property name="revisedLRUCapacity" value="100"/>
 17      
 18      <store type="db">
 19        <!-- mode: OFF | EXPRESS | NORMAL | GUARANTEED -->
 20        <invalidationStrategy mode="EXPRESS"/>
 21        
 22        <!-- type: horizontal | vertical | <any user-contributed type>-->
 23        <mappingStrategy type="horizontal">
 24          <!-- ONE_TABLE_PER_REFERENCE | ONE_TABLE_PER_CLASS | ONE_TABLE_PER_PACKAGE | ONE_TABLE_PER_REPOSITORY | LIKE_ATTRIBUTES -->
 25          <property name="toManyReferences" value="ONE_TABLE_PER_REFERENCE"/>
 26  
 27          <!-- LIKE_ATTRIBUTES | LIKE_TO_MANY_REFERENCES-->
 28          <property name="toOneReferences" value="LIKE_ATTRIBUTES"/>
 29          
 30          <!-- MODEL | STRATEGY-->
 31          <property name="mappingPrecedence" value="MODEL"/>
 32        </mappingStrategy>
 33        
 34        <!--<dbAdapter name="derby"/>
 35        <dataSource
 36          driverClass="org.apache.derby.jdbc.EmbeddedDataSource"
 37          databaseName="/temp/cdodb1"
 38          createDatabase="create"/>-->
 39  
 40        <dbAdapter name="derby"/>
 41        <dataSource 
 42          driverClass="org.apache.derby.jdbc.ClientDataSource" 
 43          databaseName="cdodb1"
 44          createDatabase="create"/>
 45  
 46        <!--<dbAdapter name="hsqldb"/>
 47        <dataSource
 48          driverClass="org.eclipse.net4j.db.hsqldb.HSQLDBDataSource"
 49          database="jdbc:hsqldb:mem:cdodb1"
 50          user="sa"/>-->
 51  
 52        <!--<dbAdapter name="mysql"/>
 53        <dataSource
 54          driverClass="com.mysql.jdbc.jdbc2.optional.MysqlDataSource"
 55          url="jdbc:mysql://localhost/cdodb1"
 56          user="sa"/>-->
 57      </store>
 58    </repository>
 59  
 60  </cdoServer>

Element cdoServer

The root element of the cdo-server.xml file. It can contain zero, one or several acceptor elements and zero, one or several repository elements.

Element acceptor

Defines an IAcceptor instance. Please refer to the Net4j documentation for details about acceptors and connectors. The type attribute corresponds to the type of an acceptor factory that is contributed via the org.eclipse.net4j.util.factories extension point with a product group of org.eclipse.net4j.acceptors. The remaining attributes depend on the specified type attribute value. The following values are possible with the shipped distribution (subject to user supplied extension):

• tcp: Acceptor for fast, new I/O based socket connections. The following additional attributes are recognized:
  • listenAddr: The network address the server socket shall be bound to. A value of "0.0.0.0" is the default (whole attribute can be omitted) and tells the socket to listen on all available addresses.
  • port: The network port the server socket shall be bound to. A value of "2036" is the default (whole attribute can be omitted).
• jvm: Acceptor for JVM internal (non-socket based ) connections. Currently not supported by the Net4Configurator.

The acceptor element can contain zero or one negotiator element(s).

Please note that the acceptor element is likely to be moved to a separate Net4j configuration file in the future.

Element negotiator

Defines an INegotiator instance to be used by the connectors created by an acceptor (defined by the enclosing acceptor element). Please refer to the Net4j documentation for details about negotiators and the pluggable security concept that can be used for authentication and authorization. The type attribute corresponds to the type of a negotiator factory that is contributed via the org.eclipse.net4j.util.factories extension point with a product group of org.eclipse.net4j.negotiators. The remaining attributes depend on the specified type attribute value. The following values are possible with the shipped distribution (subject to user supplied extension):

• challenge: Negotiator for simple yet effective and cryptographically secure challenge/response based negotiations. The following additional attributes are recognized:
  • description: The absolute path to a file in the local file system that contains the credentials of the users in the form userid: password.

Element repository

Property overrideUUID

Property supportingAudits

Property verifyingRevisions

Property rememberingKnownTypes

Property currentLRUCapacity

Property revisedLRUCapacity

Element store

Element invalidationStrategy

Element mappingStrategy

Property toManyReferences

Property toOneReferences

Property mappingPrecedence

Element dbAdapter

Element dataSource

Wikis: CDO | Net4j | EMF | Eclipse