Object store tree

When you create an object store, the object store is populated with default nodes and folders. The default nodes and folders contain Content Cortex objects, such as classes, properties, events, and subscriptions, that support features in Content Platform Engine and other Content Cortex components. The nodes and folders are displayed in an object store tree by tools such as Administration Console for Content Platform Engine.

  • Administrative folder
    Audit disposition
    Contains two subfolders, Audit Disposition Policies and Audit Processing Bookmarks, which contain the audit disposition policies and the audit processing bookmarks for the object store. Content Cortex prunes audit entries in the audit log in accordance with audit disposition policies. You can configure objects within the standard server hierarchy levels for this pruning. When the audit log is automatically managed in this way, your custom audit processing applications partly control the pruning of audit events by setting bookmarks. Bookmarks prevent the subsystem task from deleting those audit events that your applications did not process yet.
    Index Areas
    Contains the index areas that are defined for the object store. An index area is a file system directory that contains the files for the full-text indexes that belong to the object store. You create index areas manually.
    Index Jobs Manager
    Contains the index jobs that are defined for the object store. An index job generates a batch of index requests and is automatically created when you choose a CBR-enabled class or object to be indexed in the administration console. An index job is also created when you manually choose to reindex a selected index in an index area.
    Indexing Queue
    Contains the indexing requests that have failed to process for the object store. An unprocessed request is one that has not yet started running or not yet finished running or has temporarily finished running because of a system-related failure. Processed index requests that have finished running either because the text for the object was successfully indexed or because of a document-related failure are deleted automatically.
    Publishing Queue
    Publishing is a facility that enables a replica of a document to be made. The replica, known as the publication document, can have its own security and property settings, as well as have a different format than the original (or source) document. Publishing is useful when you want to make a document available to customers, but you do not want them to be able to modify the document. The publishing queue lists each publishing request that is initiated for the associated object store and displays the requests in the results pane. The results pane displays information, such as the request status, for each publishing request.
    Replication Queue
    Contains a list of documents and annotations that have failed replication on a federated system. On rare occasions, documents might fail to replicate from one system to the other. On FileNet® Image Services, federation errors are recorded in the IBM® Content Cortex Content Federation Services for Image Services export error log. Use the Remote Admin Console to reexport the appropriate documents. On Content Platform Engine, unfederated documents and annotations remain in the replication queue. Use Administration Console for Content Platform Engine to view and manage the replication queue.
    Security Policies
    Contains the security policies that are defined for an object store. Security policies allow security administrators to apply access control to large numbers of documents, folders and custom objects without directly editing the access control list on each individual object.
    Index Areas
    Index areas, which are associated with a particular object store, contain index collections for an object store and are stored in a shared network file system directory.
    Storage Areas
    Contains the storage areas that are defined for an object store.
    Storage Policies
    Contains the storage policies that are defined for an object store. Storage policies provide mapping to specific physical storage areas and are used to specify where content is stored for a given class or object with content (for example, a document).
    Workflow System
    Contains the workflow systems that are defined for an object store. A workflow system is a collection of isolated regions. Each isolated region contains the queues, rosters, and event logs that are necessary to create and process workflows.
  • Browse folder
    Root Folder
    Contains system-level documents, such as custom objects, documents, and user-defined subfolders.
    Unfiled Documents
    Contains unfiled documents or custom objects. Documents and custom objects are typically stored in user-defined subfolders under the root folder node. When you unfile a document or custom object, the document "shortcut" is removed from the root folder and placed in the unfiled documents folder. Because the unfiled documents folder is not a subfolder of the root folder, the folder and its contents are not displayed by client applications.
    The unfiled documents folder has a display limit of 500 documents. If there are more than 500 unfiled documents in an object store, you must file the first 500 documents into other folders and then refresh the unfiled documents folder to view the remaining unfiled documents.
  • Data Design folder
    Choice Lists
    Contains all of the choice lists that are defined for an object store. A choice list is a list of predefined property values. When added to a class definition, a choice list presents a list of valid choices, such as a list of states, from which users can select when completing a form.
    Classes
    Contains subfolders for Custom Objects, Documents, and Folders and Other Classes, which are all of the classes that are defined for an object store.
    Property Templates
    Contains the property templates defined for an object store.
    A property template is a shell property that you can assign to any number of classes in an object store. A property template has no function or meaning in the object store until it is assigned to a class. During property template creation, you assign attributes including data type, whether it is a single value or list, and other optional attributes.
  • Events, Actions, Processes
    Change Preprocessor Actions
    Contains the change preprocessor actions that are defined for an object store. A change preprocessor action contains the code that performs the change preprocessing. You can use either Java™ or JavaScript to implement the action.
    Document Classification Actions
    Contains all of the document classification actions that are defined for an object store. A document classification action enables Content Engine to assign values to certain document properties when the document is checked in. The values assigned to the properties are derived from the content of the document itself and the document MIME type.
    Document Lifecycle Actions
    Contains the document lifecycle actions that are defined for an object store. A document lifecycle consists of states a document goes through during its life. Each lifecycle consists of two objects: a document lifecycle policy and a document lifecycle action.
    Document Lifecycle Policies
    Contains the document lifecycle policies that are defined for an object store. A document lifecycle policy is a definition of the document's states. The policy also identifies the lifecycle action that executes in response to the state changes.
    Event Actions
    Contains the event actions that are defined for an object store. An event consists of an event action and a subscription. An event action describes the action to take place on an object.
    Subscriptions
    Contains the subscriptions that are defined for an object store. A subscription defines the object or class of objects to which the action applies, as well as which events trigger the action to occur. For example, you can define an event that sends an email notification to a system administrator each time a document is deleted.
    Workflow Definitions
    Stores the workflow definitions for an object store. A workflow definition is an electronic representation of the activities required to accomplish a business process. It acts as a processing template for routing the work to the specified participants, along with data, attachments, and other information they will need to complete the activities.
    Because a workflow definition is a subclass of the Document class, it can be checked out, checked in, filed into a folder, and deleted. You cannot add workflow definitions from the administration console. Workflow definitions are created by using the Process Designer application. To be useful, a workflow definition must be transferred to the workflow system, where it is compiled and assigned a unique identifier (VWVersion). A transferred workflow definition can be launched manually, or it can be launched from a subscription.
  • Search
    Search
    Enables you to query an object store. Search results appear in the details pane. You can create new queries or load and run predefined queries.
  • Sweep Management
    Job Sweeps
    Contains retention update jobs defined for the object store. You can use retention update jobs to change the retention period of an object based on the class of an object or the state of its properties.
    Policy-controlled sweeps
    Contains the bulk move content jobs that allow the content of large sets of documents or annotations to be moved from one storage area to another.
    Queue Sweeps
    Contains the queue sweep jobs defined for the object store. A queue sweep job passes document content elements to the thumbnail generation service that renders a thumbnail image of the document. You cannot generate thumbnails for annotations.
    Sweep Policies
    Contains the sweep policies that apply to the object store. A sweep includes a way to define a set of candidate objects to be examined and a rule for applying some action to a subset of those objects. The subset is determined by the values of various properties of the objects. The set of candidate objects to examine is defined by a target class. The rule is defined by a filter expression. The action to perform on the selected objects is defined by the sweep type or the policy type that is associated with the sweep.