Changes between Version 3 and Version 4 of AnnotationManagerN4J

Timestamp:

Nov 14, 2012, 2:46:35 PM (12 years ago)

Author:

casties

Comment:

--

AnnotationManagerN4J

@@ -17 +17 @@
 1. `hg clone https://it-dev.mpiwg-berlin.mpg.de/hg/AnnotationManagerN4J`
 2. `cd AnnotationManagerN4J`
-3. `mvn package` (this produces the web-app as a directory `target/AnnotationManager` or war file `target/AnnotationManager.war`)
+3. `mvn package` (this produces the webapp as a directory `target/AnnotationManager` or war file `target/AnnotationManager.war`)
 
 
@@ -28 +28 @@
 3. `mvn install`
 
+
+== Configuration ==
+
+The server is configured through the file `serverconfig.property` in the `WEB-INF` folder in the webapp directory.
+
+The file is in Java property file syntax and might look like this:
+{{{
+# directory where Neo4J keeps its files (otherwise the files will be put in the webapp directory)
+annotationmanager.graphdb.path = /usr/local/neo4j/dbs/AnnotationManager
+# LDAP server URL for getting full names for IDs (otherwise no full names)
+annotationmanager.ldapserver.url = ldap://ldap.mpiwg-berlin.mpg.de/dc=mpiwg-berlin,dc=mpg,dc=de
+# user name and password for the admin frontend for Persons and Groups
+annotationmanager.admin.user = superuser
+annotationmanager.admin.password = superpassword
+}}}
+
+The server also has a list of API client keys that are used to authenticate Tokens from the token servers. On the annotation server the keys are in the file `consumerkeys.property` in the `WEB-INF` folder in the webapp directory.
+
+The file is in Java property file syntax and might look like this:
+{{{
+# format: consumerKey = consumerSecret
+#         consumerKey.label = Label
+test1 = abcdef
+test1.label = TEST
+}}}