In the Micro Focus Identity Manager architecture, the terminology for data flow is specific to its direction. When the Identity Manager engine needs to enact a change in a connected system, it sends an XML document containing an instruction, which is termed a command, to the driver. This flow occurs on the Subscriber channel. Conversely, when a change (an event) occurs in the connected system, the driver detects it and sends an XML document to the Identity Manager engine to report it. This document is termed a notification. This flow occurs on the Publisher channel. Therefore, data sent to a driver is a command, and data sent to Identity Manager is a notification.

A. An event sent to a driver is a command. Notifications are sent from a driver to the Identity Manager engine.

C. An event sent to Identity Manager is a notification. Commands are sent from the Identity Manager engine to a driver.

E. Events (on the Publisher channel) and commands (on the Subscriber channel) are processed through separate and distinct sets of policies, rules, and logic.

1. Micro Focus Identity Manager 4.8 Documentation: Understanding Identity Manager, "Chapter 2: Identity Manager Architecture", Section: "Data Synchronization". This section explicitly describes the two channels. It states, "The Subscriber channel receives commands from the Metadirectory engine... The Publisher channel queries the connected application for events and submits the events to the Metadirectory engine."

2. Micro Focus Identity Manager 4.8 Documentation: Driver Customization Guide, "Chapter 2: The Identity Manager Engine and Policies", Section: "How the Engine Processes Documents". This chapter details the document flow, clarifying that documents for the driver contain commands (e.g., , ) and that documents from the driver are event notifications (e.g., ).

3. Micro Focus Identity Manager 4.8 Documentation: Policies in Identity Manager, "Chapter 1: Introduction to Policies", Section: "Policy Processing in the Subscriber and Publisher Channels". This section reinforces that commands are processed on the Subscriber channel and events (notifications) are processed on the Publisher channel, each with its own set of policies.