Installing DOMS
Getting the package
Download the newest DOMS from
https://sbforge.org/nexus/content/repositories/releases/dk/statsbiblioteket/doms/testbed/testbed/
There are two zip packages in the newer versions:
- testbed-<version>-testbed.zip
- testbed-<version>-testbed+ingester.zip
The second one contains everything the normal testbed does, plus an example content model, an example custom ingester and a few example files.
Installing the package
Unzip the downloaded package
Edit the file bin/setenv.sh with relevant values for install
Run:
bin/install.sh <installdir>
This will start the installation proces, which installs a tomcat with Fedora and the DOMS webservices, and ingests the base objects.
Testing DOMS
You can test the the install succeeded by checking the URL
http://localhost:7880/surveillance-surveyor-service/
(replace localhost:7880 with your configured values if necessary)
Using DOMS
The interface for interacting with DOMS is a SOAP webservice, where the WSDL can be found at
http://localhost:7880/centralWebservice-service/central/?wsdl
It is also possible to communicate directly with the underlying fedora webservice, e.g. with
http://localhost:7880/fedora/admin
http://localhost:7880/fedora/search
http://localhost:7880/fedora/risearch
DOMS installs by default with two users, with usernames and passwords as defined by the bin/setenv.sh configuration on install. Further users can be defined in services/fedora/server/config/fedora-users.xml.
DOMS can be stopped or started using
tomcat/bin/shutdown.sh
and
tomcat/bin/startup.sh
Installing test objects (optional)
In the directory you installed to, run
cd ingester/radio-tv-0.0.6 bin/ingest.sh -h files/preingestfiles/2007 bin/ingest.sh -h files/preingestfiles/2008 bin/ingest.sh -h files/preingestfiles/2009 bin/ingest.sh -h files/preingestfiles/2010
Installing DOMS GUI (optional)
Download the newest version from
https://sbforge.org/nexus/content/repositories/releases/dk/statsbiblioteket/doms/testbed/guitestbed
Unzip the downloaded package.
Edit the file bin/setenv.sh with relevant values for install. Note: The DomsGUI must run in a different tomcat than DOMS itself. Currently, DOMS GUI requires a specially configured CAS server in order to function.
Run
bin/install.sh <installdir>
Note: The installdir should be a different directory to DOMS.
Testing and using DOMS GUI (optional)
Use the DomsGUI interface at