TheFork Join Workflow Element aggregates the data from various sources at real time.
The Fork Join Workflow Element aggregates the data from two sources at real time. It solves the problem of split-profiles, where the user data is split across two repositories. The Fork Join Workflow Element can have one primary participant and one secondary participant, each of which is a WorkFlow Element of any type. The Fork Join Workflow Element allows the user to search (search filter) against the primary participant, the secondary participant, or both primary and secondary participant whereas the Join workflow element allows the user to search (search filter) against the primary participant only.
The Fork Join Workflow Element component inherits from the Workflow Element
The following components have a direct COMPOSITION relation FROM Fork Join Workflow Elements :
A description of each property follows.
Basic Properties: | Advanced Properties: |
---|---|
↓ cache-size | ↓ java-class |
↓ dn-attribute | ↓ password-attribute |
↓ enabled | ↓ save-password-on-successful-bind |
↓ join-suffix | |
↓ populate-joinedentrydn | |
↓ primary-and-secondary-attributes | |
↓ secondary-only-attributes |
Description | The maximum number of entries that can be stored in the cache used to filter out entry duplicates. When the entry duplicates filtering is active, the ForkJoinflowElement stores the returned entry DNs in a cache. A cache is specific to a search operation, and when the cache is full, the search operation is aborted. By default, the cache can handle 10 000 DNs. When the cache size is set to 0 or is negative, then no limit is enforced. |
---|---|
Default Value | 10000 |
Allowed Values | An integer value. Lower value is 0. |
Multi-valued | No |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | DN syntax attributes whose DN need to be translated to that of Fork Join Workflow Element. |
---|---|
Default Value | member
uniquemember
memberof
manager |
Allowed Values | A String |
Multi-valued | Yes |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
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 | The virtual DN that will be exposed by the Fork Join Workflow Element |
---|---|
Default Value | None |
Allowed Values | A valid DN. |
Multi-valued | No |
Required | Yes |
Admin Action Required | None |
Advanced Property | No |
Read-only | Yes |
Description | Decides if the attribute "joinedentrydn" has to be populated in the joined entries. |
---|---|
Default Value | false |
Allowed Values | true false |
Multi-valued | No |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
primary-and-secondary-attributes
Description | A list of attributes that are present in both the primary and secondary participants and which the application can use in the search filter. The attributes identified by the PrimaryAndSecondaryAttributes configuration parameter cannot also be identified by the SecondaryOnlyAttributes configuration parameter. |
---|---|
Default Value | |
Allowed Values | A String |
Multi-valued | Yes |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | A list of attributes that are present only in the secondary participant and which the application can use in the search filter. The attributes identified by the SecondaryOnlyAttributes configuration parameter cannot also be identified by the PrimaryAndSecondaryAttributes configuration parameter. |
---|---|
Default Value | By default, the secondary only attributes attribute list is empty, which means that participant is not responsible for handling any attributes that are present in search filter. When it is empty for all the paritipcants, then all search attributes are considered to be in primary participant. |
Allowed Values | A String |
Multi-valued | Yes |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Specifies the fully-qualified name of the Java class that provides the Fork Join Workflow Element implementation. |
---|---|
Default Value | com.oracle.dps.server.workflowelement.forkjoin.ForkJoinWorkflowElement |
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 |
Description | Specifies the names of the attribute that contains the password in the user entry. When saving the password in the user entry, that parameter contains the name of the attribute used to store the password in the user entry. |
---|---|
Default Value | userpassword |
Allowed Values | The name of an attribute type defined in the server schema. |
Multi-valued | No |
Required | No |
Admin Action Required | None |
Advanced Property | Yes |
Read-only | No |
save-password-on-successful-bind
Description | Indicates whether the password should be saved in the primary entry when authentication succeeds. When executing authentication on a secondary participant, it is sometimes useful to be able to save the password in the primary entry. |
---|---|
Default Value | false |
Allowed Values | true false |
Multi-valued | No |
Required | No |
Admin Action Required | None |
Advanced Property | Yes |
Read-only | No |