Translation

type: Content of: <section><section><itemizedlist><listitem><para>
Session
5/100
Context English Russian State
Controller Контроллер
Controllers are collections of similar Operations or Invokers. For example, a Ticket controller might contain several standard ticket operations. Custom controllers can be implemented, for example a "TicketExternalCompany" controller which may contain similar functions as the standard Ticket controller, but with a different data interface, or function names (to adapt to the Remote System function names) or complete different code.
One application for Generic Interface could be to synchronize information with one Remote System that only can talk with another Remote System of the same kind. In this case new controllers needs to be developed and the Operations and Invokers has to emulate the Remote System behavior in such way that the interface that OTRS exposes is similar to the Remote System's interface.
Operation (OTRS as a provider) Операция (OTRS как поставщик услуг)
An Operation is a single action that can be performed within OTRS. All operations have the same programming interface, they receive the data into one specific parameter, and return a data structure with a success status, potential error message and returning data.
Normally operations uses the already mapped data (internal) to call core modules and perform actions in OTRS like: Create a Ticket, Update a User, Invalidate a Queue, Send a Notification, etc. An operation has full access to the OTRS API to perform the action.
Invoker (OTRS as a requester) Invoker - запрашивающая сторона (OTRS как запрашивающая сторона, клинет)
An Invoker is an action that OTRS performs against a Remote System. Invokers use the OTRS Core modules to process and collect the needed information to create the request. When the information is ready it has to be mapped to the Remote System format in order to be sent to the Remote System, that will process the information execute the action and send the response back, to either process the success or handle errors.
Connectors Коннекторы (Connectors)
A Connector is in essence a set of actions that are either called Operations if OTRS acts as a web service provider or Invokers if OTRS acts as a web service requester. But it can also include special Mappings or Transports.
One Connector can either have only Operations, Only Invokers or both. A connector can even use parts of other connectors like the Mappings or Transports if they are not to specific for the Connector that is trying to implement them.
In other words a Connector is not limited to just the Controller layer but it can be extended to Data Mapping or Network Transport layers if needed.
Due to the modular design of the Generic Interface a Connector can be seen as a plug-in; this means that by adding Connectors the capabilities of the generic interface can be extended using: OTRS Feature add ons, OTRS Custom modules, 3rd Party modules, and so on.
Bundled Connectors Комплект Коннекторов (Connectors)
Included with this version of OTRS the following connectors are ready to be used:
Session Сеанс
Session Connector Коннектор сессии
This connector is capable to create a valid SessionID that can be used in any other operation. Этот коннектор может создать действительный SessionID, который в дальнейшем может быть использован в любой другой операции.
Provides: Поставщики:
Operations: Операции:
SessionCreate SessionCreate
SessionGet
Operations Операции
Creates a new valid SessionID to be used in other operations from other connectors like TicketCreate.
To use the SessionID in other operations from other connectors it is necessary that the operation implements authentication by SessionID. All the rest of the bundled operations are capable of accepting a valid SessionID as an authentication method.
Possible Attributes: Возможные Атрибуты:
<SessionCreate>
<!--You have a MANDATORY CHOICE of the next 2 items at this level-->
<!--Optional:-->
<UserLogin>?</UserLogin>
<!--Optional:-->
<CustomerUserLogin>?</CustomerUserLogin>
<!--Optional:-->
<Password>?</Password>
</SessionCreate>
<SessionCreate>
<!--You have a MANDATORY CHOICE of the next 2 items at this level-->
<!--Optional:-->
<UserLogin>?</UserLogin>
<!--Optional:-->
<CustomerUserLogin>?</CustomerUserLogin>
<!--Optional:-->
<Password>?</Password>
</SessionCreate>
Gathers data from a valid session excluding sensitive information such as user password or challenge token.
If any of its values is a complex structure then it is automatically converted to a JSON string.
<SessionGet>
<SessionID>?</SessionID>
</SessionGet>
Ticket Connector Коннектор Заявки
ComponentTranslation
This translation Translated OTRS 6/Administration Manual Сеанс
The following string has the same context and source.
Translated OTRS 6/((OTRS)) Community Edition Сеанс

Loading…

User avatar ymyasoedov

Translation changed

OTRS 6 / Administration ManualRussian

Session
SessionСеанс
a year ago
Browse all component changes

Glossary

English Russian
No related strings found in the glossary.

Source information

Source string comment
type: Content of: <section><section><itemizedlist><listitem><para>
Source string location
en/content/administration/genericinterface/genericinterface-connectors.xml:37
String age
a year ago
Source string age
a year ago
Translation file
i18n/doc-admin.ru.po, string 2590