- Creating a hierarchical item type
You create a hierarchical item type by enabling the hierarchical option of an item type when it is created. - Folders-only item types
A folders-only item type enforces the Folder semantic type for all its items. - Adding the ICM$NAME attribute to a hierarchical item type
The ICM$NAME attribute is the standard name attribute for an item type. It is a required attribute for hierarchical item types. If you do not add the ICM$NAME attribute to an item type when you enable its hierarchical option, it is automatically added when the hierarchical item type is created. - Root hierarchical folder
The ICMROOTFOLDER folder is the root of all hierarchical folders and documents. It does not have a parent hierarchical folder, - System default hierarchical folder
ICMSYSDEFAULTFOLDER is a hierarchical folder that is used as the system default hierarchical folder when a hierarchical parent folder is unavailable. Enabling the system default hierarchical folder lets you avoid an error when a hierarchical parent folder is missing during a create or move operation. - Hierarchical item constraints
Constraints are enforced for hierarchical items during run time. - Constraints for creating hierarchical items
Constraints are enforced when you create hierarchical items and documents. - Constraints for reindexing hierarchical items
When you reindex an item between two hierarchical item types or a hierarchical and nonhierarchical item type, constraints are enforced for the hierarchical parent and child items. - Constraints for linking hierarchical items
When you add, move, or remove a link between two hierarchical items, constraints are enforced. - Constraints for deleting hierarchical items and documents
When you delete a hierarchical item or document, hierarchical constraints are enforced. - Constraints for updating hierarchical items and documents
When you update a hierarchical item or document, hierarchical constraints are enforced. - Concurrency of hierarchical run time operations
When there are two or more run time operations involving hierarchical items operating at the same time, concurrency problems can occur. Concurrency problems can result in inconsistent hierarchical data. - Hierarchical folder model adoption strategy
The hierarchical folder model is flexible and provides advanced features and constraints. With the hierarchical folder model the overall performance for your applications is higher than if you managed your data by using the existing folder model and enforced the same hierarchical constraints.
Parent topic: Creating an IBM Content Manager application
Related concepts:
