Events vs Commands


Events vs Commands

The distinction is subtle but important. Many of the possible child elements of <input> can be interpreted either as DirXML command or as DirXML event, depending on the context, and have essentially the same syntax.

In general, for elements that can be used as either a command or as notification of an event the following applies:

  • If the element is being sent to the shim (ie Connected Application) then the element is a command
  • If the element is being sent to Identity Manager (ie EDirectory) then the element is an event notification.

When the DirXML Shim sends an DirXML event to DirXML Engine the DirXML Shim is informing DirXML Engine of something that occurred in the Connected Application. DirXML Engine will then determine, based on configurable policies, which DirXML command, if any, must be sent to the eDirectory.

When DirXML Engine sends a DirXML command to the DirXML Shim, DirXML Engine has already taken an eDirectory event as input, applied the appropriate policies, and determined that the change in the Connected Application represented by the DirXML command is necessary.

More Information#

There might be more information for this subject on one of the following: ...nobody