Manual - OTOBO Installation/Installation Manual OTOBO 11 — Chinese (Traditional) @ OTOBO Translation: ``Kernel::System::Ticket::IndexAccelerator::RuntimeDB``

Translation

English

Chinese (Traditional)

Needs editing

Skip

	English	Chinese (Traditional)	Actions
	After the transfomation we can overwrite the tables in the OTOBO schema with the transformed data from OTRS. Effectively we need not a single dump file, but several SQL scripts.	转换后，我们可以用 OTRS 转换后的数据覆盖 OTOBO 模式中的表。实际上，我们需要的不是一个转储文件，而是几个 SQL 脚本。
	When ``mysqldump`` is installed and a connection to the OTRS database is possible, you can create the database dump directly on the Docker host. This case is supported by the script bin/backup.pl.	如果安装了 ``mysqldump``，并且可以连接到 OTRS 数据库，则可以直接在 Docker 主机上创建数据库转储。脚本 bin/backup.pl 支持这种情况。
	This requires that an OTOBO installation is available on the Docker host.	这需要在 Docker 主机上安装 OTOBO。
	Alternatively, the database can be dumped on another server and then be transferred to the Docker host afterwards. An easy way to do this is to copy /opt/otobo to the server running OTRS and perform the same command as above.	或者，也可以将数据库转储到另一台服务器上，然后再传输到 Docker 主机上。一种简单的方法是将 /opt/otobo 复制到运行 OTRS 的服务器上，然后执行与上述相同的命令。
	The script bin/backup.pl generates four SQL scripts in a dump directory, e.g. in 2021-04-13_12-13-04 In order to execute the SQL scripts, we need to run the command ``mysql``.	脚本 bin/backup.pl 会在转储目录中生成四个 SQL 脚本，例如 2021-04-13_12-13-04 为了执行 SQL 脚本，我们需要运行 ``mysql`` 命令。
	Native installation:	本地安装：
	Docker-based installation:	基于 Docker 的安装：
	Run the command ``mysql`` within the Docker container db for importing the database dump files. Note that the password for the database root is now the password that has been set up in the file .env on the Docker host.	在 Docker 容器 db 中运行 ``mysql`` 命令，以导入数据库转储文件。请注意，数据库 root 的密码现在是在 Docker 主机上的 .env 文件中设置的密码。
	For a quick check whether the import worked, you can run the following commands.	要快速检查导入是否成功，可以运行以下命令。
	or when running under Docker	或在 Docker 下运行时
	The database is now migrated. This means that during the next step we can skip the database migration. Watch out for the relevant checkbox.	数据库现已迁移。这意味着下一步我们可以跳过数据库迁移。注意相关复选框。
	Performance Tuning	性能调整
	This is a list of performance enhancing techniques for your OTOBO installation. The topics include configuration, coding, memory use, and more.	这是为您的 OTOBO 安装提供的性能提升技术列表。主题包括配置、编码、内存使用等。
	Ticket Index Module	票据索引模块
	Ticket index module can be set via system configuration setting ``Ticket::IndexModule``. There are two back end modules building the index for the ticket queue view:	票单索引模块可通过系统配置设置``Ticket::IndexModule``进行设置。有两个后端模块为票单队列视图建立索引：
	``Kernel::System::Ticket::IndexAccelerator::RuntimeDB``	`内核::系统::票据::索引加速器::RuntimeDB``内核::系统::票据::索引加速器::RuntimeDB
	This is the default option, which 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.	这是默认选项，它会根据票单表即时生成每个队列视图。在系统中有大约 60,000 张未结票单之前，不会出现性能问题。
	``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:	功能最强大的模块，应在有超过 80,000 张未结票单时使用。它使用一个额外的 "ticket_index "表，该表将根据票单数据填充关键字。在切换后端后，使用以下命令生成初始索引：
	Ticket Search Index	机票搜索索引
	OTOBO uses a special search index to perform full-text searches across fields in articles from different communication channels.	OTOBO 使用一个特殊的搜索索引，对来自不同传播渠道的文章进行跨领域全文搜索。
	To create an initial index, use this command:	要创建初始索引，请使用此命令：
	Actual article indexing happens via an OTOBO 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 only after a few minutes.	实际的文章索引工作是通过后台的 OTOBO 守护进程进行的。虽然刚添加到系统中的文章会立即被标记为索引，但有可能几分钟后才会有索引。
	There are some options available for fine-tuning the search index:	有一些选项可用于微调搜索索引：
	``Ticket::SearchIndex::IndexArchivedTickets``	门票::搜索索引::索引已存门票
	Defines if archived tickets will be included in the search index (disabled 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``	票据::SearchIndex::属性
	Basic full-text index settings.	基本全文索引设置。
	``Ticket::SearchIndex::Attribute`` Setting	Ticket::SearchIndex::Attribute "设置
	Run the following command in order to generate a new index:	运行以下命令以生成新索引：
	``WordCountMax``	最大字数

Loading…

mt:deepl

Automatically translated

English

Chinese (Traditional) 59 characters edited Current translation Needs editing

4 months ago

None

String added in the repository

English

Chinese (Traditional) 0 characters edited Empty

4 months ago

Browse all string changes

Things to check

Consecutive duplicated words

Text contains the same word twice in a row: 内核::系统::票据::索引加速器::RuntimeDB

Reset

Glossary

English	Chinese (Traditional)
No related strings found in the glossary.

String information

Labels

Automatically translated

Flags

ignore-same

Source string location

../../content/performance-tuning.rst:23

String age

4 months ago

Last updated

4 months ago

Source string age

7 months ago

Translation file

locale/zh_TW/LC_MESSAGES/content.po, string 581