...
With that out of the way, lets proceed. The system is basicly two components, the validator webservices, and the new content models.
Api hooks
First, look at Api Hooks. You need to add three lines to your fedora.fcfg. In case you don't know this file, it is the big config file for Fedora, and reside in $FEDORA_HOME/server/config. Search for <module role="fedora.server.management.Management" class="fedora.server.management.ManagementModule">
and add these three decorator hooks
| Code Block |
|---|
<param name="decorator2" value="dk.statsbiblioteket.doms.fedora.server.management.DomsForbiddenInvocationHandler"/>
<param name="decorator3" value="dk.statsbiblioteket.doms.fedora.server.management.DomsStateInvocationHandler"/>
<param name="decorator4" value="dk.statsbiblioteket.doms.fedora.server.management.DomsValidatorInvocationHandler"/>
|
Now Fedora will pass any Api-M call through those three InvocationHandlers. So we need to install these invocation handlers.
Look at the Api Hooks page. In the attachments to that page, there are two files, a src archive and a jar file. Choose whether or not
you want to build from source. Please note, the system does not really use config files right now, it uses hardcoded strings, so you might want to build from source.
Anyway, the DomsValidatorInvocationHandler just calls webservice, which it believes to reside on "http://localhost:7910/doms-validator_webservice/"
Install the jar file in $TOMCAT_HOME/webapps/fedora/WEB_INF/lib so that Fedora can access it.