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*.
{note:title=Configure esup-helpdesk online!}{color:red}{*}Go to *{color}{color:red}*[http://www.esup-portail.org/helpdesk-config]*{color} {color:red}{*}in order to generate the configuration files interactively\!*{color}
{note}
{tip:title=Note for developers}Other properties can be added to the configuration file */properties/config.properties* and used and the Spring configuration files.
{tip}
{tip:title=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]).
{tip}
h1. Configuring the application
Excepted when indicated, all the properties are optional ((*y) icons mark the parts where properties are required).
* [Configuring the database connection] (*y)
* [Configuring the authentication] (*y)
* [Configuring exception handling]
* [Configuring the data initialization] (*y)
* [Configuring the LDAP access] (*y)
* [Configuring portal information access] (*y)
* [Configuring outgoing email] (*y)
* [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] (*y)
* [Configuring indexing] (*y)
* [Configuring ticket expiration and archiving]
* [Configuring URL generation] (*y)
* [Configuring email feeding]
* [Configuring the web services]
h1. 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]).
{note:title=Configure esup-helpdesk online!}{color:red}{*}Go to *{color}{color:red}*[http://www.esup-portail.org/helpdesk-config]*{color} {color:red}{*}in order to generate the configuration files interactively\!*{color}
{note}
{tip:title=Note for developers}Other properties can be added to the configuration file */properties/config.properties* and used and the Spring configuration files.
{tip}
{tip:title=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]).
{tip}
h1. Configuring the application
Excepted when indicated, all the properties are optional ((*y) icons mark the parts where properties are required).
* [Configuring the database connection] (*y)
* [Configuring the authentication] (*y)
* [Configuring exception handling]
* [Configuring the data initialization] (*y)
* [Configuring the LDAP access] (*y)
* [Configuring portal information access] (*y)
* [Configuring outgoing email] (*y)
* [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] (*y)
* [Configuring indexing] (*y)
* [Configuring ticket expiration and archiving]
* [Configuring URL generation] (*y)
* [Configuring email feeding]
* [Configuring the web services]
h1. 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]).