Identity Manager uses a MetaDirectory Engine to process Identity Vault data and events. What component assures changes in the Identity Vault are not…

The Metadirectory Engine uses a driver-specific event cache to guarantee data delivery. When a connected system becomes unavailable, the engine processes events from the Identity Vault's change log and places the resulting commands into this cache. This file-based cache persists the transactions intended for the offline system. Once the connection is restored, the engine reads from the cache and delivers the queued events in the correct order, ensuring no changes are lost and maintaining data integrity between the Identity Vault and the connected system.

A. Partition: A partition is a logical division of the eDirectory tree used for replication and distribution among servers, not for caching events for connected systems.

B. Obit flag: An obit flag (obituary) is an internal eDirectory mechanism used to manage the lifecycle of objects (e.g., deletion, move) across directory replicas.

C. Change Log: The Change Log is a record of all transactions that have occurred within the Identity Vault. The engine reads from it but does not use it to queue events for offline systems.

1. Micro Focus Identity Manager 4.8.5 Documentation, "Understanding Identity Manager," Section 2.2, "The Metadirectory Engine."

This section states: "The Metadirectory Engine reads events from the Identity Vault and the connected application, then processes the events through policies and filters. The engine also caches events if the destination application is unavailable."

2. Micro Focus Identity Manager 4.8 Documentation, "Driver Implementation Guide," Section 3.3, "Driver Cache Files."

This guide details the mechanism: "The Identity Manager engine uses cache files to store events that have not yet been processed by the driver shim... This allows the driver to be stopped and restarted without losing events. When the driver restarts, it processes any events that are in its cache files."