<inbound-flow-counters>
Contains information about the number of disconnectors that became connectors during this run, and the disposition of existing connectors.
Schema Hierarchy
<run-history>
<run-details>
<step-details>
Syntax
<inbound-flow-counters>
<disconnector-filtered>
</disconnector-filtered>
<disconnector-joined-no-flow>
</disconnector-joined-no-flow>
<disconnector-joined-flow>
</disconnector-joined-flow>
<disconnector-projected-no-flow>
</disconnector-projected-no-flow>
<disconnector-projected-flow>
</disconnector-projected-flow>
<disconnector-joined-remove-mv>
</disconnector-joined-remove-mv>
<disconnector-projected-remove-mv>
</disconnector-projected-remove-mv>
<disconnector-remains>
</disconnector-remains>
<connector-filtered-remove-mv>
</connector-filtered-remove-mv>
<connector-filtered-leave-mv>
</connector-filtered-leave-mv>
<connector-flow>
</connector-flow>
<connector-no-flow>
</connector-no-flow>
<connector-delete-remove-mv>
</connector-delete-remove-mv>
<connector-delete-leave-mv>
</connector-delete-leave-mv>
<connector-delete-add-processed>
</connector-delete-add-processed>
<connector-flow-remove-mv>
</connector-flow-remove-mv>
<flow-failure>
</flow-failure>
</inbound-flow-counters>
element
Attributes and Elements
The following sections describe attributes, child elements, and parent elements.
Attributes
| Attribute | Type | Required | Description |
|---|---|---|---|
|
id |
guid |
The GUID of the management agent. |
|
|
ma |
ma |
The name of the management agent. |
Child Elements
| Element | Min Occurs | Max Occurs | Description |
|---|---|---|---|
1 |
1 |
Contains information about the number of connectors for which delete-add processing was performed. |
|
1 |
1 |
Contains information about the number of connectors that were deleted on this pass in which the metaverse object was left in place. |
|
1 |
1 |
Contains information about the number of connectors that were deleted on this pass in which the metaverse object was removed. |
|
1 |
1 |
Contains information about the number of connectors that were disconnected by the connector filter on this pass, but the metaverse object was left in place. |
|
1 |
1 |
Contains information about the number of connectors that were disconnected by the connector filter on this pass in which the metaverse object was removed. |
|
1 |
1 |
Contains information about the number of connectors that passed the connector filter test and remained connectors. When import attribute flow was applied, new or changed values flowed to the metaverse. |
|
Contains information about the number of existing connectors that passed the connector filter test and had import attribute flow applied to them, but had their metaverse object removed because the provisioning extension disconnected the connectors that joined to that metaverse object. |
|||
1 |
1 |
Contains information about the number of connectors that passed the connector filter test and remained connectors. When import attribute flow was applied to these connectors, no attributes flowed to the metaverse. |
|
1 |
1 |
Contains information about the number of disconnectors that were run through the connector filter and were marked as filtered disconnectors. |
|
1 |
1 |
Contains information about the number of disconnectors that were successfully joined by the synchronization engine for which attribute changes flowed to the metaverse. |
|
1 |
1 |
Contains information about the number of disconnectors that were successfully joined by the synchronization engine for which no attribute changes flowed to the metaverse. |
|
Contains information about the number of disconnectors that the synchronization engine joined to metaverse objects in the first part of the synchronization process, but removed when the provisioning extension disconnected its connectors. |
|||
1 |
1 |
Contains information about the number of disconnectors that were projected by the synchronization engine for which attribute changes flowed to the metaverse. |
|
1 |
1 |
Contains information about the number of disconnectors that were projected by the synchronization engine for which there was no import attribute flow to the metaverse. |
|
1 |
1 |
Contains information about the number of disconnectors that the synchronization engine tried to project to the metaverse, but in the process, the provisioning extension disconnected the connectors, which led to the removal of the metaverse object that the synchronization engine was trying to create. |
|
1 |
1 |
Contains information about the number of disconnectors that successfully passed the connector filter test, but for which there were no rules calling for them to project or join, and so they remain as normal disconnectors in the connector space. |
|
1 |
1 |
Contains information about the number of synchronization failures. |
Parent Elements
| Element | Description |
|---|---|
Stores run information about one step of the management agent run. |
Remarks
The <inbound-flow-counters> element is present only if the step involves applying changes from the connector source to the metaverse. The user interface (UI) view of the run statistics relates to the XML counts as follows:
Projections = disconnector-projected-no-flow + disconnector-projected-flow + disconnector-projected-remove-mv
Joins = disconnector-joined-no-flow + disconnector-joined-flow + disconnector-joined-remove-mv
Filtered Disconnectors = disconnector-filtered
Disconnectors = disconnector-remains
Connectors with Attribute Flow Updates = connector-flow + disconnector-projected-flow + disconnector-joined-flow + connector-flow-remove-mv
Connectors without Attribute Flow Updates = connector-no-flow + disconnector-projected-no-flow + disconnector-joined-no-flow
Filtered Connectors = connector-filtered-leave-mv + connector-filtered-remove-mv
Deleted Connectors = connector-delete-leave-mv + connector-delete-remove-mv
Metaverse Object Deletes = disconnector-projected-remove-mv + disconnector-joined-remove-mv + connector-flow-remove-mv + connector-delete-remove-mv + connector-filtered-remove-mv