Working solution with IDB 5.0.3. Installed 5.0.4 and the custom connector for CAMS failed with:

Change detection engine import all items for connector CAMS User failed with reason Method not found: 'Void Unify.Product.IdentityBroker.DirectEntityFieldsToFieldListConverter..ctor()'..

Richard Green has modified his connector

From Identity Broker 5 web console, the about link presents incomplete version information (missing the major version)

Using IDB5 (5.0.3 - not yet confirmed if this is still an issue with 5.0.4, but looking at the list of fixes, I suspect so).

Exporting a user to DET's CAMS system, for which a connector has been written. In Dev the system uses a dummy web service front end to allow users to be exported. If an export occurs when the service is unavailable, then an error is returned to the MA (in this case a missing end point error). That is as expected.

At this point, an entity search in the adapter does not show the user as being there.

Starting the web service and repeating the export from FIM, gives a cd-existing-object error.

To enable the export to complete successfully, it was necessary to run an import all on the the IDB5 connector - even though this reported no pending changes and no change to the number of adapter entities.

Any idea what might be going on?

When searching adapter space and trying to filter on a GUID based attribute, if the value put in the filter is not a GUID, then a System.FormatException is thrown (no surprise there). The problem is (and I am not sure if this is a bug or simply how it should behave) that I cannot find any way to clear that error or clear the filter. The only way to get a valid entity search screen back is to restart the service or restart the browser. It would be nice if refreshing the adapter view or re-selecting the entity count would present the normal entity list

Adding of the signing of log files whould ensure that we can show they were not modified, which would in turn provide a chain of evidence for auditors...

Task:
Installation of Identity Broker for SAP HCM

Task List:
1. Install Identity Broker service
2. Configure Identity Broker service
3. Install and configure connector and adapter components.

After the successfull installation of Identity Broker service the Identity Broker database was created and the Identity Broker script ran sucessfully. The next step was to configure the service with the datbase connection details as given below. Upon starting the Identity Broker service the following error was captured as given below.

The error indicates that the connection string is missing in the configuration file however the string is present in the DataEngine.extensibility.config.xml configuration.

DataEngine Configuration:
<DataEngine>
<dataRepository>
<dataConnection name="sql" repository="FIM_DEV_Unify_IdentityBroker" connectionString="Data Source=amausgcdbad05;Initial Catalog=FIM_DEV_Unify_IdentityBroker;Integrated Security=True" />
</dataRepository>
</DataEngine>

DataEngine Configuration Values:
Database type = SQL
Database server = amausgcdbad05
Database Name = FIM_DEV_Unify_IdentityBroker

Event Viewer:

• <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
• <System>
  <Provider Name="UNIFY Identity Broker v3.0 service" />
  <EventID Qualifiers="0">0</EventID>
  <Level>2</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2011-01-11T23:07:57.000000000Z" />
  <EventRecordID>1264</EventRecordID>
  <Channel>Application</Channel>
  <Computer>AMSGCQAP01.int.alliedmills.com.au</Computer>
  <Security />
  </System>
