If the Event Broker scheduler is in a 'Started' state, and it becomes unlicensed, the scheduler will maintain this state until the service is restarted

.

To reproduce this behaviour:

1. Start the EventBroker service
2. Ensure that the scheduler has started
3. Add a license that expired before the day of reading.
4. Ensure that the Event Broker instance is now unlicensed and that the scheduler has maintained this state.

The check operation added will overwrite the existing check operation.

A few issues were found when playing with operation list functions in IE9 to see what more expansive operation lists would look like in the browser. These include:

• If an operation is moved below an operation with children, all the children disappear (the root operation remains)
• I had an operation with 3 levels (root, child, then 2 children of the child). I "moved down" one of the 2 children, and it cleared all children, leaving only the root
• Operations cannot be promoted at any level, whether added initially as children, or demoted to become a child
• After performing the above tests in IE9, the operations functions menu became unresponsive and the browser could not contact the running Event Broker service. I was not able to replicate this after performing a far larger test using IE9, however (ie. adding more children, moving and demoting some operations).

While IE9 for the most part seems to have fields a bit closer together than in Chrome, the Create Group and LDAP Directory Agent pages have no spaces between key fields. See attached screenshots.

When you install or uninstall Event Broker on a machine with UAC active (eg. Windows 7), the MSI name in the Program Name field when installing, repairing, or uninstalling, is an unintelligible collection of letters and numbers (eg. 8eb628.msi). The publisher is correctly verifiable, but should this be the name of the Event Broker MSI rather than this name?

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.