Le fichier /properties/The configuration file (config.properties indique comment se comporte l'application esup-helpdesk. Le fichier /properties/config-example.properties donne toutes les propriétés disponibles dans la distribution. D'autres propriétés peuvent être ajoutées à ce fichier et utilisé dans les fichiers de configuration Spring.

Sauf indication contraire, les propriétés sont facultatives.

• Connexion à la base de données
• Authentification
• Gestion des exceptions
• Initialisation de l'application
• Accès à l'annuaire LDAP
• Accès aux informations du portail
• Envoi de courriers électroniques
• Configuration initiale des services
• Visibilité des services par les utilisateurs
• Priorité par défaut des tickets
• Visibilité par défaut des tickets
• Visibilité par défaut des FAQ
• Assignation par défaut des tickets
•  

########################################################################
# LDAP attributes automatically printed for users that create tickets
#

#
# the name of the attributes that are automatically printed by the application
# each time a user creates a ticket. Must be a subset of ldap.attributes.
# leave empty to print all the LDAP attributes.
#

#userInfo.ldapAttributes=

#
# the user id that will be used when running ant target test-user-info.
#

#userInfo.testUserId=paubry

########################################################################
# Computer URLs
#

#
# The pattern to use when building computer URLs for GLPI.
#

\#computerUrl.glpiPattern=http://glpi.domain.edu/front/computer.php?contains\[0\]=%s&field\[0\]=1&sort=1&deleted=N&start=0

#
# The CAS service URL.
#

#computerUrl.casServiceUrl=https://cas.domain.edu?service=%s

# the name of the default computer url builder.

#defaultComputerUrlBuilderName=null

########################################################################
# Upload
#

#
# the path where the application stores the uploaded files. In clustered
# environments, all the application servers must have r/w access to this
# path.
# REQUIRED
#

#uploadedFiles.path=c:/helpdesk/files

#
# the path where the v2 application was storing the uploaded files, used
# by ant target upgrade. The server that runs the ant target must have r/w
# access to this path.
# REQUIRED for the migration from v2 to v3
#

#uploadedFiles.v2Path=c:/helpdesk/v2Files

########################################################################
# Indexing
#

#
# the path where to store the index files. The server that runs the ant
# targets rebuild-index and update-index have r/w access to this path. In
# clustered environment, all the application servers must have r access to
# the path.
# REQUIRED
#

#indexing.path=c:/helpdesk/index

########################################################################
# archiving
#

# the time tickets are kept as tickets before being archived  by the ant
# target archive-tickets (h=hour, d=days, m=month)
#

#archiving.timeLimit=1m

########################################################################
# expiration
#

# the time closed tickets are kept non approved before being approved
# by the ant target expire-tickets (d=days, m=month)
#

#expiration.timeLimit=14d

########################################################################
# URL generation
#

\#
\# The name of the bean used to generate URLs. Set this property to
\# \[servletUrlgenerator\] for servlet deployment and \[uportalUrlGenerator\]
\# for uPortal portlet deployments
\#

#urlGeneration.bean=servletUrlGenerator

#
# the login URL of the CAs server
# REQUIRED for both servlet and portlet deployments
#

#urlGeneration.casLoginUrl=https://cas.domain.edu/login?service=%s

#
# the login URL of the application for local (CAS authenticated) users.
# REQUIRED for servlet deployments
#

#urlGeneration.servletLoginUrl=http://helpdesk.domain.edu/stylesheets/cas.faces

#
# the login URL of the application for external (email authenticated) users.
# REQUIRED for servlet deployments
#

#urlGeneration.servletGuestUrl=http://helpdesk.domain.edu/stylesheets/welcome.faces

#
# the functional name of the portlet in uPortal.
# REQUIRED for uPortal portlet deployments
#

#urlGeneration.uportalFunctionnalName=esup-helpdesk

#
# the login URL of the application for local (CAS authenticated) users.
# REQUIRED for uPortal portlet deployments
#

#urlGeneration.uportalLoginUrl=http://portal.domain.edu/Login

#
# the login URL of the application for external (email authenticated) users.
# REQUIRED for uPortal portlet deployments
#

#urlGeneration.uportalGuestUrl=http://portal.domain.edu/Guest

########################################################################
# FEED

#
# The address of the IMAP mailbox
# REQUIRED by ant target feed
#

#feed.imap.address=support@domain.edu

#
# the host name or IP address of the IMAP server
# REQUIRED by ant target feed
#

#feed.imap.server=imap.domain.edu

#
# the credentials used to connect to the IMAP server
# REQUIRED by ant target feed
#

#feed.imap.account=support
#feed.imap.password=secret

#
# the folder to read
#

#feed.imap.folder=INBOX

#
# the ID of the target category for the tickets
#

#feed.imap.categoryId=1

########################################################################
# WEB SERVICES

# the (comma-separated) clients authorized to use the web service
# if left empty (by default), any client will be authorized to use
# the web service (potential security hole).

) 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

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.

Ancre
config config

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

...