The Operations in the Operation List are the existing ones from v3.0.0.1

The Op List is for IdB Changes it contains the follow:

• Schedule
• Check Operation - Identity Broker Change Operation
• Run Profile operation - Delta Import and Delta Sync on chris21 MA
• Run Profile operation - Delta Sync on chris21 MA

1 - Made change in chris21 by modifying part of a user name and bring in the Identity Broker
2 - Event Broker Check operation detected the change (returned "True")
3 - Event Broker perform Run Profile operation result in the error below

5/17/2011 4:22:00 PM	•	Information	UNIFY Event Broker	Operation List Executor	Operation list OpList - chris21 IdB - Incoming started
5/17/2011 4:22:00 PM	•	Information	UNIFY Event Broker	Operation List Executor	Running check operation Identity Broker Changes for operation list OpList - chris21 IdB - Incoming
5/17/2011 4:22:00 PM	•	Information	UNIFY Event Broker	Operation List Executor	Check operation Identity Broker Changes for operation list OpList - chris21 IdB - Incoming returned True
5/17/2011 4:22:00 PM	•	Error	UNIFY Event Broker	Operations	Operation 019455c9-1baa-4b00-8060-7c162fe50af6 failed in operation list with id 9ac60794-67eb-493d-9463-d73d94b02776 for the following reason. This is retry number 0: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Unify.Product.EventBroker.RunProfilePlugInFactory.CreateComponent(IOperationFactoryInformation factoryInformation)
at Unify.Framework.ExtensibilityPlugInGenerator`4.CreateComponent(TFactoryInfo factoryInformation)
at Unify.Product.EventBroker.StandardOperationListExecutor.RunNextOperations(IEnumerator`1 operationEnumerator)

When looking at the Operation List details it is found that the Operation names are no longer in plain text, it contains GUID, see image OpList-name-in-GUID.jpg for details

Edit the Operation by left click on the settings icon (wheel) and select "Edit operation" and then click "Update" restored the Operation name list, see image

This restored the Operation List above and allow the run profile to work correctly again. That is the run profile is now succeed.

5/17/2011 6:52:00 PM	•	Information	UNIFY Event Broker	Operation List Executor	Running check operation Identity Broker Changes for operation list OpList - chris21 IdB - Incoming
5/17/2011 6:52:00 PM	•	Information	UNIFY Event Broker	Operation List Executor	Check operation Identity Broker Changes for operation list OpList - chris21 IdB - Incoming returned True
5/17/2011 6:52:12 PM	•	Information	UNIFY Event Broker	Operation List Executor	Completed Run Profile operation with id 019455c9-1baa-4b00-8060-7c162fe50af6 in operation list OpList - chris21 IdB - Incoming
5/17/2011 6:52:14 PM	•	Information	UNIFY Event Broker	Operation List Executor	Completed Run Profile operation with id 63b94c5f-ec91-45dd-a073-11ea5dfcc8d7 in operation list OpList - chris21 IdB - Incoming
5/17/2011 6:52:14 PM	•	Information	UNIFY Event Broker	Operation List Executor	Operation list OpList - chris21 IdB - Incoming finished
5/17/2011 6:52:30 PM	•	Information	UNIFY Event Broker	Operation List Executor	Operation list OpList - chris21 IdB - Incoming started
5/17/2011 6:52:30 PM	•	Information	UNIFY Event Broker	Operation List Executor	Running check operation Identity Broker Changes for operation list OpList - chris21 IdB - Incoming
5/17/2011 6:52:30 PM	•	Information	UNIFY Event Broker	Operation List Executor	Check operation Identity Broker Changes for operation list OpList - chris21 IdB - Incoming returned False

This behaviour is very strange so that is why I am still creating this issue eventhough it seems to be resolved now through my action described above.

The "UNIFY Event Broker" service does not have a description.

The default authentication mode is different for each agent - for example, the FIM Agent defaults to SQL Authentication but the SQL Agent defaults to Windows Authentication.

A clear explanation is required as to how to configure the Event Broker scheduler such that ILM/FIM integrity is not compromised in the event of a failure in Startup processing.

I got some questions from Srini from IBM. They're building the DEV environments for DET.

We are having some issues with providing complete access to selective user(s) apart from the user that installed the product. Is this possible?

Also, please let us know if the product can be un-installed and re-installed without any issues. - I beleive this won't cause any issues but worth checking.

Could not read the PDF because there was no PDF reader on the server. I was after the configuration xml for UNService.exe.config and UNConsole.exe.config, and had to email myself the PDF to view it. The online doco only has an entry for the Identity Broker 2.* plug-in (see separate issue).

As per Shane's response to a similar issue I had with Identity Broker for FIM documentation, "... I do however agree with PDF not being suitable for servers, so in future I believe PDF, XPS and TXT should be supplied if notes are ever supplied in future installers"

A clear desciption is required on how to configure (exclusive) Startup processing, particularly since backwards-compatibility must be achieved for the vast majority of existing Event Broker 2.* sites where this is a critical implementation feature.

Srini is telling me that in the DEV environment (that we don't have access to) he requires the AD and MIIS plugins for Event Broker. It was my understanding that in the current version, 2.2.3, these were already packaged with the standard Event Broker installation. Is this correct? If not, is it alright for me to send them to him?

If a valid license has been submitted a second license cannot be submitted.

Determine whether the ability to post multiple times from the same form should be protected against, or whether it is intended (albeit fringe) functionality.