Note: this component is designated "advanced", which means that objects of this type are not expected to be created or altered in most environments. If you believe that such a change is necessary, you may want to contact UnboundID support in order to understand the potential impact of that change.
The Interactive Transactions Extended Operation Handler provides support for processing interactive transactions, which can be used to process multiple operations as a single atomic unit. Add, compare delete, modify, modify DN, search, and some types of extended operations may be processed as part of an interactive transaction.
↓Parent Component
↓Properties
↓dsconfig Usage
The Interactive Transactions Extended Operation Handler component inherits from the Extended Operation Handler
The properties supported by this managed object are as follows:
| Basic Properties: | Advanced Properties: |
|---|---|
| ↓ description | None |
| ↓ enabled | |
| ↓ backend-id |
| Description | A description for this Extended Operation Handler |
| Default Value | None |
| Allowed Values | A string |
| Multi-Valued | No |
| Required | No |
| Admin Action Required | None. Modification requires no further action |
| Description | Indicates whether the Interactive Transactions Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server). |
| Default Value | None |
| Allowed Values | true false |
| Multi-Valued | No |
| Required | Yes |
| Admin Action Required | Use of interactive transactions is discouraged in most environments because they are prone to creating conditions that may result in deadlocks between operations that may result in the cancellation of one or both operations.
When possible, it is recommended that standard LDAP transactions (as described in RFC 5805) be used instead of interactive transactions. Although arbitrary reads are not available with standard LDAP transactions, they can be used in conjunction with the LDAP assertions control (to ensure that the update will only be processed if the target entry matches a given filter), and the pre-read and/or post-read controls (to retrieve a copy of the entry as it appeared immediately before or immediately after the update). The increment modify extension may also be used to atomically increment or decrement an integer value by a specified amount. |
| Description | Specifies the backend ID for the backend in which the transactions will be allowed. Interactive transactions will only be supported for operations in a single backend. |
| Default Value | None |
| Allowed Values | A string |
| Multi-Valued | No |
| Required | Yes |
| Admin Action Required | None. Modification requires no further action |
To list the configured Extended Operation Handlers:
dsconfig list-extended-operation-handlers
[--property {propertyName}] ...
To view the configuration for an existing Extended Operation Handler:
dsconfig get-extended-operation-handler-prop
--handler-name {name}
[--tab-delimited]
[--script-friendly]
[--property {propertyName}] ...
To update the configuration for an existing Extended Operation Handler:
dsconfig set-extended-operation-handler-prop
--handler-name {name}
(--set|--add|--remove) {propertyName}:{propertyValue}
[(--set|--add|--remove) {propertyName}:{propertyValue}] ...
To create a new Interactive Transactions Extended Operation Handler:
dsconfig create-extended-operation-handler
--handler-name {name}
--type interactive-transactions
--set enabled:{propertyValue}
--set backend-id:{propertyValue}
[--set {propertyName}:{propertyValue}] ...
To delete an existing Extended Operation Handler:
dsconfig delete-extended-operation-handler
--handler-name {name}