The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not push the repository.


Context English Italian State
If you have problems, you can add the following line to your ``~/.bashrc`` to execute the commands from the file.
Step 13: Further Information Passaggio 13: Ulteriori informazioni
We advise you to read the OTRS :doc:`performance-tuning` chapter.
Introduction Introduzione
OTRS (Open Technology – Real Service) is an open source ticket request system with many features to manage customer telephone calls and emails. It is distributed under the GNU General Public License (GPL) and tested on various Linux platforms. Do you receive many e-mails and want to answer them with a team of agents? You're going to love OTRS!
About This Manual Di questo manuale
This manual is intended for use by system administrators. The chapters describe the installation and updating of the OTRS software. Questo manuale è destinato all'uso da parte degli amministratori di sistema. I capitoli descrivono l'installazione e l'aggiornamento del software OTRS.
There is no graphical user interface for installation and updating. System administrators have to follow the steps described in the following chapters. Non esiste un'interfaccia utente grafica per l'installazione e l'aggiornamento. Gli amministratori di sistema devono seguire i passaggi descritti nei seguenti capitoli.
All console commands look like ``username> command-to-execute``. Username indicates the user account of the operating system, which need to use to execute the command. If a command starts with ``root>``, you have to execute the command as a user who has root permissions. If a command starts with ``otrs>``, you have to execute the command as the user created for OTRS.
Don't select ``username>`` when you copy the command and paste it to the shell. Otherwise you will get an error.
We supposed that OTRS will be installed to ``/opt/otrs``. If you want to install OTRS to a different directory, then you have to change the path in the commands or create a symbolic link to this directory.
Performance Tuning Ottimizzazione delle prestazioni
There is a list of performance enhancing techniques for your OTRS installation, including configuration, coding, memory use, and more. Esiste un elenco di tecniche di miglioramento delle prestazioni per l'installazione OTRS, tra cui configurazione, codifica, utilizzo della memoria e altro ancora.
Ticket Index Module Modulo indice ticket
Ticket index module can be set in system configuration setting ``Ticket::IndexModule``. There are two back end modules for the index for the ticket queue view:
``Kernel::System::Ticket::IndexAccelerator::RuntimeDB`` ``Kernel::System::Ticket::IndexAccelerator::RuntimeDB``
This is the default option, and will generate each queue view on the fly from the ticket table. You will not have performance trouble until you have about 60,000 open tickets in your system.
``Kernel::System::Ticket::IndexAccelerator::StaticDB`` ``Kernel::System::Ticket::IndexAccelerator::StaticDB``
The most powerful module, should be used when you have above 80,000 open tickets. It uses an extra ``ticket_index`` table, which will be populated with keywords based on ticket data. Use the following command for generating an initial index after switching back ends:
Ticket Search Index
OTRS uses a special search index to perform full-text searches across fields in articles from different communication channels.
To create an initial index, use this command:
Actual article indexing happens via an OTRS daemon job in the background. While articles which were just added in the system are marked for indexing immediately, it could happen their index is available within a few minutes.
There are some options available for fine tuning the search index:
``Ticket::SearchIndex::IndexArchivedTickets`` ``Ticket::SearchIndex::IndexArchivedTickets``
Defines if archived tickets will be included in the search index (not enabled by default). This is advisable to keep the index small on large systems with archived tickets. If this is enabled, archived tickets will be found by full-text searches.
``Ticket::SearchIndex::Attribute`` ``Ticket::SearchIndex::Attributo``
Basic full-text index settings.
``Ticket::SearchIndex::Attribute`` Setting ``Ticket::SearchIndex::Attributo`` Setting
Run the following command in order to generate a new index:
``WordCountMax`` ``WordCountMax``


No matching activity found.

Browse all component changes

Things to check

Unchanged translation

Source and translation are identical



English Italian
No related strings found in the glossary.

Source information

Source string location
String age
10 months ago
Source string age
10 months ago
Translation file
locale/it/LC_MESSAGES/content.po, string 105