I understand from the doco that "polling " means a delta import from the connected system - true ?
We will need a connector built for DBB CSO and there will be 16,500 students to import from source.
It makes sense to build this new connector with delta import (and full) from connected system meaning "polling"
Which current IB connectors support polling?
Is building a new SQL connector with polling straightforward for the PG?

TIA

I have developed some generic XSLT stylesheets while working on FIM @ DEEWR to generate documentation for both Event Broker 3.0 and Identity Broker 3.0. These stylesheets are designed as an extension to the standard generated FIM documentation by utilizing the same "Object Visualizer" Powershell/XSL/HTA tool that is freely downloaded from the FIM Microsoft TechNet website (follow references to this tool from the FIM JIRA project).

The latest version of these XSLT documents are available from myself on request.

I know that earlier versions of the Aurion broker were artificially limited to writing back telephone number only with EMP_UPD_PERS. Has that restriction been lifted? If so, is it all attributes available in the API Function of just a select number?

I may have asked for this before, so please delete if this is a duplicate. A common problem is that connectors often include a vast number of columns that you don't want or need surfaced to the adapter layer ... and the only remedy is to delete the attributes from the generated FIM MA schema. This does not prevent the generated LDIF from including these redundant columns, however, and they only come back again if you need to regenerate your FIM MA.

Please confirm that there are no requirements for updates to the Broker solution if the client upgrades from Aurion 10.1 to Aurion 10.2

The installation of Identity Broker 4.0 itself was quick and painless. There was a minor issue with the delayed enabling of the "Next" button--it seems the form validation is not re-evaluated until focus is changed to another field.

The creation of the chris21 Connector was based on the chris21 details form. Executing an Import All brought in the ~1200 entities (the addition of a progress bar is a nice feature as it removes the relative arbitrariness of progress seen in the previous version).

Other/minor notes (apologies if these have been documented already):

The required miiserver config file alteration is slightly different to the previous version of Identity Broker.

• As noted in https://unifysolutions.jira.com/browse/IDB-467; the "contract" attribute of the //configuration/system.serviceModel/client/endpoint node should be "IdentityBrokerLDIFAdapter.ILDIFAdapter".
• Is there any way the configuration changes could be automated in a future version?

If a dropdown menu is visible, navigation outside of that menu is prevented. (IE8)

Is it possible to also have the text in menu dropdowns hyperlinks, rather than just the icon it corresponds to?

Perhaps an intended feature to distinguish highlighted items, but the icons for the respective Connectors/Adapters enlarge on mouse over.

I was having an issue with Polling Imports so unfortunately was not able to test changes. I will update with these and other experiences upon further testing.

Thanks,

Christian

The alt/title text which appears on mouse hover for an adapter group operation (e.g. delete, update details) instead refers to that action being performed on a connector group.

On the page "Time Offset", because the content box has a fixed size, only very limited number of field name can be displayed in "Offset Field" drop down list. It is a bit hard to go through the list, if there are lots of fields.

Creation of a new Connector:

Pending Configurations - Can IdB ask the user if they want to navigate away and loose unsaved changes where possible & do away with pending configs?

Identity Broker Update Connector Config only allows modification of:
#Name
#Comment
#Queue when blocked
This functionality should be moved into the Connector configuration.