Microsoft Identity Integration Server 2003 Developer Reference

step-details

The <step-details> element stores run information about one step of the management agent run.

Usage

<step-details
	step-number = "a number"
step-number Contains the sequence number of the step within the run, starting with 1. 

	step-id = "GUID of step"
step-id 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. 

/>

Attributes

Attribute Type Required Description
step-number a number Yes Contains the sequence number of the step within the run, starting with 1.
step-id GUID of step Yes 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.

Child Elements

Element Description
<start-date> Contains the date and time at which the step began.
<end-date> Contains the date and time at which the step completed.

Note  This element will be present only if the step has completed.
<step-result> Contains a non-localized string giving the current status of the step.
<step-description> 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).
<current-export-step-counter> 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.
<last-successful-export-step-counter> 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.
<ma-connection> 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.
<ma-discovery-errors> 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).
<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.
<mv-retry-errors> Contains information about metaverse objects that the Identity Integration Server could not synchronize.

Note  This error never occurs on export runs.
<ma-discovery-counters> Contains the values of some management agent discovery counters.
<staging-counters> 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.
<inbound-flow-counters> Contains information about the number of disconnectors which became connectors during this run and the disposition of existing connectors.
<outbound-flow-counters> 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.
<export-counters> Contains statistics on the number of changes sent out. If the step type is export, then this element will be present.

Parent Elements

Element
<run-details>

Child Element Sequence

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.

Sequence
	start-date
<start-date> Contains the date and time at which the step began. 
 (Exactly 1)
	end-date
<end-date> Contains the date and time at which the step completed.

Note  This element will be present only if the step has completed.

 
 (Minimum = 0; Maximum = 1)
	step-result
<step-result> Contains a non-localized string giving the current status of the step. 
 (Exactly 1)
	step-description
<step-description> 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). 
 (Exactly 1)
	current-export-step-counter
<current-export-step-counter> 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. 
 (Exactly 1)
	last-successful-export-step-counter
<last-successful-export-step-counter> 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. 
 (Exactly 1)
	ma-connection
<ma-connection> 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. 
 (Exactly 1)
	ma-discovery-errors
<ma-discovery-errors> 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). 
 (Minimum = 0; Maximum = 1)
	synchronization-errors
<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. 
 (Minimum = 0; Maximum = 1)
	mv-retry-errors
<mv-retry-errors> Contains information about metaverse objects that the Identity Integration Server could not synchronize.

Note  This error never occurs on export runs.

 
 (Minimum = 0; Maximum = 1)
	ma-discovery-counters
<ma-discovery-counters> Contains the values of some management agent discovery counters. 
 (Minimum = 0; Maximum = 1)
	staging-counters
<staging-counters> 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. 
 (Minimum = 0; Maximum = 1)
	inbound-flow-counters
<inbound-flow-counters> Contains information about the number of disconnectors which became connectors during this run and the disposition of existing connectors. 
 (Minimum = 0; Maximum = 1)
	outbound-flow-counters
<outbound-flow-counters> 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. 
 (Minimum = 0; Maximum = 1)
	export-counters
<export-counters> Contains statistics on the number of changes sent out. If the step type is export, then this element will be present. 
 (Minimum = 0; Maximum = 1)
Sequence

Element Information

Can be empty No