LDAP Model for Workflow
Workflows can be stored in the UMC directory in bytecode format. Workflows are from the type umcWorkflow and are stored in the o=Workflows, o=umc tree. The OSM takes care of the execution of the workflow requests in a transactional behavior and that they are performed in the proper order according to the object life cycle definition.
The OSM has the knowledge about state machines and their representation in the directory and performs transactions on target objects. The state machine objects are stored as umcStateMachine objects in the o=Workflow, o=umc tree. Each target, this might be any object from the type umcuser, umcEnterprise, umcSite, umcRetailer, sspServiceProfile, umcRadiusPerson, umcOutsourceServiceProfile, and umcAccessServiceProfile, of a transaction must have the auxiliary class transactionalObjectAuxClass attached to it. Those transactional objects can be locked by the OSM, that is indicated by the presence of a umcTransactionalLock object in the o=Lock, o=umc tree. This object has a copy of the target as direct subordinate within the directory tree. The OSM performs the directory operations for updating the states, creating and deleting the copy of the target.
The creation of state machines, workflows and transaction locks are performed using the SDX Admin that is able to trigger workflows.
For detailed information about the SDX LDAP schema, see the documentation in the SDX software distribution in the folder /SDK/doc/ldap.