OIM OID CONNECTOR

Question

i interfaced OIM with Oracle 10 g database instance using database connector. i installed the connector using a database user account by giving some privileges (sysadmin which is admin account of that database instance was not able to install the connector,so i created a new database user and gave him the privileges by running OIM.bat file)
now i m trying to interface OIM with OID. it says that system admin or any user with certain privileges can install a connector.
The required permissions are the following:
Form Designer (Allow Insert, Write Access, Delete Access)
Structure Utility.Additional Column (Allow Insert, Write Access, Delete Access)
Meta-Table Hierarchy (Allow Insert, Write Access, Delete Access)
In that case which user can i use. may i use the admin credentials of OIM (xelsysadm) or do i need to create a new user with relevant privileges
how can this be materialised?
i m constantly getting INVALID_NAMING_ERROR while i try to provision OID IT Resource to the users in OIM.
what can be the reason
Edited by: user12240044 on Jan 12, 2010 8:43 PM
i configured the target system by modifying the custom.bat file as follows :
ldapmodify -h hostname -p 4389 -D "cn=orcladmin" -w "adminpassword" -c -f customRoleOccupant.ldif
ldapadd -h hostname -p 4389 -D "cn=orcladmin" -w "adminpassword" -c -f customIndex.ldif
ldapmodify -h hostname -p 4389 -D "cn=orcladmin" -w "adminpassword" -c -f customOrganizationalRole.ldif
then i run the custom.bat file
is it must to make modifytimestamp a searchable attribute. why is it needed?
Edited by: user12240044 on Jan 12, 2010 9:02 PM
Admin Id     cn=orcladmin,cn=Users,dc=ad,dc=infosys,dc=com
Admin Password     ******
CustomizedReconQuery     
Last Target Delete Recon TimeStamp     
Last Target Recon TimeStamp     
Last Trusted Delete Recon TimeStamp     
Last Trusted Recon TimeStamp     
Port     389
Prov Attribute Lookup Code     AttrName.Prov.Map.OID
Recon Attribute Lookup Code     AttrName.Recon.Map.OID
Root DN     dc=ad,dc=infosys,dc=com
SSL     false
Server Address     given
Use XL Org Structure     true
Edited by: user12240044 on Jan 12, 2010 9:39 PM

Answer 1

Although the documentation does not make any mention of it AT ALL, you need to add modifytimestamp to the ldapTargetResourceTimeStampField in the recon lookup attribute map. The modifytimestamp attribute in OID then needs to be indexed so that it can be used in the LDAP search the connector makes.