6.1. OTRS config files
From open-support.info
m (1 revision: Update book/figure) |
|||
| (3 intermediate revisions not shown) | |||
| Line 8: | Line 8: | ||
|editor=Dick6809 | |editor=Dick6809 | ||
}} | }} | ||
| - | <onlyinclude> | + | <onlyinclude>All OTRS configuration files are stored in the directory Kernel and in its subdirectories. There is no need to manually change any other file than <tt>Kernel/Config.pm</tt>, because the rest of the files will be changed when the system gets upgraded. Just copy the configuration parameters from the other files into <tt>Kernel/Config.pm</tt> and change them as per your needs. This file will never be touched during the upgrade process, so your manual settings are safe. |
| - | All OTRS configuration files are stored in the directory Kernel and in its subdirectories. There is no need to manually change any other file than <tt>Kernel/Config.pm</tt>, because the rest of the files will be changed when the system gets upgraded. Just copy the configuration parameters from the other files into <tt>Kernel/Config.pm</tt> and change them as per your needs. This file will never be touched during the upgrade process, so your manual settings are safe. | + | |
The file <tt>Kernel/Config/Defaults.pm</tt> contains the parameters of the central OTRS framework. It defines all basic system settings such as the mail configuration, database connection, default charset and standard language. The file <tt>Kernel/Config/Files/Ticket.pm</tt> contains all configuration parameters for the trouble ticket system. | The file <tt>Kernel/Config/Defaults.pm</tt> contains the parameters of the central OTRS framework. It defines all basic system settings such as the mail configuration, database connection, default charset and standard language. The file <tt>Kernel/Config/Files/Ticket.pm</tt> contains all configuration parameters for the trouble ticket system. | ||
| - | In the directory <tt>Kernel/Config/Files there are some other files that are parsed when the OTRS login page is accessed. If additional applications like the FAQ or the File Manager are installed, the configuration files for those can also be found in the mentioned path. | + | In the directory <tt>Kernel/Config/Files</tt> there are some other files that are parsed when the OTRS login page is accessed. If additional applications like the FAQ or the File Manager are installed, the configuration files for those can also be found in the mentioned path. |
| - | To maintain compatibility with older OTRS versions, there is always a .pm and a .xml file for every application and for the central framework. The .pm files are needed to parse all default and customized settings. The .xml files are used by the graphical interface for system configuration which has been available since OTRS 2.0, and which lets you set most of the configuration parameters of the system through your web browser. In future versions of OTRS the .pm files will be removed and the system will be configurable only via the .xml files. All parameters in <tt>Kernel/Config/Defaults.pm</tt> will be moved to <tt>Kernel/Config/Files/Framework.xml and all parameters for the trouble ticket system will be no longer stored in <tt>Kernel/Config/Files/Ticket.pm</tt> but in <tt>Kernel/Config/Files/Ticket.xml. The format of the configuration parameters will completely change to XML. | + | To maintain compatibility with older OTRS versions, there is always a .pm and a .xml file for every application and for the central framework. The .pm files are needed to parse all default and customized settings. The .xml files are used by the graphical interface for system configuration which has been available since OTRS 2.0, and which lets you set most of the configuration parameters of the system through your web browser. In future versions of OTRS the .pm files will be removed and the system will be configurable only via the .xml files. All parameters in <tt>Kernel/Config/Defaults.pm</tt> will be moved to <tt>Kernel/Config/Files/Framework.xml</tt> and all parameters for the trouble ticket system will be no longer stored in <tt>Kernel/Config/Files/Ticket.pm</tt> but in <tt>Kernel/Config/Files/Ticket.xml</tt>. The format of the configuration parameters will completely change to XML. |
| - | If the OTRS web interface is accessed, all .xml files in the <tt>Kernel/Config/Files directory are parsed in alphabetical order, and the settings for the central framework and additional applications will be loaded. Afterwards, the settings in the two files <tt>Kernel/Config/Files/ZZZAAuto.pm</tt> and <tt>Kernel/Config/Files/ZZZAuto.pm</tt> will be evaluated. Both files are used by the graphical interface for system configuration and should never be changed manually. Lastly, the file <tt>Kernel/Config.pm</tt> that contains your individual settings and manually changed configuration parameters, will be parsed. Reading the configuration files in this order makes sure that your specific configuration settings are used by the system.</onlyinclude> | + | If the OTRS web interface is accessed, all .xml files in the <tt>Kernel/Config/Files</tt> directory are parsed in alphabetical order, and the settings for the central framework and additional applications will be loaded. Afterwards, the settings in the two files <tt>Kernel/Config/Files/ZZZAAuto.pm</tt> and <tt>Kernel/Config/Files/ZZZAuto.pm</tt> will be evaluated. Both files are used by the graphical interface for system configuration and should never be changed manually. Lastly, the file <tt>Kernel/Config.pm</tt> that contains your individual settings and manually changed configuration parameters, will be parsed. Reading the configuration files in this order makes sure that your specific configuration settings are used by the system.</onlyinclude> |
Latest revision as of 05:23, 24 April 2011
All OTRS configuration files are stored in the directory Kernel and in its subdirectories. There is no need to manually change any other file than Kernel/Config.pm, because the rest of the files will be changed when the system gets upgraded. Just copy the configuration parameters from the other files into Kernel/Config.pm and change them as per your needs. This file will never be touched during the upgrade process, so your manual settings are safe.
The file Kernel/Config/Defaults.pm contains the parameters of the central OTRS framework. It defines all basic system settings such as the mail configuration, database connection, default charset and standard language. The file Kernel/Config/Files/Ticket.pm contains all configuration parameters for the trouble ticket system.
In the directory Kernel/Config/Files there are some other files that are parsed when the OTRS login page is accessed. If additional applications like the FAQ or the File Manager are installed, the configuration files for those can also be found in the mentioned path.
To maintain compatibility with older OTRS versions, there is always a .pm and a .xml file for every application and for the central framework. The .pm files are needed to parse all default and customized settings. The .xml files are used by the graphical interface for system configuration which has been available since OTRS 2.0, and which lets you set most of the configuration parameters of the system through your web browser. In future versions of OTRS the .pm files will be removed and the system will be configurable only via the .xml files. All parameters in Kernel/Config/Defaults.pm will be moved to Kernel/Config/Files/Framework.xml and all parameters for the trouble ticket system will be no longer stored in Kernel/Config/Files/Ticket.pm but in Kernel/Config/Files/Ticket.xml. The format of the configuration parameters will completely change to XML.
If the OTRS web interface is accessed, all .xml files in the Kernel/Config/Files directory are parsed in alphabetical order, and the settings for the central framework and additional applications will be loaded. Afterwards, the settings in the two files Kernel/Config/Files/ZZZAAuto.pm and Kernel/Config/Files/ZZZAuto.pm will be evaluated. Both files are used by the graphical interface for system configuration and should never be changed manually. Lastly, the file Kernel/Config.pm that contains your individual settings and manually changed configuration parameters, will be parsed. Reading the configuration files in this order makes sure that your specific configuration settings are used by the system.