• <EventData>
  <Data>Service cannot be started. Unify.Framework.AdoNetDataControlConfigurationException: Missing connectionString attribute from <dataConnection name="sql" repository="FIM_DEV_Unify_IdentityBroker" /> at Unify.Framework.AdoNetDataControlFactoryBase.SetConfiguration(XElement configurationElement) at Unify.Framework.SqlServerDataControlFactory..ctor(XElement element) at Unify.Framework.SqlServer.SqlServerDataControlGenerator.CreateComponent(XElement element) at Unify.Framework.PlugInGeneratorBase`4.CreateComponent(TFactoryInfo factoryInformation) at Unify.Framework.StoredValuesEngine..ctor(IAdoNetDataControlGenerator dataControlGenerator, DirectoryInfo executingAssemblyDirectory) at Unify.Framework.StoredValuesEnginePlugInFactory.CreateComponent(IUnifyEnginePlugInFactoryInformation factoryInformation) at Unify.Framework.DependencyPlugInGenerator`4..ctor(ICollection`1 plugInGenerator, IPlugInFactory`2 factoryInformationFactory) at Unify.Framework.UnifyEngine..ctor(IEnumerable`1 additionalPlugInFactories, Di...</Data>
  </EventData>
  </Event>

Just some immediate gut reactions to trying to configure an adapter DN (before I have long enough to think like a developer and justify it)

• It's a bit confusing as to how to go to edit the DN template. The path you take is to "Edit Adapter Properties" and on its second screen, but I wouldn't have immediately known by looking at it. This is also a bit confusing after IdB 4 lets you click directly on the DN template button
• Mousing over the template shows the "Edit" word at the very right hand side of the template window. My instinct was to go "yes I do want to edit it, click where my mouse is to edit it". Instead, you have to go over to the Edit button to do so.

Would be worth getting some other opinions on how people feel when using it but those were my immediate reactions

Currently the service requires local admin to register it automatically or it must be registered manually. Have had numerous requests to see if we can automate this, most recently from Aurion Corp. Alternatively we'll need to include the script in the installer or something so that the process is much easier.

The following error is being investigated with internal sql dba's. Whenever i attempt to do a full import from the ADW MA it will begin to generate the UNIFYFull.txt file "file partially built) then fails with a stopped-extension-dll-exception.

Error occurred in module: Adapter Adapter get all entities for adapter db19b111-cc07-4343-b668-5caa25efe771 failed with reason Transaction (Process ID 105) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.. Duration: 00:01:47.9019691 Error details: System.Data.SqlClient.SqlException: Transaction (Process ID 105) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.HasMoreRows() at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout) at System.Data.Linq.SqlClient.ObjectReaderCompiler.ObjectReaderBase`1.Read() at System.Data.Linq.SqlClient.ObjectReaderCompiler.ObjectReader`2.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at System.Linq.Buffer`1..ctor(IEnumerable`1 source) at System.Linq.Enumerable.ToArrayTSource(IEnumerable`1 source) at Unify.Framework.LinqWhereQuery`5.GetEnumerator() at Unify.Framework.QueryableExtensions.<AutoStream>d_b`1.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at Unify.Framework.EnumerableExtensions.<ProduceAutoPages>d9`1.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at Unify.Framework.EnumerableExtensions.<ActionOnLast>d16`1.MoveNext() at System.Linq.Enumerable.<SelectManyIterator>d14`2.MoveNext() at Unify.Framework.EnumerableExtensions.<ActionOnLast>d16`1.MoveNext() at System.Linq.Enumerable.<SelectManyIterator>d14`2.MoveNext() at Unify.Framework.EnumerableExtensions.<ActionOnFirst>d1c`1.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at Unify.Framework.ActionOnExceptionEnumerator`1.MoveNext() at Unify.Framework.EnumerableExtensions.<ActionOnLast>d16`1.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at System.Linq.Enumerable.<SelectManyIterator>d14`2.MoveNext() at System.Linq.Enumerable.<ConcatIterator>d71`1.MoveNext() at Unify.Framework.LDIFComponentFileGenerator`1.GenerateFile(TextWriter writer, IEnumerable`1 entries) at Unify.Framework.LDIFAdapter.<>cDisplayClass5`1.<CreateLDIFComponentStream>b_4(Stream stream) at Unify.Framework.LazyEvaluationStream.Evaluate(Object obj)

I've attached two screen shots of how Identity Broker 5.0.1 is rendered in IE8, which according to the documentation is supported (IE8+). I've had access to two systems with IE8, both of which exhibit these symptoms. The first being a Windows Server 2008 system and the other a clean install of Windows 7 that I made in Azure specifically to see if this issue was reproducible.

As can be seen below, quirks mode is functional but misformed. In standards mode much of the page is obscured by the upper pane, including most of the controls associated with the connectors or adapters pages.

Browser Mode: IE 8, Document Mode: Internet Explorer 8 Standards

Browser Mode: IE 8, Document Mode: Quirks

In both cases Identity Broker is running on the embedded web server. Screenshots taken with 8.0.7601.17514 of IE.