inbound-flow-counters Element
The <inbound-flow-counters> element contains information about the number of disconnectors which became connectors during this run and the disposition of existing connectors.
Usage
<inbound-flow-counters
ma = "ma"
id = "guid"
/>
Attributes
| Attribute | Type | Required | Description |
|---|---|---|---|
ma |
ma |
No |
The name of the management agent. |
id |
guid |
No |
The GUID of the management agent. |
Child Elements
| Element | Description |
|---|---|
|
Information about the number of connectors for which delete-add processing was performed. |
|
|
Information about the number of connectors that were deleted on this pass where the metaverse object was left in place. |
|
|
Information about the number of connectors that were deleted on this pass where the metaverse object was removed. |
|
|
Information about the number of connectors that were disconnected by the connector filter on this pass but the metaverse object was left in place. |
|
|
Information about the number of connectors that were disconnected by the connector filter on this pass where the metaverse object was removed. |
|
|
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. |
|
|
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 joined to that metaverse object. |
|
|
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. |
|
|
Information about the number of disconnectors that were run through the connector filter and marked as filtered disconnectors. |
|
|
Information about the number of disconnectors that were successfully joined by the synchronization engine for which attribute changes flowed to the metaverse. |
|
|
Information about the number of disconnectors that were successfully joined by the synchronization engine for which there was no attribute changes flowed to the metaverse. |
|
|
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. |
|
|
Information about the number of disconnectors that were projected by the synchronization engine for which attribute changes flowed to the metaverse. |
|
|
Information about the number of disconnectors that were projected by the synchronization engine for which there was no import attribute flow to the metaverse. |
|
|
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 lead to the removal of the metaverse object the synchronization engine was trying to create. |
|
|
Information about the number of disconnectors that successfully passed the connector filter filter test, but which there were no rules calling for them to project or join and hence now remain as normal disconnectors in the connector space. |
|
|
Information about the number of synchronization failures. |
Parent Elements
| Element |
|---|
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
disconnector-filtered (Exactly 1)
disconnector-projected-no-flow (Exactly 1)
disconnector-projected-flow (Exactly 1)
disconnector-projected-remove-mv (Exactly 1)
disconnector-joined-no-flow (Exactly 1)
disconnector-joined-flow (Exactly 1)
disconnector-joined-remove-mv
disconnector-remains (Exactly 1)
connector-no-flow (Exactly 1)
connector-flow (Exactly 1)
connector-flow-remove-mv
connector-filtered-leave-mv (Exactly 1)
connector-filtered-remove-mv (Exactly 1)
connector-delete-leave-mv (Exactly 1)
connector-delete-remove-mv (Exactly 1)
connector-delete-add-processed (Exactly 1)
flow-failure (Exactly 1)
Sequence
Remarks
The <inbound-flow-counters> element is present only if the step involves applying changes from the connector source to the metaverse.
The 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
Element Information
| Can be empty | No |
Send comments about this topic to Microsoft
Build date: 2/16/2009