2010-02-03 15:09:52 +00:00
|
|
|
# -----------------------------------------------------------------------------
|
|
|
|
#
|
2011-05-02 14:34:20 +00:00
|
|
|
# VITRO deployment properties
|
2010-02-03 15:09:52 +00:00
|
|
|
#
|
|
|
|
# This file is provided as example.deploy.properties.
|
|
|
|
#
|
|
|
|
# Save a copy of this file as deploy.properties, and edit the properties as
|
|
|
|
# needed for your deployment.
|
|
|
|
#
|
|
|
|
# -----------------------------------------------------------------------------
|
|
|
|
|
2010-04-12 14:22:35 +00:00
|
|
|
#
|
|
|
|
# This namespace will be used when generating URIs for objects created in the
|
|
|
|
# editor. Change it to reflect your own domain. For example, Cornell's
|
|
|
|
# namespace is http://vivo.cornell.edu/individual/
|
|
|
|
#
|
|
|
|
# Note: it is essential that this namespace end with a trailing slash.
|
|
|
|
#
|
|
|
|
Vitro.defaultNamespace = http://vitro.mydomain.edu/individual/
|
|
|
|
|
2010-02-21 18:45:18 +00:00
|
|
|
#
|
2011-05-02 14:34:20 +00:00
|
|
|
# The base install directory for your Tomcat server. The Vitro application
|
2010-02-21 18:45:18 +00:00
|
|
|
# will be deployed in the /webapps directory below this base.
|
|
|
|
#
|
|
|
|
tomcat.home = /usr/local/tomcat
|
|
|
|
|
|
|
|
#
|
|
|
|
# The name of the Vitro application. This will be used as the name of the
|
|
|
|
# subdirectory within your Tomcat server's /webapps directory. It also appears
|
|
|
|
# in the URL for the application. For example, http://my.vitro.server/vitro
|
|
|
|
#
|
|
|
|
webapp.name = vitro
|
|
|
|
|
2010-02-03 15:09:52 +00:00
|
|
|
#
|
2011-05-02 14:34:20 +00:00
|
|
|
# The location where the Vitro application will store the data that it creates.
|
2011-07-13 15:19:52 +00:00
|
|
|
# This includes uploaded files (usually images) and the search index.
|
2010-02-03 15:09:52 +00:00
|
|
|
#
|
2011-05-02 14:34:20 +00:00
|
|
|
vitro.home.directory = /usr/local/vitro/data
|
2010-02-03 15:09:52 +00:00
|
|
|
|
|
|
|
#
|
2011-06-09 20:37:07 +00:00
|
|
|
# Email parameters which VIVO can use to send mail. If these are left empty,
|
|
|
|
# the "Contact Us" form will be disabled and users will not be notified of
|
|
|
|
# changes to their accounts.
|
2010-02-03 15:09:52 +00:00
|
|
|
#
|
2011-06-09 20:37:07 +00:00
|
|
|
email.smtpHost = smtp.my.domain.edu
|
|
|
|
email.replyTo = vivoAdmin@my.domain.edu
|
2010-02-03 15:09:52 +00:00
|
|
|
|
|
|
|
#
|
|
|
|
# The basic parameters for a MySQL database connection. Change the end of the
|
|
|
|
# URL to reflect your database name (if it is not "vitro"). Change the username
|
|
|
|
# and password to match the authorized user you created in MySQL.
|
|
|
|
#
|
|
|
|
VitroConnection.DataSource.url = jdbc:mysql://localhost/vitro
|
|
|
|
VitroConnection.DataSource.username = vitroweb
|
|
|
|
VitroConnection.DataSource.password = vitrovitro
|
|
|
|
|
2011-05-26 13:58:06 +00:00
|
|
|
#
|
|
|
|
# The maximum number of active connections in the database connection pool.
|
|
|
|
# Increase this value to support a greater number of concurrent page requests.
|
|
|
|
#
|
|
|
|
VitroConnection.DataSource.pool.maxActive = 40
|
|
|
|
|
|
|
|
#
|
|
|
|
# The maximum number of database connections that will be allowed
|
|
|
|
# to remain idle in the connection pool. Default is 25%
|
|
|
|
# of the maximum number of active connections.
|
|
|
|
#
|
|
|
|
VitroConnection.DataSource.pool.maxIdle = 10
|
|
|
|
|
|
|
|
#
|
|
|
|
# Parameters to change in order to use VIVO with a database other than
|
|
|
|
# MySQL.
|
|
|
|
#
|
|
|
|
VitroConnection.DataSource.dbtype = MySQL
|
|
|
|
VitroConnection.DataSource.driver = com.mysql.jdbc.Driver
|
|
|
|
VitroConnection.DataSource.validationQuery = SELECT 1
|
|
|
|
|
2011-04-11 17:21:38 +00:00
|
|
|
#
|
|
|
|
# The URL to connect to for the Solr service that is used by the application.
|
|
|
|
# The Solr service provides the application with full text search and many
|
|
|
|
# other features. If you leave this commented out the application will attempt to use
|
|
|
|
# the solr from the same tomcat server at the context ${webapp.name}solr
|
|
|
|
#
|
|
|
|
# vitro.local.solr.url =
|
|
|
|
|
2010-02-21 18:45:18 +00:00
|
|
|
#
|
2011-06-08 21:21:59 +00:00
|
|
|
# The email address of the root user for the VIVO application. The password
|
|
|
|
# for this user is initially set to "rootPassword", but you will be asked to
|
2011-01-14 19:38:23 +00:00
|
|
|
# change the password the first time you log in.
|
2010-02-21 18:45:18 +00:00
|
|
|
#
|
2011-06-08 21:21:59 +00:00
|
|
|
rootUser.emailAddress = root@myDomain.com
|
2010-12-14 21:58:01 +00:00
|
|
|
|
|
|
|
#
|
|
|
|
# How is a logged-in user associated with a particular Individual? One way is
|
|
|
|
# for the Individual to have a property whose value is the username of the user.
|
|
|
|
# This is the name of that property.
|
|
|
|
#
|
2011-05-02 14:34:20 +00:00
|
|
|
selfEditing.idMatchingProperty = http://vitro.mydomain.edu/ns#networkId
|
2010-12-14 21:58:01 +00:00
|
|
|
|
|
|
|
#
|
|
|
|
# If an external authentication system like Shibboleth or CUWebAuth is to be
|
|
|
|
# used, these properties say how the login button should be labeled, and which
|
|
|
|
# HTTP header will contain the user ID from the authentication system. If such
|
|
|
|
# as system is not to be used, leave these commented out. Consult the
|
|
|
|
# installation instructions for more details.
|
|
|
|
#
|
|
|
|
#externalAuth.buttonText = Log in using BearCat Shibboleth
|
|
|
|
#externalAuth.netIdHeaderName = remote_userID
|