MIM Event Broker Forum
Welcome to the community forum for MIM Event Broker.
Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.
Need a more intuitive interface for the AD changes plug-in
Not really sure how to phrase this, but I spent several hours today (yes hours!) unsuccessfully configuring both of the AD changes plugins ... no matter what I tried, I was unable to get anything back but the following in the log files:
20110502,06:26:51,UNIFY Event Broker,Agent Engine,Warning,"The test of Agent UNIFYFIM AD (d3187109-fc0d-41f9-bd94-3a60a8757457) failed with message:
System.Runtime.InteropServices.COMException (0x80005000): Unknown error (0x80005000)
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_SchemaEntry()
at Unify.Product.EventBroker.ADAgent.TestConnection()
at Unify.Product.EventBroker.AgentEngine.Notify(ITestAgentConnectionMessage message)",Normal
The exception stacks themselves are far from intuitive, and I know how difficult it is to get anything more meaningful from the System.DirectoryServices interfaces because I've been working with them myself for years. The problem is that EvB needs to be at least as easy (hopefully better) to work with as LDP.EXE (in c:\windows\adam), but at the moment you don't find out if there is something wrong until you run the scheduler, and then all you get is a generic message. The home page is helpful in identifying the general proximity of the problem, but in my case I found myself in trial-and-error mode. It shouldn't be that hard really ... if you're using a domain account you need a domain name as part of your credentials ... but try as I may I couldn't connect to AD, which should be one of the easiest plug-ins to configure (since it's by far the easiest MA to configure).
Run out of time to add more explanation ... way too tired and have to get up again in 4 hours ... but to get a feel for my pain today I would have really had to record my session . Perhaps this is the best way I can illustrate my problem ... by showing the different strings I tried in each of the following 3 fields alone (UNIFYFIM is the domain name):
Server: localhost; CENTRELINK-FIM; UNIFYFIM; CENTRELINK-FIM.unifyfim.unifytest.local
Username: administrator;unifyfim\administrator;unifyfim
administrator;administrator@unifyfim;administrator@unifyfim.unifytest.local
Authentication: Secure; Basic
All combinations and permutations of the above seemed to result in the same error.
Also, I had to resort to restarting the Event Broker service (not the scheduler, the main service) because I wasn't confident that a process hadn't hung on me, because the circular "processing" icon just seemed to persist for ever after an exception had occurred.
In summary, I think this needs more attention as it will definitely be the source of the most grief for any potential client if it's not as least as easy to use as the AD MA.
Default start from times on the schedule should default to the current time
Base occurrences default with a "start from time" of 12pm. It may be easier if the behaviour from Event Broker v2.x is used here instead, in that the default time should be the current time. This will mainly be of assistance in ensuring all operations are not all running at the same time. The alternative is that most configurations will have all import and export checks occurring at the exact same second for all operation lists.
Operation List for Identity Broker for chris21 failed
I have a composite Adapter for chris21 with the AdapterId=
{D5251D7D-05CC-4d35-916E-E99E06B9FFD3}I can perform various Run Profile operation from FIM on chris21 MA without issue.
I can also scheduled am Operation
List without the Check Operation to perform the Run Profile operation - Full Import and Full Sync through Event Broker successfully.
In Event Broker v3.0.0.1 I created a chris21 Agent with the following settings:
Name: chris21-pdt_MA-AHG
Endpoint Address: http://localhost:59990/IdentityBroker/ChangesAvailableAdapter.svc
Endpoint Configuration: IdentityBroker
Note: For the Endpoint Address, the tip provided as the possible parameter does not include the ending /mex as documented in Identity Broker Changes
Thus one of the above source of information is out of date.
- Create an Operation List, name: OpList - chris21 IdB - Incoming
- Added a Schedule: Runs every 00:00:30 from 5/2/2011 12:00:00 PM
- Added a Check Operation with the following settings:
** Retries: 2
** Retry wait time: 00:02:00
** Select Agent: chris21-pdt_MA-AHG
** AdapterId: {D5251D7D-05CC-4d35-916E-E99E06B9FFD3}
(but being automatically replaced to D5251D7D-05CC-4d35-916E-E99E06B9FFD3)
- Added two Standard Operations for Run Profile operations.
When this Operation List is enabled and the following error occurred:
/3/2011 12:50:07 PM Warning UNIFY Event Broker Agent Engine The test of Agent ADDS MA-AHG (32c0ad55-b955-42c0-9194-fd73e2752fb7) failed with message: System.Runtime.InteropServices.COMException (0x80005000): Unknown error (0x80005000) at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_SchemaEntry() at Unify.Product.EventBroker.ADAgent.TestConnection() at Unify.Product.EventBroker.AgentEngine.Notify(ITestAgentConnectionMessage message) 5/3/2011 12:50:31 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.Runtime.Remoting.ServerException: Operation for management agent with id f0fada76-9b8d-42ab-aee2-5de0b22b576a with name Delta import and delta synchronization failed with result call-failure:0x800706BE at Unify.Product.EventBroker.FIMAgent.ExecuteRunProfile(IStoredValueCollection storedValuesCollection, Guid agentId, Guid managementAgentId, Guid runProfileId) at Unify.Product.EventBroker.RunProfilePlugIn.Execute() at Unify.Product.EventBroker.StandardOperationListExecutor.RunNextOperations(IEnumerator`1 operationEnumerator) 5/3/2011 1:05:07 PM Warning UNIFY Event Broker Agent Engine The test of Agent ADDS MA-AHG (32c0ad55-b955-42c0-9194-fd73e2752fb7) failed with message: System.Runtime.InteropServices.COMException (0x80005000): Unknown error (0x80005000) at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_SchemaEntry() at Unify.Product.EventBroker.ADAgent.TestConnection() at Unify.Product.EventBroker.AgentEngine.Notify(ITestAgentConnectionMessage message)
The Operation List status has a "Running" icon next to it and reporting that it is performing the operation 1 of 3.
When change the Agent setting to include the /mex to the Endpoint Address as below
In Event Broker v3.0.0.1 I created a chris21 Agent with the following settings: Name: chris21-pdt_MA-AHG Endpoint Address: http://localhost:59990/IdentityBroker/ChangesAvailableAdapter.svc/mex Endpoint Configuration: IdentityBroker
I got the following error instead.
3/2011 12:45:30 PM Error UNIFY Event Broker Operations Operation 65ac34b8-2148-4650-90b8-7369f76a27c4 failed in operation list with id 9ac60794-67eb-493d-9463-d73d94b02776 for the following reason. This is retry number 1: System.ServiceModel.EndpointNotFoundException: The message with To 'http://localhost:59990/IdentityBroker/ChangesAvailableAdapter.svc/mex' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver's EndpointAddresses agree. Server stack trace: at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter) at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Unify.Framework.IChangesAvailableAdapter.ChangesAvailable(Guid adapterId) at Unify.Product.EventBroker.IdentityBrokerChangesPlugIn.Check() at Unify.Product.EventBroker.StandardOperationListExecutor.RunCheck(ICheckOperationFactoryInformation checkOperation) 5/3/2011 12:47:30 PM Error UNIFY Event Broker Operations Operation 65ac34b8-2148-4650-90b8-7369f76a27c4 failed in operation list with id 9ac60794-67eb-493d-9463-d73d94b02776 for the following reason. This is retry number 2: System.ServiceModel.EndpointNotFoundException: The message with To 'http://localhost:59990/IdentityBroker/ChangesAvailableAdapter.svc/mex' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver's EndpointAddresses agree. Server stack trace: at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter) at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Unify.Framework.IChangesAvailableAdapter.ChangesAvailable(Guid adapterId) at Unify.Product.EventBroker.IdentityBrokerChangesPlugIn.Check() at Unify.Product.EventBroker.StandardOperationListExecutor.RunCheck(ICheckOperationFactoryInformation checkOperation)
Is there a File based Agent available for FIM File based MA?
I noticed that there is no File based Agent in the Agents list available in the Agents tab for managing FIM File based MA.
Currently I have no requirement for it. I thought I ask because it may be in the pipeline for the next version.
Add root operation button still visible after a root operation has been added
Because the add next and add child operations are part of the operations menu, this link should disappear after at least one operation exists.
Move related fields into fieldsets in agents and operations
Related fields should be grouped together in fieldsets, as is the case in a number of the agents and operations already (eg. the FIM agent). This should be done for the remaining operations also, eg. retry settings and success/failure actions in one field set, configuration-related settings in another
AD Agent authentication type should not default to custom
The AD Agent screen should not default to Custom authentication - it is quite confusing for a new user. Basic or Secure should be selected instead.
AD Agent Custom by Default.png
Tooltip on Identity Broker agent not properly formatted
The tooltip for the endpoint address on the Identity Broker agent does not sit properly within the hint box. This is likely because the example URL is too long (see screenshot)
Identity Broker Endpoint Hint Too Long.png
What is the icon next to the agent on the index page meant to mean?
There is a warning icon next to the agent in the agents index page.
I assume it's a connection thing, but there are no tooltips or messages.
See attached.
screen.png
Incorrect operation list execution details
The operation list execution details page on the operations controller is missing a field, and does not reflect the details as shown on the operation details page.
Customer support service by UserEcho
