La liste d'utilisateurs n'est pas rendue car vous ne possédez pas les droits d'accès nécessaires pour afficher les profils utilisateur.
Historique de la page
The configuration file (config.properties) is used to configure the behaviour of the application at runtime.
Using config.properties
From 3.30
The config.properties file is no more integrated in the application. (No more need recover config utility. Version control compatible. Easy upgrade in case of bug correction)
To use this externalized properties file, use the -Dconfig.location parameter on the java command line.
Tomcat example:
set JAVAOPTS="-Dconfig.location=/path/to/config.properties"; startup.sh
| Remarque |
|---|
See chapter Configuring the application And adapt web.xml (see Installation 3.30) You also find an exhaustive list of those properties can be found in the config.properties.example file from sources. |
| Remarque |
|---|
If you want to use a specific log configuration, please specify a specific log4j configuration file with this parameter on the java command line: -Dlog4j.configuration=file:/path/to/log4j.properties |
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-example.properties..properties.
| Remarque | ||
|---|---|---|
| ||
Go to http://www.esup-portail.org/helpdesk-config in order to generate the configuration files interactively! |
| Astuce | ||
|---|---|---|
| ||
Other properties can be added to this file the configuration file /properties/config.properties and used and the Spring configuration files. |
| Astuce | ||
|---|---|---|
| ||
The configuration file /properties/config.properties is automatically recover recovered from previous versions when upgrading (see Conservation des personnalisations lors des mises à jour Recovering previous configuration and customizations when upgrading). |
| Ancre | ||||
|---|---|---|---|---|
|
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
- Configuration de la connexion à la base de données
- Configuration de l'authentification
- Configuration de la gestion des exceptions
- Configuration de l'initialisation de l'application
- Configuring the LDAP access
- Configuring portal information access
- Configuration de l'envoi de courriers électroniques
- Configuration des propriétés initiales des services
- Configuration des propriétés initiales des gestionnaires
- Configuration de la priorité par défaut des tickets
- Configuration de la visibilité par défaut des tickets
- Configuration de la visibilité par défaut des FAQ
- 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 Configurign the automatic ticket assignment
- Configuring user profile retrieval
- Configuration du stockage des fichiers attachés
- Configuration de l'indexation
- Configuration de l'expiration et de l'archivage des tickets
- Configuring the storage of attached files
- Configuring indexing
- Configuring ticket expiration and archiving
- Configuring URL generation Configuration de la génération des URLs
- Configuring email feeding
- Configuration du contrôle d'accès des 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.
...
Vue d'ensemble
Gestion des contenus