Contains the globally unique identifier (GUID) of the row in
the step history table. It is used to retrieve the connector space
distinguished name associated with a counter.
Contains the globally unique identifier (GUID) of the row in
the step history table. It is used to retrieve the connector space
distinguished name associated with a counter.
Contains an XML description of the step copied from the run
profile. It includes information such as step type, subtype,
partition name, and management agent-specific information like the
name of the discovery file (in case of XML management agent).
Contains a number (sometimes called the current export batch
number) associated with the management agent. It is incremented
each time an export run-step is run for this management agent.
Contains the <current-export-step-counter> of the last
export run step which completed in its entirety. This number is
sometimes called the last successful export batch number of the
management agent.
Stores information about the connection between the management
agent and the connected directory. It may appear for both import
and export runs. The management agent reports the server it
connected to and also servers it failed to connect to. The
management agent reports management agent-specific error
information, which is helpful in debugging the problem.
Contains an XML description of errors that were encountered.
This element is only present if the step does an import against a
connected directory and the management agent hit errors (as opposed
to synchronization errors).
Contains a list of connector space objects having problems
either synchronizing a connector space delta through to the
metaverse and out to other connector spaces or pushing an export
delta out to the connected directory.
Contains statistics on the staging of the entries that were
imported. If the step involves importing from a connected directory
or from a drop file, then this element will be present.
Contains a tag which records the counts of provisioning and
export attribute flow. If the step involves applying changes from
the connector space to the metaverse, then there may be one or more
provisioning changes or export attribute flow. Each management
agent for which provisioning or non-trivial export attribute flow
occurs, there will be an <outbound-flow-counters> tag.
The tree shows the ordering and number of child elements. Child
elements in a Sequence must appear in the order given and
child elements in a Choice are mutually exclusive.
Sequences and Choices can be nested. Element names
are followed by the minimum and maximum occurrences.
Contains an XML description of the step copied from the run
profile. It includes information such as step type, subtype,
partition name, and management agent-specific information like the
name of the discovery file (in case of XML management agent).
Contains a number (sometimes called the current export batch
number) associated with the management agent. It is incremented
each time an export run-step is run for this management agent.
Contains the <current-export-step-counter> of the last
export run step which completed in its entirety. This number is
sometimes called the last successful export batch number of the
management agent.
Stores information about the connection between the management
agent and the connected directory. It may appear for both import
and export runs. The management agent reports the server it
connected to and also servers it failed to connect to. The
management agent reports management agent-specific error
information, which is helpful in debugging the problem.
Contains an XML description of errors that were encountered.
This element is only present if the step does an import against a
connected directory and the management agent hit errors (as opposed
to synchronization errors).
Contains a list of connector space objects having problems
either synchronizing a connector space delta through to the
metaverse and out to other connector spaces or pushing an export
delta out to the connected directory.
Contains statistics on the staging of the entries that were
imported. If the step involves importing from a connected directory
or from a drop file, then this element will be present.
Contains a tag which records the counts of provisioning and
export attribute flow. If the step involves applying changes from
the connector space to the metaverse, then there may be one or more
provisioning changes or export attribute flow. Each management
agent for which provisioning or non-trivial export attribute flow
occurs, there will be an <outbound-flow-counters> tag.