Installing muradora

Requirements

• JDK 1.5
• Ant 1.6+
• muradora Download
• muradora Orbeon XForms Web Application (orbeon.war) server for advance MODS editing using XForms.
• Fedora 2.2 is installed with the following components:
  • Solr Plugin For Fedora
  • melcoe-pdp: A web service (axis2) end-point is provided by this so that the GUI can send generated XACML policies to be stored in the DB XML database and used by the PDP.
  • melcoe-pep

Compile muradora

1. Unpack the downloaded muradora source code
2. Navigate to the src folder under muradora and edit the muradora.properties replacing the below properties with appropriate values:
   1. fedora.baseUrl: The URL to the Fedora 2.2 server (eg. http://<your fedora server hostname>:8080/fedora)
   2. fedora.default.username: This is the default "anonymous/public/non-authenticated user" that one assumes when they first arrive at Muradora. Unless they log in, their current role will be "public" and the default access permissions for this "public" role in Muradora (and by extension Fedora as well) is defined in one of the bootstrap XACML policies. This bootstrap user with the "public" role and the corresponding password should be defined in the $FEDORA_HOME/server/config/fedora-users.xml.
   3. fedora.default.password: The password corresponding to the above "fedora.default.username" usually defined in the $FEDORA_HOME/server/config/fedora-users.xml.
   4. fedora.admin.username: There are times when Muradora needs make calls to Fedora as someone with the "administrator" role . The username for the user with role "administrator" should be specified here. Similar to the "fedora.default.username" this user needs to be defined in the $FEDORA_HOME/server/config/fedora-users.xml with the corresponding password.
   5. fedora.admin.password: The password corresponding to the above "fedora.admin.username" usually defined in the $FEDORA_HOME/server/config/fedora-users.xml.
   6. fedora.risearchUrl: The url to the RISearchIndex REST service. Ensure that this is http://<your fedora server hostname>:8080/fedora/melcoerisearch.
   7. fedora.risearch.username: The admin username for accessing the RISearch interface (most of the time will be the same as "fedora.admin.username")
   8. fedora.risearch.password: The admin password for accessing the RISearch interface (most of the time will be the same as "fedora.admin.password")
   9. solr.url: The URL to Solr web service (for example: http://localhost:8080/solr)
   10. policyDataManager.url: The URL endpoint to the Policy Data Manager web service (should be on the same server as the PDP). For example: http://localhost:8080/axis2/services/PolicyDataManagerService. To check if the URL is correct, append "?WSDL" to the end of the URL and open it in a web browser. You should be able to see the WSDL which is used to describe Policy Data Manager web service.
   11. pdp.url: The address of the PDP which will be used by muradora to enforce authorisation on the client side. For example, muradora needs to determine whether the current user can see the "Submit" link on the top horizontal menu. The URL will look like this: http://localhost:8080/axis2/services/MelcoePDP. As with policyDataManager.url, you can check if it is correct by trying to browse to the web service's WSDL file.
   12. localDB.path: The folder to store the personalisation database. You also need to ensure that this folder exists.
   13. jhove.conf: This needs to point to the fully qualified path name to where jhove.conf file is located (i.e $TOMCAT_HOME/webapps/muradora/WEB-INF/jhove.conf)
3. Navigate back to the top level of the unpacked muradora folder and type "ant package-web". This will create muradora.war web archive file under dist/webapps folder which can be deployed in $TOMCAT_HOME/webapps.
4. Create a folder for the personalisation information database. By default you should ensure the following folder exists: /usr/local/muradora-db. The location of this database can be changed by editing the localDB.path property in the muradora.properties file as mentioned above.

Deploying the Orbeon Web Application

• Download Orbeon Web Application (orbeon.war), into webapps folder under $TOMCAT_HOME.
• Modify $TOMCAT_HOME/conf/server.xml and put this line into <Host> section:

<Context path="/muradora" docBase="muradora" debug="1" crossContext="true"/>

so that it looks like:

<Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true"
      xmlValidation="false" xmlNamespaceAware="false">
    <Context path="/muradora" docBase="muradora" debug="1" crossContext="true"/>
    <Context path="/orbeon" docBase="orbeon" debug="1" crossContext="true"/>
</Host>

Ensuring sufficient memory is given to Tomcat

If you are running Muradora in the same application server as all the other components such as Fedora, Solr, ASM etc..., you need to ensure that sufficient memory is given to Tomcat. You can do this by setting the appropriate JAVA_OPTS environment such as:

export JAVA_OPTS="-Xms512m -Xmx1024m -XX:PermSize=512m"

Back to Deployment Guides