...
Both the quick and custom options will install the Fedora client software in addition to the Fedora server. The client option, however, will install only the Fedora client software.
Start Fedora
...
If you selected the quick install option, you will find Tomcat installed in FEDORA_HOME/tomcat
. To run Fedora, start Tomcat by entering:
Panel |
---|
$FEDORA_HOME/tomcat/bin/startup.sh |
Panel |
---|
"%FEDORA_HOME%\tomcat\bin\startup.bat" |
Installing the Demo Objects
If you just started Fedora for the first time, it's a good idea to check out the demonstration objects to get an idea of how Fedora works. See the Demonstration documentation for complete descriptions.
NOTE: If, during a custom install, you entered values other than the defaults for fedoraServerHost (localhost) or fedoraServerPort (8080), you must run the demo object converter utility script to change the host and/or port in the demonstration object ingest files. The demonstration object conversion is only required if you are ingesting demonstration objects. If the demonstration objects are already ingested into the repository (e.g. from a previous installation), there is no need for conversion. The demonstration objects are shipped with references to "localhost:8080" and these references must reflect the new values of fedoraServerHost fedoraServerPort. Refer to the Command-line Utilities documentation for additional details on running the demo object converter.
To ingest the demonstration objects, at a command prompt, enter:
Panel | ||
---|---|---|
|
(or for Windows)
Panel | ||
---|---|---|
|
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.
Further Configuration
...
The Fedora Server's configuration is chiefly governed by the Fedora Server Configuration File, fedora.fcfg
, located at FEDORA_HOME/server/config/fedora.fcfg
.
The Fedora server configuration file contains:
- Global parameters for the Fedora server
- Configuration parameters for each server module
- Configuration parameters for each persistent data store
The configuration file has a simple schema. It starts with a server element, under which a series of parameter elements occur, followed by a series of module elements, followed by a series of datastore
elements. The parameter elements directly following the root server element are used to control what are considered generic server functionality; for example: the port on which the server is exposed.
The module elements are used to configure specific parts of Fedora. For instance, the module with the role attribute fedora.server.search.FieldSearch
is used to configure the field-searching component of the server. Inside the module element, several param
elements are included. These are specific to that module's implementation. Descriptions of each parameter can currently be found in the configuration file itself.
The datastore
elements are used to configure various databases that might be used by the system. Although the sample configuration file holds several, you will typically only need one. The datastore
elements are associated with the modules by means of a parameter inside the associated module. In the sample configuration file, for example, the poolNames
parameter of the fedora.server.storage.ConnectionPoolManager
module refers to one of the datastore
elements in its value.
There are many other parameters you can configure with Fedora. Refer to the Fedora Server Configuration File itself (fedora.fcfg
) for internal documentation on all the parameters.
Logging
Fedora uses the Simple Logging Facade for Java (SLF4J) framework for logging with Logback as the actual logging implementation. For detailed information about using SLF4J, consult the SLF4J Manual: http://www.slf4j.org/manual.html, and for information about using Logback consult the Logback manual: http://logback.qos.ch/manual/index.html.
The log configuration file is located at FEDORA_HOME/server/config/logback.xml
. One of the benefits of using SLF4J and Logback is that configuration changes take effect without needint to restart the server.
Normally, coarse-grained logs for Fedora are written to FEDORA_HOME/server/logs/fedora.log
. The following examples show the kinds of configuration changes you can make to aid in debugging.
To change the level to DEBUG for all Fedora classes, change the logger name="org.fcrepo"
line to the following:
Panel |
---|
<logger name="org.fcrepo" additivity="false" level="DEBUG"> |
Panel |
---|
log4j.logger.fedora.server.utilities.SQLUtility = DEBUG, FEDORA |
...
Advanced Configuration
fedora.fcfg
Anchor | ||||
---|---|---|---|---|
|
The Fedora Server's configuration is chiefly governed by the Fedora Server Configuration File, fedora.fcfg
, located at FEDORA_HOME/server/config/fedora.fcfg
.
The Fedora server configuration file contains:
- Global parameters for the Fedora server
- Configuration parameters for each server module
- Configuration parameters for each persistent data store
The configuration file has a simple schema. It starts with a server element, under which a series of parameter elements occur, followed by a series of module elements, followed by a series of datastore
elements. The parameter elements directly following the root server element are used to control what are considered generic server functionality; for example: the port on which the server is exposed.
The module elements are used to configure specific parts of Fedora. For instance, the module with the role attribute fedora.server.search.FieldSearch
is used to configure the field-searching component of the server. Inside the module element, several param
elements are included. These are specific to that module's implementation. Descriptions of each parameter can currently be found in the configuration file itself.
The datastore
elements are used to configure various databases that might be used by the system. Although the sample configuration file holds several, you will typically only need one. The datastore
elements are associated with the modules by means of a parameter inside the associated module. In the sample configuration file, for example, the poolNames
parameter of the fedora.server.storage.ConnectionPoolManager
module refers to one of the datastore
elements in its value.
There are many other parameters you can configure with Fedora. Refer to the Fedora Server Configuration File itself (fedora.fcfg
) for internal documentation on all the parameters.
Logging
Fedora uses the Simple Logging Facade for Java (SLF4J) framework for logging with Logback as the actual logging implementation. For detailed information about using SLF4J, consult the SLF4J Manual: http://www.slf4j.org/manual.html, and for information about using Logback consult the Logback manual: http://logback.qos.ch/manual/index.html.
The log configuration file is located at FEDORA_HOME/server/config/logback.xml
. One of the benefits of using SLF4J and Logback is that configuration changes take effect without needint to restart the server.
Normally, coarse-grained logs for Fedora are written to FEDORA_HOME/server/logs/fedora.log
. The following examples show the kinds of configuration changes you can make to aid in debugging.
To change the level to DEBUG for all Fedora classes, change the logger name="org.fcrepo"
line to the following:
Panel |
---|
<logger name="org.fcrepo" additivity="false" level="DEBUG"> |
Panel |
---|
log4j.logger.fedora.server.utilities.SQLUtility = DEBUG, FEDORA |
Panel |
---|
<logger name="org.fcrepo.server.resourceIndex" additivity="false" level="DEBUG"> |
Installing the Demo Objects
If you just started Fedora for the first time, it's a good idea to check out the demonstration objects to get an idea of how Fedora works. See the Demonstration documentation for complete descriptions.
NOTE: If, during a custom install, you entered values other than the defaults for fedoraServerHost (localhost) or fedoraServerPort (8080), you must run the demo object converter utility script to change the host and/or port in the demonstration object ingest files. The demonstration object conversion is only required if you are ingesting demonstration objects. If the demonstration objects are already ingested into the repository (e.g. from a previous installation), there is no need for conversion. The demonstration objects are shipped with references to "localhost:8080" and these references must reflect the new values of fedoraServerHost fedoraServerPort. Refer to the Command-line Utilities documentation for additional details on running the demo object converter.
To ingest the demonstration objects, at a command prompt, enter:
Panel | ||
---|---|---|
|
(or for Windows)
Panel | ||
---|---|---|
|
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.