Configuration

Configuration variables

Property Name	Property Value	*Comments
lr.dspace.hostname	The url of your dspace instance. e.g. ufal-point-dev.ms.mff.cuni.cz	DSpace host name - should match base URL. Do not include protocol i.e. http or https and do not include port, this is only the name of server. Also do not use localhost because using this property some external links will be generated
lr.dspace.baseUrl	The base URL of the dspace instance. e.g. http://ufal-point-dev.ms.mff.cuni.cz:8080/$DSPACE_INSTANCE_NAME	DSpace base URL. the full url of the instance
lr.database	Name of the database	The name of the database that you will use for your dspace instance. If the database is not created yet, this name will be used to create the new database. Be careful with the trailing spaces in the name!
lr.db.username	User name to connect to database	This user should have read/write permissions on your database
lr.db.password	Password of the given user	Don't write the password in any other file and don't commit this local.conf file to remote repository
lr.utilities.database	Name of the utilities database
lr.dspace.dir	The installation directory of your instance
lr.solr.log.server	Solr server address that your instance is using e.g. http://ufal-point-dev.ms.mff.cuni.cz:8080/$DSPACE_INSTANCE_NAME/solr
lr.help.mail
lr.mail.from.address
lr.ga.analytics.key.file	Path to the Google Analytics API key file	Make sure to copy the real API key file to this location upon first installation
lr.ga.analytics.account.email
lr.info.recipient
lr.feedback.recipient
lr.errors.email	Email where errors logged from specific loggers will be sent.	If you will not use this feature, update dspace.cfg and set this variable to an empty string.

Note: Please change all the emails to proper unique email addresses for your DSpace instance to avoid any conflicts with other instances.

Also check all remaining variables, see notes below::

Property Name	Property Value	Comments
ufal.handleserver	local or epic	local uses the local handle server will ignore the pid service settings and epic uses the epic pid service
ufal.db.name	Name of the RDBMS	This is not the name of the database you are using. Instead the name of the RDBMS used e.g. postgres or oracle. This is required for database creation scripts.
ufal.db.url	Connection URL of the database for postgres use jdbc:postgresql://localhost:5432/${ufal.database}	Make sure you are using the correct port and if you are connecting to remote server, verify that the port is accessible. Do not change the ${ufal.database}, the database name will be substituted from above property.
ufal.db.driver	The database driver you are using. For postgres it is org.postgresql.Driver	Make sure that the required jars are available. In our case the jars are part of UFAL Utilities
ufal.utilities.db.url	Connection URL of the utilities database use jdbc:postgresql:${ufal.utilities.database}
ufal.dspace.version	Version of the dspace instance	You can use this value to append version with other values. Currently we are not using this property
ufal.dspace.name	A description of your dspace instance	it will be used as a description of your dspace instance for other services
ufal.utilities.dir	${dspace.dir}/utilities	Leave it as it is.
ufal.utilities.functionalitymanager.class	cz.cuni.mff.ufal.lindat.utilities.FunctionalityManager	You can provide your own implementation of FunctionalityManager and change the class name here
ufal.mail.server	Mail server address	you can use 127.0.0.1, if configured on localhost
ufal.solr.log.server	Provide the solr server address that your instance is using.	Make sure to add the entry of your solr application in tomcat server.xml. If the solr server is only accessible through localhost, use the appropriate local host address.
ufal.replication.*	Ask EUDAT for the credentials to an IRODS server.	If you will not use this feature, update dspace.cfg and set these variables to empty strings.
The rest of the configuration is self explanatory.