Fedora, along with Drupal, is one of the core technologies behind Islandora. This chapter will cover the basic steps for installing Fedora - for more information, please see the FedoraCommons documentation.
Fedora is available under the terms of the Apache License and has a very active open source community producing additional tools, applications and utilities. Islandora currently uses Fedora version 3.5.
Pre-installation
...
Software Checklist
Fedora requires the following to be set-up and running prior to beginning your installation:
- Java SE Development Kit (JDK) 6
- A database: Installed for Drupal. Consult the Fedora installation guide for notes on running other databases.
- An application server: Fedora includes the Tomcat Application Server. Consult the Fedora installation guide for notes on running other application servers.
Installation Steps
1. Download the latest release of Fedora from Fedora Commons (3.5 is the latest tested for use with Islandora).
...
a. $FEDORA_HOME/tomcat/logs/catalina.out should contain no errors.
b. View your Fedora instance through a web browser: http://localhost:8080/fedora/ or http://[yourdomain]:8443/fedora
Set XACML Policies
10. Stop your Fedora instance by running:$FEDORA_HOME/tomcat/bin/shutdown.sh
mv /usr/local/fedora/data/fedora-xacml-policies/repository-policies/default/deny-purge-* ~/
...
Code Block |
---|
|
<?xml version="1.0" encoding="UTF-8"?>
<Policy xmlns="urn:oasis:names:tc:xacml:1.0:policy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
PolicyId="permit-apim-to-authenticated"
RuleCombiningAlgId="urn:oasis:names:tc:xacml:1.0:rule-combining-algorithm:first-applicable">
<Description>note that other policies may provide exceptions to
this broad policy. This policy assumes api-m users have to be
authenticated</Description>
<Target>
<Subjects>
<AnySubject/>
</Subjects>
<Resources>
<AnyResource/>
</Resources>
<Actions>
<Action>
<ActionMatch MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal">
<AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">urn:fedora:names:fedora:2.1:action:api-m</AttributeValue>
<ActionAttributeDesignator DataType="http://www.w3.org/2001/XMLSchema#string"
AttributeId="urn:fedora:names:fedora:2.1:action:api"/>
</ActionMatch>
</Action>
</Actions>
</Target>
<Rule RuleId="1" Effect="Permit"/>
</Policy>
|
Save as permit-apim-to-authenticated.xml.
...
Code Block |
---|
<AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">192.168.56.1</AttributeValue> |
...
12. Restart Fedora by using the startup command from step 8:
Code Block |
---|
$FEDORA_HOME/tomcat/bin/startup.sh |
...
13. Access the Fedora Web Administrator: http://localhost:8080/fedora/admin and ensure you can ingest and purge objects.
14. For information on using Fedora, make use of the tutorials at the Fedora Commons site.
Note |
---|
There are two global policies that block/override purge rights. This behaviour is correct as it assumes that items will be set to a status of "deleted" rather than being purged directly. By default it assumes that if an object or Datastream is set to active or inactive, then only the "administrator" role can purge. To resolve this, you can simply remove these policies in $FEDORA_HOME/data/fedora-xacml-policies/repository-policies/default/: - deny-purge-datastream-if-active-or-inactive.xml
- deny-purge-object-if-active-or-inactive.xml
|
...