Spring Context
The Spring main application context is /WEB-INF/classes/application-context.xml which is optionally overridden by properties loaded in /WEB-INF/classes/application.properties.
Since most configuration can be done from configuration properties (see below) and can be overridden by the JNDI bindings, usually there is no need to edit these files directly to configure the itracker application.
JNDI Context
Some JNDI environment resources are configured from the container running the itracker webapp. The lookup names are found in application.properties.
-
Configurable configurationServiceTarget.jndiPropertiesOverridePrefix from WEB-INF/classes/application.properties,
useful for overriding values in configuration.properties from java:comp/env/itracker.
eg. override system_base_url value with java:comp/env/itracker/system_base_url using the web.xml or context.xml. - Datasource (database connection): java:comp/env/itracker/itracker_ds (see also dataSource.jndiName in application.properties and datasource.xml)
- DB Dialect (hibernate dialect): java:comp/env/itracker/db_dialect (see also db_dialect.defaultObject in application.properties and datasource.xml)
-
Mailsession (notifications, password, ..)):
java:comp/env/itracker/mail/Session
You can also override the lookup name by setting configurationServiceTarget.mailSessionLookupName but usually you want to rather configure a mail-session accordingly for your web context.
Configuration Properties
There are some properties which you're able to configure for your itracker ( classpath:configuration.properties ) or override the properties with env-entries under java:comp/env/itracker/
-
system_base_url
: This property can be used to override the url determined
dynamically
by the system when a user submits an issue or self registers. This
is mainly due to some users using private domain names that wouldn't
be accessible to all recipiants of a notification email. This
property is only used to create urls in emails sent to all users.
default: http://localhost:8080/itracker -
web_session_timeout
This property can be used to set the web session inactivity
timeout. This number is the number of minutes that can elapse
before the users
session times out due to inactivity.
default: 30 minutes -
site_logo
Set this if you wish to use an alternate image logo in the header
of all
pages. It must be a resolvable absolute path to the context-root. (type : String)
default: shows no logo (null) -
site_title
Set this if you wish to use an alternate site title in the header
of all pages.
default: itracker.org -
available_locales
Comma-separated list of available locales to the frontend.
default: current default_locale from the configuration -
default_locale
Set to the default locale of the server. This controls the default
language
for users after they are logged in, and also the language of the login
page before they are logged in. This HAVE TO be in the format
language_country (eg. en_US, de_DE, pt_PT, it_IT) (type : String)
default: en_US -
create_super_user
Set to true to create a default admin user if no other users exist
in the
database (type : Boolean)
default: true -
allow_forgot_password
Set to true to allow users to recover their passwords (type :
Boolean)
default: true -
allow_self_register
Set to true to allow users to self register for your sever. This is
a global
setting that must be enabled for the project level options to be
effective. If enabled, you must then go into each project you want
accessible to self registered
users, and which permissiosn you want. Currently only create and view all
are
available (view own is automatically granted), if you want other
permissions, you
must grant them using the normal user administration procedures. (type
: Boolean)
default: true -
allow_save_login
Set to true to allow users to save their login in a cookie on their
machine
for auto login. Setting this to false will not allow any user on the
system
to use this feature. (type : Boolean)
default: true -
save_login_key
The "key" used to identify cookies from a specific token-based
remember-me application.
default: itracker - save_login_timeout The period (in seconds) for which the remember-me cookie should be valid. default: 2592000 (30 days)
-
allow_workflowscripts
Set to false to deny execution of workflowscripts for the system.
Be sure that your system is protected against injection of
malicious scripts when enabled. (type : Boolean)
default: true -
reminder_notification_days
Defines the number of days after which issue reminder notifications will
be sent.
Set to 0 to disable reminder notifications. (type : Integer)
default: 30
To configure when reminders are sent, see application.properties reminder_cron.defaultObject -
authenticator_class
This parameter sets the class to use for authentication.
The class must be resident in the classpath that the ear is loaded in,
and extend the org.itracker.services.authentication.PluggableAuthenticator
abstract class. (type : String)
default: Default-Authenticator -
max_attachment_size
The maximum size of an individual issue attachment in kb.
default: 512 -
max_total_attachment_size
The maximum total size of all attachments in kb.
default: 100000 -
notification_from_address
Deprecated: From address for email notifications to use, if not set,
the mail-session default (mail.from) value will be used.
default: mail.from as defined in mail-session -
notification_from_text
Deprecated: From address text for email notifications to use
default: ITracker Notification System -
notification_replyto_address
Deprecated: ReplyTo address for email notifications to use, if not set,
the notification_from_address value will be used.
default: mail.from as defined in mail-session -
notification_smtp_host
Deprecated: SMTP hostname for email notifications to use
default: localhost -
notification_smtp_charset
Deprecated: SMTP notificate character set. You might need to change this for
some locales
default: the mail-session mail.mime.charset -
notification_smtp_password and
notification_smtp_userid
Deprecated: SMTP authentication userid and password if required by
your application server
it is recommended to use a mail-session instead, only use this for fallback support. -
pdf.export.fonts
Fonts which will be included in exported PDFs, they are used from Jasper reports.
your application server
Fonts are looked up in classpath: /fonts/#name#.ttf