The configuration file (config.properties) is used to configure the behaviour of the application at runtime.
Using config.properties
From 3.30
An exhaustive list of those properties can be found in the config.properties.example file from sources.
Prior 3.30
The configuration file /properties/config.properties is used to configure the behaviour of the application at runtime. An exhaustive list of those properties can be found in the distributed file /properties/config.properties.
Configure esup-helpdesk online!
Go to http://www.esup-portail.org/helpdesk-config in order to generate the configuration files interactively!
Note for developers
Other properties can be added to the configuration file /properties/config.properties and used and the Spring configuration files.
Recovering the configuration when upgrading
The configuration file /properties/config.properties is automatically recovered from previous versions when upgrading (see Recovering previous configuration and customizations when upgrading).
Configuring the application
Excepted when indicated, all the properties are optional ( icons mark the parts where properties are required).
- Configuring the database connection
- Configuring the authentication
- Configuring exception handling
- Configuring the data initialization
- Configuring the LDAP access
- Configuring portal information access
- Configuring outgoing email
- Configuring the initial properties of departments
- Configuring the initial properties of managers
- Configuring the default ticket priority
- Configuring the default ticket visbility
- Configuring the default FAQ visibility
- Configuring the automatic ticket assignment
- Configuring user profile retrieval
- Configuring the storage of attached files
- Configuring indexing
- Configuring ticket expiration and archiving
- Configuring URL generation
- Configuring email feeding
- Configuring the web services
Testing the configuration
Once the application configured, it is possible to test the configuration by running the ant tasks test-database, test-ldap, test-portal, test-smtp and test-user-info.
If no error is detected, it is time to initialize the data and start the application (see 03 Administration).