This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IGIM Collector failing to register

I have a new IGIM Identity collector that is failing to register as a consumer for user objects.   Oddly, it is registering for group changes, but not for users.   In the collector, its configured to collect identity info, and the parameters all seem correct - when i kick off a manual collection, its retrieves data and identity just fine, but when I go look at  the driver filter, its missing user objects.  Similarly, when I look at the consumers that are registered with the rest endpoint, its missing a user consumer.    

Any thoughts on how to force the collector to re-register, or see how/why its failing to self-register?   It's odd that it partially registers, so I don't know if its the collector failing, or if the driver is failing. Trace didn't have anything interesting.  Do I need to crank up debug in the tomcat log?

--Jim

Tags:

  • 0  

    Correction, it IS registering a user consumer, but there is no filter with classes or attributes specified:

     {"consumerName":"IDMIdentityWithChangesTemplate-6-9-45d30dac84f14449b0280e1eb0fcb72d.user","consumerId":"7d884966-7795-4e6e-b195-43064787a280"}

  • 0  

    Hi Jim,

    am I understanding you correctly that the filter from the IGIM Driver is not being updated properly by the IG, or is the filter being updated but when the IG goes to get the changes it doesn't work?

    If the filter is not updated, then you could try to delete the attribute "DirXML-DriverStorage" (directly on the driver object in the IDM), the driver should be stopped. Then run a full import again to see if the driver is updated.

    If this doesn't help, then there is a more complex possibility which the support once sent me. I would look for it if the attribute removal does not work.



    BR

    Tobias