While unsuccessful in creating the FIM Agent, I was however able to create Operations and Operation Lists ... albeit incomplete. This was only possible after deleting the ill-configured FIM Agent, as while this was in existence, the following error details were generated:
System.ServiceModel.FaultException`1System.ServiceModel.ExceptionDetail: Access denied (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.UnauthorizedAccessException: Access denied ----> System.Management.ManagementException: Access denied at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at Unify.Product.EventBroker.FIMAgent.GetManagementAgents() — End of inner ExceptionDetail stack trace — at Unify.Product.EventBroker.FIMAgent.UnauthorizedAccessExceptionHandler(ManagementException managementException)
at Unify.Product.EventBroker.FIMAgent.ExceptionHandlerT(T exception, IEnumerable`1 exceptionHandlers)
at Unify.Product.EventBroker.AgentRequestResponseEngine.FIMAgentGetManagementAgentsRequestAction(IAgent agent, XElement details, Guid agentId)
It is obvious from the stack that the FIM Agent is intended to support retrieval of management agent details, so the question remains what of the FIM MA itself? I am suspecting this is an oversight to some extent ... but I hope it isn't, as it's part of the core FIM configuration itself (a special MA case), with its own run profiles like any other MA, and is the reason for the need for the new FIM Portal Integration plug-in developed by Matt.
Customer support service by UserEcho