I have created a RMI adapter for customer for ITIM 5.1 using ADT 3.1 .All the operations are working fine except Modify request.There is a strange behaviour I can see in the modify request.All the modify request for all the attributes are performing in delayed fashion.
Supose I have a attribute emailid and the attribute value in both ITIM and target is firstname.lastname@example.org. Now when I am modifying the emailid attribute value to email@example.com ,First time the person and the account emailid attribute value is changing to as desired but in the managed platform it shows the previous one that is firstname.lastname@example.org. After that when I modify the email attribute value to email@example.com it effects the person and Account as expected but in the target system Its showing the value what I have given in the previous modify request that is firstname.lastname@example.org. So modification of attribute value in managed platform is one step behind the ITIM person and account.
I have seen many post in the forum regarding the same issue but nobody gets any reply.
Its very urgent regarding client perspective so please give me some suggestion on this issue.
If you face and overcome same situation with ATD 3.1 or any other version please let me know the solution as early as possible and also you can provide me your suggestion by email
My emailid is email@example.com
For understanding below are the details
itim version 5.1
TDI version 7.0
Target system DB2
This topic has been locked.
1 reply Latest Post - 2012-10-08T12:53:01Z by yn2000
Pinned topic Modify request on managed platform is delayed one step
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-10-08T12:53:01Z at 2012-10-08T12:53:01Z by yn2000
yn2000 100000540S1075 PostsACCEPTED ANSWER
Re: Modify request on managed platform is delayed one step2012-10-08T12:53:01Z in response to SystemAdminITIM sends both values, the old value that being replaced and the new value that replacing the old one.
I guess your TDI code is choosing the old value.