The Load Balancing Workflow Element is used route requests to a set of routes.
The Load Balancing Workflow Element is used route requests to a set of routes. From the load balancing workflow element perspective, a route is a workflow element. Whether the route is a Proxy LDAP workflow element, or another load balancing workflow element, or a workflow element of any type does not matter.
The Load Balancing Workflow Element component inherits from the Workflow Element
The following components have a direct COMPOSITION relation FROM Load Balancing Workflow Elements :
This page describes the Load Balancing Workflow Element:
A description of each property follows.
Basic Properties: | Advanced Properties: |
---|---|
↓ enabled | ↓ java-class |
↓ workflow-element-id |
Description | Indicates whether the Workflow Element is enabled for use in the server. If a Workflow Element is not enabled, then its contents are not accessible when processing operations. |
Default Value | None |
Allowed Values | true false |
Multi-valued | No |
Required | Yes |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Provides a name that identifies the associated Workflow Element . The name must be unique among all Workflow Elements in the server. |
Default Value | None |
Allowed Values | A String |
Multi-valued | No |
Required | Yes |
Admin Action Required | None |
Advanced Property | No |
Read-only | Yes |
Description | Specifies the fully-qualified name of the Java class that provides the Load Balancing Workflow Element implementation. |
Default Value | com.sun.dps.server.workflowelement.loadbalancing.LoadBalancingWorkflowElement |
Allowed Values | A java class that implements or extends the class(es) : org.opends.server.workflowelement.WorkflowElement |
Multi-valued | No |
Required | Yes |
Admin Action Required | None |
Advanced Property | Yes |
Read-only | No |
Each configuration property can be mapped to a specific LDAP attribute under the "cn=config" entry. The mappings that follow are provided for information only. In general, you should avoid changing the server configuration by manipulating the LDAP attributes directly.
Base DN | cn=Workflow elements,cn=config |
objectclass name | ds-cfg-load-balancing-workflow-element |
objectclass superior | ds-cfg-workflow-element |
Property | LDAP attribute |
enabled | ds-cfg-enabled |
java-class | ds-cfg-java-class |
workflow-element-id | ds-cfg-workflow-element-id |