Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagenone
mysql \-u root \-p

Create the database. For example, to create a database named "fedora3", enter:

Code Block

...

languagenone

CREATE DATABASE fedora3;

Set username, password and permissions for the database. For example, to set the permissions for user fedoraAdmin with password fedoraAdmin on database "fedora3", enter:

Code Block
language

...

none

GRANT ALL ON fedora3.\* TO fedoraAdmin@localhost IDENTIFIED BY 'fedoraAdmin';

...


GRANT ALL ON fedora3.\* TO fedoraAdmin@'%' IDENTIFIED BY 'fedoraAdmin';

MySQL 4.1.x users must also specify the default character set for the Fedora database as "utf8" and the default collation as "utf8_bin". For example, to set the default character set and collation on a database named "fedora3", enter:

panel
Code Block
languagenone

ALTER DATABASE fedora3 DEFAULT CHARACTER SET utf8;


ALTER DATABASE fedora3 DEFAULT COLLATE utf8_bin;

Oracle

To prepare Oracle for use with Fedora, the following steps should be taken by an administrative user. First, using the Database Configuration Assistant, ensure that the database you'll be using is created with the UTF8 charset. Next, you'll need to create a Fedora tablespace and user in the database. Assuming the administrative user is sys and the SID is fedora3, log in using SQL*Plus using the following command:

Code Block

...

languagenone

sqlplus sys/PASSWORD@fedora3 as sysdba

To create a tablespace named "fedora_tblspace" with data in /var/lib/oracle, enter the following:

Code Block
language

...

none

CREATE TABLESPACE fedora_tblspace

...


DATAFILE '/var/lib/oracle/fedora_tblspace.dat' SIZE 1024M REUSE

...


AUTOEXTEND ON NEXT 256M MAXSIZE UNLIMITED

...


SEGMENT SPACE MANAGEMENT AUTO;

To create a user "fedoraAdmin" with password "fedoraAdmin", using the "fedora_tblspace", enter the following:panel

Code Block
languagenone

CREATE USER fedoraAdmin IDENTIFIED BY fedoraAdmin

...


DEFAULT TABLESPACE fedora_tblspace;

Using the GRANT command, make sure the user has permission to connect, create, alter, and drop tables sequences, triggers, and indexes in this tablespaces. For example:panel

Code Block
languagenone

GRANT ALL PRIVILEGES TO fedoraAdmin;
Info

...

Due to distribution license restrictions, the Fedora Installer does not include the Oracle JDBC driver. Oracle JDBC drivers are available from http://technet.oracle.com/software/tech/java/sqlj_jdbc/content.html. The installer will prompt you for the location of the driver on your filesystem. Also, if you run Fedora in Java 6 as is required by Fedora 3.4, you will need an Oracle Java 6 jdbc jar such as ojdbc6.jar.

PostgreSQL

Please consult the documentation at http://www.postgresql.org/docs/ for more detailed information about configuring PostgreSQL.

Launch the PostgreSQL interactive terminal, psql, (optionally appending the -U argument to connect as a different user).

Code Block
language

...

none

psql \-d postgres

To create a user "fedoraAdmin"" with password "fedoraAdmin" and database named "fedora3", enter the following:

panel
Code Block
language
none

CREATE ROLE "fedoraAdmin" LOGIN PASSWORD 'fedoraAdmin';


CREATE DATABASE "fedora3" WITH ENCODING='UTF8' OWNER="fedoraAdmin";

Microsoft SQL Server

David Handy has contributed a guide for interfacing Fedora with MS SQL Server

...

To start the installer, change to the directory where you downloaded the installer and at a command prompt, enter:

Code Blockpanel
languagenone

java -jar fcrepo-installer-3.4.2.jar
Tip
Info
title
Tip

Fedora can also be installed in non-interactive mode by specifying an install.properties file as an argument to the installer. After installing interactively, you will find an install.properties file in your $FEDORA_HOME/install/ directory. You can use this file as a template for future, non-interactive installations. *Take care if you are using an install.properties file from an earlier release as the file may not contain some properties defined in the later release, default settings will be used in this case, which may or may not be appropriate for your installation.

Note

Please ensure that the user account that is running the installer has sufficient permissions to write to the directories where Fedora will be installed (if deploying to an existing Tomcat installation, this includes permissions to the Tomcat directory). Installer created files will usually be owned by the user running the installer. Consequently, for example, after installation users of the Fedora Admin client will need write permissions to the log files defined by

...

config/logback.xml.

Quick Install

The quick option is designed to get Fedora up and running as quickly as possible, with a minimum of advanced options. The quick install will automatically install Tomcat pre-loaded with the Fedora Repository and the Derby database. Neither SSL support nor XACML policy enforcement is enabled by the quick install.

...

If you selected the quick install option, you will find Tomcat installed in FEDORA_HOME/tomcat. To run Fedora, start Tomcat by entering:

Code Block
language

...

none

$FEDORA_HOME/tomcat/bin/startup.sh

...


{panel}

(or for

...

 Windows)

{code:language=none}
%FEDORA_HOME%\tomcat\bin\startup.bat

...


If you selected the custom install option, ensure that your database server is running (unless you selected the included Derby option which will be automatically started when the first database connection is made).

...

To ingest the demonstration objects, at a command prompt, enter:

fedora-ingest-demos.sh 
\
[hostname
\
] 
\
[port
\
] 
\
[username
\
] 
\
[password
\
] 
\
[protocol
\
]
Code Block
Panel
languagenone

Wiki Markup

(or for Windows)

fedora-ingest-demos.bat 
\
[hostname
\
] 
\
[port
\
] 
\
[username
\
] 
\
[password
\
] 
\
[protocol
\
]
Code Block
languagenone

Panel
Wiki Markup

For additional information on the fedora-ingest-demos command, see the documentation for the Client Command-line Utilities. Please note that the demonstration objects must be ingested before they can be discovered using the default search interface.

...

To change the level to DEBUG for all Fedora classes, change the logger name="org.fcrepo" line to the following:

Code Block
borderStylesolid
<logger name="org.fcrepo" additivity="false" level="DEBUG">

To change the level to DEBUG for just one class, add the following lines:

Code Block
languagenone
log4j.logger.fedora.server.utilities.SQLUtility = DEBUG, FEDORA
log4j.additivity.fedora.server.utilities.SQLUtility = false

To change the level to DEBUG for a whole package, add the following lines:

Code Block
themeborderStyleMidnightsolid
<logger name="org.fcrepo.server.resourceIndex" additivity="false" level="DEBUG">
<appender-ref ref="FEDORA"/>