| | |
| | | relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes |
| | | relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend. |
| | | relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value. |
| | | relation.workflow.user-friendly-name=Workflow |
| | | relation.workflow.user-friendly-plural-name=Workflows |
| | | relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the directory server. |
| | | relation.workflow-element.user-friendly-name=Workflow Element |
| | | relation.workflow-element.user-friendly-plural-name=Workflow Elements |
| | | relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow. |
| | | relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend. |
| | | relation.work-queue.user-friendly-name=Work Queue |
| | | relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner. |
| | | relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately. |