Rapporto Tecnico, Anno 7, n° 42 maggio 2012

<param name="fedora-system:2" value="org.fcrepo.server.access.internalservices.BootstrapImpl">
<comment>The class that implements the methods of the bootstrap
disseminator. These method implementations are "built-in" to the
Fedora system, and are dynamically associated with every behavior
definition and behavior mechanism object. This class can be thought
of as implementing an "internal service" whereas other disseminators
use external services (described by WSDL) to do their work.</comment>
</param>
<param name="fedora-system:3" value="org.fcrepo.server.access.defaultdisseminator.DefaultDisseminator">
<comment>The interface that defines the methods of the default
disseminator. These methods are "built-in" to the Fedora system, and
are dynamically associated with every object.</comment>
</param>
<param name="fedora-system:4" value="org.fcrepo.server.access.defaultdisseminator.DefaultDisseminatorImpl">
<comment>The class that implements the methods of the default
disseminator. These method implementations are "built-in" to the
Fedora system, and are dynamically associated with every object.
This class can be though of as implementing an "internal service"
whereas other disseminators use external services (described by
WSDL) to do their work.</comment>
</param>
</module>
<module role="org.fcrepo.server.search.FieldSearch" class="org.fcrepo.server.search.FieldSearchSQLModule">
<comment>Supports the API-A simpleSearch and advancedSearch methods.</comment>
<param name="indexDCFields" value="true">
<comment>(optional, default is true) Whether the content of the DC
datastream should be examined and the contents indexed, for each object.
You may wish to save time and space by disabling DC field indexing,
particularly if you have an external search service (such as Fedora
Generic Search) that already fulfills this need.
Note: If you change this value on a Fedora repository that has been
running for some time, you will need to perform a SQL rebuild using the
Fedora Rebuilder tool if you want to change objects that have already
been ingested.</comment>
</param>
<param name="connectionPool" value="localMySQLPool">
<comment>(optional) To make unspecified, comment out or delete the
whole param line as opposed to using an empty string,
default=ConnectionPoolManager's default) The connectionPool
providing the connection to the database to be used. Warning: When
setting these values, keep in mind that while a session is not timed
out (maxSecondsPerSession seconds haven't elapsed, and not all
results have been requested), a connection from the pool is tied up.
Therefore, the connectionPool should be at least of size n, large
enough to accomodate n simultaneous search sessions. The longer
maxSecondsPerSession is, the more chance you have of tying up all
available connections from the pool. Therefore, keep
maxSecondsPerSession fairly low, but still reasonable for an
automated program or user to serially get a long list of results,
and make sure you have a connectionPool large enough to accomodate
your users.</comment>
</param>
<param name="maxSecondsPerSession" value="500">
<comment>(required, must be &gt; 0)
The maximum number of seconds that the server guarantees subsequent
search results may be obtained. This is only used in cases where the
number of results is greater than maxResults (as specified by the
server [above] or the client [in the search request]).</comment>
</param>
<param name="maxResults" value="100">
<comment>(required, must be &gt; 0)
The maximum number of records to
return as the result of a search. Even if a client requests more
results at a time, this is the cutoff value.</comment>
</param>
</module>
<module role="org.fcrepo.server.resourceIndex.ResourceIndex"
class="org.fcrepo.server.resourceIndex.ResourceIndexModule">
<comment>Supports the ResourceIndex.</comment>
<param name="level" value="1">
<comment>(required)
Index level. Currently, only 0, and 1 are supported levels.
0 = off and 1 = on.
WARNING: changing the level (except to 0) requires
running the Resource Index Rebuilder.</comment>
</param>
<param name="syncUpdates" value="false">
<comment>(optional, default is false)
Whether to flush the triple buffer before
returning from object modification operations.
Specifying this as true will ensure that RI queries
immediately reflect the latest triples.
Specifying false will not provide this guarantee,
but can significantly reduce roundtrip time for
API-M operations (depending on the triplestore
implementation).</comment>
</param>
<param name="datastore" value="localMulgaraTriplestore">
<comment>(required)
Name of the triplestore to use. WARNING: changing the
triplestore running the Resource Index Rebuilder.</comment>
</param>
<param name="alias:test" value="http://example.org/terms#">
<comment>(optional) Aliases that can be used for queries. The param
name of an alias starts with the string "alias:" and is followed by
the name of the alias (shortcut) for the value, which is a URI

53