Date: Thu, 28 Mar 2024 07:55:30 -0400 (EDT) Message-ID: <400759075.27600.1711626930603@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_27599_246117914.1711626930602" ------=_Part_27599_246117914.1711626930602 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Although deploying Fedora 4 is as easy as downloading the WAR file and c= opying to your servlet container's webapps directory, this document details= the process.
The Fedora 4 Authentication (AuthN) and Authorization (AuthZ) framework = is designed to be flexible and extensible, to allow any organization to con= figure access to suit its needs.
To support horizontal scalability use cases as well as geographic distri= bution, Fedora 4 can be configured as a cluster of application servers.
Fedora 4 is instrumented using Metrics http://metrics.codahale.com/. The= se metrics are exposed via JMX http://www.oracle.com/technetwork/java/javas= e/tech/javamanagement-140525.html and an HTTP API. All REST API operations = track timing and histogram information. Key internal API methods are also i= ncluded. Modeshape http://modeshape.jboss.org and Infinispan http://infinis= pan.org include their own metrics reporting over JMX.
This guide will help you setup the OAI-PMH provider for Fedora 4 on Tomc= at 7. For further details, please refer to the project's documentation on G= itHub https://github.com/fcrepo4-labs/fcrepo4-oaiprovider.
The Fedora community has conducted a number of performance tests. The de= tails of each test, including testing parameters and results, are included = in the following sections.