Use of LDAP and Dynamic Organization Models

From an Organization Unit extension point (places in a static organization model where you want the Dynamic Organizations to appear) you need to perform an LDAP query.

The extension point is the holder of the LDAP Query configuration, and the point within the model at which Dynamic Organization Model instances resulting from that LDAP Query will be located and assigned.The LDAP Query is the search filter, used to identify LDAP entries by their attribute values. An attribute commonly used within these queries is ObjectClass: for example, where objectClass = organizationalUnit .

The LDAP Alias (LDAP Connection Shared Resource), Base-DN and Search Scope properties determine the start position and depth of the search within the LDAP Directory.

There is a named LDAP attribute from which the name of the Dynamic Organization Model instances will be derived.

You need to map the Dynamic Organization Identifier fields to named LDAP attributes. The values of the named LDAP attributes, taken from the LDAP entry from which each instance is generated, will be used, by a process task, to uniquely identify the instance as a Participant of that task. It is, therefore, important that these named LDAP attributes hold values unique to each instance.

Any Base-DN, specified in the extension point configuration, will be appended to any Base-DN applied to the URL of the selected LDAP Connection Shared Resource.

From each LDAP entry, returned by the LDAP Query, the values of the named LDAP Attribute will be read; and, for each value, a new instance of the Dynamic Organization Model will be created. Also, for each new Dynamic Organization Model instance, the values of the LDAP Attributes mapped to the Dynamic Organization Identifier fields will be read from the same LDAP entry and recorded against that instance.

See Dynamic Organization Participants for a graphic showing an Organization Unit extension point where you want the Dynamic Organizations to appear in an Organization Model.

Note: In TIBCO Business Studio you usually allocate work to a position. With a Dynamic Organization all that exists is the template. The Dynamic Organization Identifier is used to map LDAP attributes (Attribute/LDAP attribute). This is likely to be the same LDAP Attribute from which the Dynamic Organization Model instance derives its name. See "Dynamic Organization Identifier Mapping" in the TIBCO Business Studio Modeling Guide.

See "Creating LDAP Containers" in the Organization Browser User's Guide.