Dear Mr. Ronda,
I deleted the complete installation of fedora
server, client and src development. And reinstalled the fedora. As per the
instrunction, I did ant serverdist process from c:\fedora-1.2-src directory
(FEDORA_DEV directory). Then I initialised the McKoi databsae from C:\ directory
by following command:
got message DBInstalled and finished.
<?xml version="1.0"
encoding="UTF-8"?>
<server
xmlns="http://www.fedora.info/definitions/1/0/config/"
xmlns:fedora-config="http://www.fedora.info/definitions/1/0/config/"
class="fedora.server.BasicServer">
<param name="repositoryName"
value="Fedora Repository 1"/>
<comment>Defines a human
readable name for the Fedora server; default is Fedora
Repository.</comment>
<param name="adminEmailList"
value="rajesh <at> inflibnet.ac.in"/>
<comment>Defines
one or more email addresses for server administrators; list is space
delimited.</comment>
<param name="adminPassword"
value="fedoraAdmin"/>
<comment>Defines the password for the
Fedora server; default is fedoraAdmin.</comment>
<param
name="log_max_size" value="5242880"/>
<comment>Defines the
threshold at which a new log file is generated based on the size of the current
log file in bytes; default is 5242880 bytes.</comment>
<param
name="log_max_days" value="7"/>
<comment>Defines the threshold
at which a new log file is generated based on number of days since the server
was started in days; default is 7 days.</comment>
<param
name="log_dir" value="logs"/>
<comment>Defines the directory
in which the Fedora logs will be written; default is
logs.</comment>
<param name="log_level"
value="finest"/>
<comment>Defines the level of logging
desired;default is finest; possible levels include:
-
config
denotes logging indicating what occurred during the
server's (or a module's) configuration phase.
-
fine
denotes logging indicating basic information about a
request to the server (like hostname, operation name, and success or
failure).
- finer
denotes logging
indicating detailed information about a request to the server (like the full
request, full response, and timing information).
- finest
(deafult)
denotes logging indicating method entry/exit or
extremely verbose information intended to aid in debugging.
-
info
denotes logging indicating that something relatively
uncommon and interesting happened, like server or module startup or shutdown, or
a periodic job.
- warning
denotes logging
indicating that an undesired (but non-fatal) condition occured.
- severe
denotes logging indicating that
the server is inoperable or unable to
start.
</comment>
<param name="log_flush_threshold"
value="1"/>
<comment>Defines the flush threshold for logging
in number of records; default is one log
record.</comment>
<param name="path_algorithm"
value="fedora.server.storage.lowlevel.TimestampPathAlgorithm"/>
<comment>Defines
the java class used to determine the path algorithm for LowLevelStorage;
default is
fedora.server.storage.lowlevel.TimestampPathAlgorithm.
</comment>
<param
name="file_system"
value="fedora.server.storage.lowlevel.GenericFileSystem"/>
<comment>Defines
the java class that determines the type of implementation for LowLevelStorage;
default is
fedora.server.storage.lowlevel.GenericFileSystem.
</comment>
<param
name="registry"
value="fedora.server.storage.lowlevel.DBPathRegistry"/>
<comment>Defines
the java class used to determine the path registry for LowLevelStorage;
default is
fedora.server.storage.lowlevel.DBPathRegistry.
</comment>
<param
name="backslash_is_escape" value="yes"
oraclevalue="no"/>
<comment>Defines whether the backing
database (which include registry tables) the backslash
character
to be the escape character (token beginning an escape
sequence). This is needed to correctly
store and retrieve
filepaths from the registry tables, if running under
Windows/DOS.
</comment>
<param
name="object_store_base"
value="C:\fedora1_2_objects"/>
<comment>Defines the root
directory for the internal storage of Fedora objects.
This value
should be adjusted based on your installation environment;
default assumes a Windows installation of
C:\fedora1_2_objects.
</comment>
<param
name="temp_store_base"
value="C:\fedora1_2_temp"/>
<comment>Defines the root
directory for Fedora temporary storage.
This value should be
adjusted based on your installation environment;
default assumes
a Windows installation of
C:\fedora1_2_temp.
</comment>
<param
name="datastream_store_base"
value="C:\fedora1_2_datastreams"/>
<comment>Defines the root
directory for the internal storage of Managed Content datastreams.
This value should be adjusted based on your installation
environment;
default assumes a Windows installation of
C:\fedora1_2_datastreams.
</comment>
<param
name="debug" value="false"/>
<comment>A boolean toggle used to
turn off/on internal debugging in the code.</comment>
<param
name="datastreamExpirationLimit"
value="300"/>
<comment>
Controls the size of
the datastream mediation hash by removing entries outside the specified
threshold.
The value is specified in
seconds.
Note this value must be greater than the limit specified
for the datastreamMediationLimit.
</comment>
<param
name="datastreamMediationLimit"
value="5000"/>
<comment>
Determines the time
interval in which external mechanisms must respond to requests by the Fedora
server.
The value is specified in
milliseconds.
The value specified should be set high enough
to allow for an average response time from any single external
mechanisms.
Note this value must be less than the limit specified
for the datastreamExpirationLimit.
</comment>
<param
name="fedoraServerPort" value="8080"/>
<comment>Defines the
port number on which the Fedora server runs; default is
8080.</comment>
<param name="fedoraShutdownPort"
value="8005"/>
<comment>Defines the port number used to
shutdown the Fedora sever; default is 8005.</comment>
<param
name="fedoraRedirectPort" value="8443"/>
<comment>Defines the
redirect port of the Fedora sever; default is
8443.</comment>
<param name="fedoraServerHost"
value="192.168.1.15"/>
<comment>Defines the host name for the
Fedora server, as seen from the outside
world.</comment>
<module
role="fedora.server.storage.DOManager"
class="fedora.server.storage.DefaultDOManager">
<comment>
Description:
The
interface to the storage subsystem. This
provides
context-appropriate DOReaders and DOWriters for reflecting on and
writing to the
objects stored in the repository. It
also
provides methods
for reflecting on the contents of the repository
as a whole.
This implementation uses
DefinitiveDOReader/Writer
for an "application" of "apim" and a
FastDOReader/Writer
for an "application" of "apia" (from the Context).
Other
context-specific
logic TBD.
Parameters:
- pidNamespace
(required)
This is the
namespace id for pids of newly-created
objects.
This should
be unique for a
repository.
It can be
from 1 to 17 characters, and may only
contain
A-Z, a-z, 0-9,
and '-' (dash).
- retainPIDs
[default="demo test"]
Namespaces of PIDs to retain during the ingest
process.
When an
object is ingested, Fedora normally allocates a unique
PID
within
pidNamespace for it regardless of what the object says its
PID is. This
option provides a way to override that behavior
on
a per-pid-namespace
basis. If specified, this should be a
space-delimited list
of pid namespaces that will be accepted in the
object
as-is.
- storagePool
[default=default provided by the
ConnectionPoolManager]
The named connection pool from which
read/write
database
connections are to be provided for the
storage
subsystem (see
the ConnectionPoolManager module)
- storageFormat
(required)
The format
in which internal serializations of digital
objects
are to be
written. There must exist a
correspondingly
named
serializer-deserializer pair in the DOTranslator
module.
- storageCharacterEncoding
[default=UTF-8]
If the
serialization format is text-based,
this is the character
encoding that should be
used.</comment>
-
exportFormat
(required)
The format
in which external serializations of digital
objects
are to be
written. There must exist a
correspondingly
named
serializer-deserializer pair in the DOTranslator
module.
<param name="pidNamespace"
value="111"/>
<param name="retainPIDs" value="demo test
changeme"/>
<param name="storagePool"
value="localMySQLPool" mckoivalue="localMcKoiPool"
oraclevalue="localOracle9iPool"/>
<param
name="storageFormat" value="metslikefedora1"/>
<param
name="exportFormat" value="metslikefedora1export"/>
<param
name="storageCharacterEncoding"
value="UTF-8"/>
</module>
<module
role="fedora.server.management.Management"
class="fedora.server.management.DefaultManagement">
<comment>
Description:
The
management subsystem.
This implements the methods necessary to fulfill API-M
requests without
regard to:
- how the service is
exposed
-
how bytestreams and java types might be marshalled/demarshalled
over the
wire
- how
the storage subsystem is
implemented.
Parameters:
- allowHosts (optional...to make unspecified, comment out or delete the whole
param line as opposed to using an empty
string)
A comma-separated list of IP ranges that the client's address
is compared to. If this is specified, the remote address
must match for any Management request to be accepted.
If this is not specified, all requests will be accepted unless
the remote address matches a deny
pattern.
-
denyHosts (optional...to make unspecified, comment out or delete the whole param
line as opposed to using an empty
string)
A comma-separated list of IP ranges that the client's address
is compared to. If this is specified, the remote address
must not match for any Management request to be accepted.
If this is not specified, request acceptance is governed
solely by the allowHosts
parameter.
</comment>
<param name="allowHosts"
value="192.168.1.1-192.168.1.255"/>
</module>
<module
role="fedora.server.access.Access"
class="fedora.server.access.DefaultAccess">
<comment>
Description:
The
access subsystem.
This
implements the methods necessary to fulfill
API-A
requests without
regard to:
- how the service is
exposed
-
how bytestreams and java types might be marshalled/demarshalled
over the
wire
- how
the storage subsystem is
implemented.
Parameters:
- allowHosts (optional...to make unspecified, comment out or delete the whole
param line as opposed to using an empty
string)
A comma-separated list of IP ranges that the client's address
is compared to. If this is specified, the remote address
must match for any Management request to be accepted.
If this is not specified, all requests will be accepted unless
the remote address matches a deny
pattern.
-
denyHosts (optional...to make unspecified, comment out or delete the whole param
line as opposed to using an empty
string)
A comma-separated list of IP ranges that the client's address
is compared to. If this is specified, the remote address
must not match for any Management request to be accepted.
If this is not specified, request acceptance is governed
solely by the allowHosts
parameter.
- doMediateDatastreams
(required)
A boolean switch indicating whether Datastream Mediation is activated or
not.
Datastream Mediation provides additional repository security by not exposing
the actual physical location of Referenced Content datastreams to external
mechanisms(services). Instead of exposing the actual physical location of
Referenced Content datastreams , Datastream Mediation functions as a proxy
requiring all external services to communicate through the Fedora server to
resolve the location of Referenced Content datastreams. For Datastream
Mediation to function, the Fedora server must be internet accessible on its
designated port by any potential external service. This requirement can be
difficult to satisfy if the Fedora server is located behind a firewall and
you do not have ready access to the firewall's configuration to enable the
required access. If the Fedora server is behind a firewall and you have no
access to the firewall's configuration, you can disable Datastream Mediation
which will allow external services to access Referenced Content datastreams
using their actual physical locations. Managed Content and XMLMetadata
datastreams are stored internally in the Fedora repository and can only be
accessed through the Fedora server so disabling Datastream Mediation has no
effect on these types of datastreams. Disabling Datastream Mediation exposes
the physical location of Referenced Content datastream to external
services
which can result in unintended access to the raw datastreams by
surreptitious
external mechanisms. It is recommended that Datastream Mediation be disabled
only for testing or cases where this security issue is not a concern. The
default value of doMediateDatastreams is
true.
</comment>
<param name="doMediateDatastreams"
value="false"/>
</module>
<module
role="fedora.server.access.DynamicAccess"
class="fedora.server.access.DynamicAccessModule">
<comment>
Description:
The
dynamic behavior module for the access
subsystem.
This
implements the methods necessary to fulfill
API-A
requests without
regard
to:
- dynamically associating a default behavior definition and mechanism with
objects
-
(Future) dynamically associating other behavior definitions and mechanisms with
objects
-
running disseminations of dynamic
behaviors
Parameters:
-
fedora-system:1
The interface that defines the methods of the
bootstrap
disseminator. These methods are "built-in" to the
Fedora
system, and are dynamically associated with every
behavior definition and behavior mechanism
object.
-
fedora-system:2
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 though of as
implementing
an "internal service" whereas other disseminators
use
external services (described by WSDL) to do their
work.
-
fedora-system:3
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.
-
fedora-system:4
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 name="fedora-system:1"
value="fedora.server.access.internalservices.Bootstrap"/>
<param
name="fedora-system:2"
value="fedora.server.access.internalservices.BootstrapImpl"/>
<param
name="fedora-system:3"
value="fedora.server.access.internalservices.DefaultBehavior"/>
<param
name="fedora-system:4"
value="fedora.server.access.internalservices.DefaultBehaviorImpl"/>
</module>
<module
role="fedora.server.search.FieldSearch"
class="fedora.server.search.FieldSearchSQLModule">
<comment>
Description:
Supports
the API-A simpleSearch and advancedSearch
methods.
Parameters:
-
maxResults (required, must be >
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.
-
maxSecondsPerSession (required, must be >
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])
-
connectionPool (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 name="maxResults"
value="100"/>
<param name="maxSecondsPerSession"
value="100"/>
<param name="connectionPool"
value="localMySQLPool" mckoivalue="localMcKoiPool"
oraclevalue="localOracle9iPool"/>
</module>
<module
role="fedora.oai.OAIProvider"
class="fedora.server.oai.FedoraOAIProviderModule">
<comment>
Description:
Exposes
the repository for OAI
harvesters.</comment>
Parameters:
-
repositoryName
(required)
The name of the repository, to be given to OAI
harvesters.
-
repositoryDomainName
(required)
The domain name of the repository, which helps to uniquely
identify
items from the repository in OAI-PMH
requests. This should just
be the domain name of the
organization that exposes the objects.
More information on
the OAI identifier syntax can be found at
http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm
- adminEmails
(required)
One or more space-separated email addresses, to be given to OAI
harvesters.
- friends
(optional...to make unspecified, comment out or delete the whole param line as
opposed to using an empty
string)
A
space-separated list of URLs to known OAI provider
baseURLs.
This is OAI's provider discovery enabler. Harvesters can use these to
crawl OAI providers.
-
maxRecords (optional...to make unspecified, comment out or delete the whole
param line as opposed to using an empty string, default=FieldSearch:maxResults,
imposed
maximum=FieldSearch:maxResults)
The maximum number of results to return at a time for ListRecords
requests.
- maxHeaders
(optional...to make unspecified, comment out or delete the whole param line as
opposed to using an empty string, default=FieldSearch:maxResults, imposed
maximum=FieldSearch:maxResults)
The maximum number of results to return at a time for ListIdentifiers
requests.
<param name="repositoryName" value="INFLIBNET
Digital Repository System"/>
<param
name="repositoryDomainName" value="rajesh.lo"/>
<param
name="adminEmails"
value="rajesh <at> inflibnet.ac.in"/>
<param
name="friends" value="http://arXiv.org/oai2
http://memory.loc.gov/cgi-bin/oai2_0"/>
<param
name="maxRecords" value="100"/>
<param name="maxHeaders"
value="100"/>
</module>
<module
role="fedora.server.storage.translation.DOTranslator"
class="fedora.server.storage.translation.DOTranslatorModule">
<comment>Supports
translation from DigitalObject to a stream of
some format, and
vice-versa. The parameters below specify
serializer/deserializer classes
to be used for a given format.
Those classes must implement the
DOSerializer/DODeserializer
interfaces.
</comment>
<param name="serializer_metslikefedora1"
value="fedora.server.storage.translation.METSLikeDOSerializer"/>
<param
name="deserializer_metslikefedora1"
value="fedora.server.storage.translation.METSLikeDODeserializer"/>
<param
name="serializer_metslikefedora1export"
value="fedora.server.storage.translation.METSLikeExportDOSerializer"/>
<param
name="deserializer_metslikefedora1export"
value="fedora.server.storage.translation.METSLikeDODeserializer"/>
</module>
<module
role="fedora.server.management.PIDGenerator"
class="fedora.server.management.BasicPIDGenerator">
<comment>The
pid generator.</comment>
<param name="pidgen_log_dir"
value="pidgen"/>
</module>
<module
role="fedora.server.storage.replication.DOReplicator"
class="fedora.server.storage.replication.DefaultDOReplicator">
<comment>Supports
synching data from definitive storage with
dissemination
db.</comment>
</module>
<module
role="fedora.server.storage.ConnectionPoolManager"
class="fedora.server.storage.ConnectionPoolManagerImpl">
<comment>This
module facilitates obtaining
ConnectionPools</comment>
<param name="defaultPoolName"
value="localMySQLPool" mckoivalue="localMcKoiPool"
oraclevalue="localOracle9iPool"/>
<param name="poolNames"
value="localMySQLPool" mckoivalue="localMcKoiPool"
oraclevalue="localOracle9iPool"/>
</module>
<module
role="fedora.server.validation.DOValidator"
class="fedora.server.validation.DOValidatorModule">
<comment>
Description:
Supports validation of digital objects, including XML Schema
validation (to METS schema),
Schematron validation (to Fedora
Rules schema written in Schematron language), and (in future) other programatic
validation
including referential integrity checking of existence
and availability of distributed data and/or services.
Parameters:
- tempDir (required): this is a
directory that the validation module can use as a work space, as when it
must
write a temporary file.
-
xmlSchema: this is local path for the Fedora-METS XML schema used to do XML
schema validation of digital objects
-
schematronPreprocessor: this is the local path to the "skeleton" style
sheet for schematron processing
- schematronSchema:
this is the local path to the Fedora Schematron Schema used to do
Fedora-specific validation of digital objects.
This schema
expresses integrity rules which are not covered by the Fedora-METS XML
schema.
</comment>
<param name="tempDir"
value="work"/>
<param name="xmlSchema"
value="xsd/mets-fedora-ext.xsd"/>
<param
name="schematronPreprocessor"
value="schematron/preprocessor.xslt"/>
<param
name="schematronSchema"
value="schematron/fedoraRulesExt.xml"/>
</module>
<module
role="fedora.server.storage.ExternalContentManager"
class="fedora.server.storage.DefaultExternalContentManager">
<comment>This
module facilitates obtaining external content via
HTTP
Parameters:
- userAgent (optional...to make unspecified, comment out or delete the whole
param line as opposed to using an empty string, default=Fedora): How to identify
the
Fedora server in HTTP requests. This defaults to
something
reasonable, but if you want to provide more
information
(such as an admin email address) in the User-Agent
HTTP
request header, put it
here.
</comment>
</module>
<module
role="fedora.server.utilities.ThreadMonitor"
class="fedora.server.utilities.ThreadMonitorModule">
<comment>Prints
basic information about the running threads to the
log
periodically for diagnostic purposes.
still I got same problem Servlet engine and
ConnectionPoolNotFoundException. Please guide.
Whe I stop the fedora server. It gets stop.
but when I go to stop the McKoi database it gets me following
error:
at
com.mckoi.database.jdbc.TCPStreamDatabaseInterface.ConnectToDatabase: Unknown
Source
Finished.
For your kind information. I am using Windows
2000 Advanced Server with ServicePack 1.
RSS Feed