Hi Ivan,
roledefgenerator is not going to import anything. It will just generate a jar file for the target connector containing roledef + the attribute mapping. This jar will need to be deployed in IM and then, you will have to import the roledefinition as explained in the link I provided you previously.
It assumes that your ODI connector relies on DYN schema and you run roledefgenerator only for your ODI e.g.
VAPP-14.4.0:/opt/CA/IdentityManager/IAM_Suite/IdentityManager/tools/RoleDefinitionGenerator/bin > ./RoleDefGenerator.sh -h provserverhostname -u etaadmin ODI
Password:
Created folder /opt/CA/IdentityManager/IAM_Suite/IdentityManager/tools/RoleDefinitionGenerator/bin/./META-INF
Obtaining metadata doc...
Preparing data model...
Generating IM_FrameworkXml
Generating IM_ManagedObjectXml
Generating IM_ResourceBundle
Generating IM_JIAMToIMMappingXml
generateRoleDef called for IM_AccountManagementRoleDefXml
Generating search and list screens...
Generating account screens...
Generating account template screens...
Generating endpoint screens...
Generating role definitions...
persisting role def IM_AccountManagementRoleDefXml
Generating .jar file...
Done generating .jar file...
As expected, generatedItems map contains no entries
VAPP-14.4.0:/opt/CA/IdentityManager/IAM_Suite/IdentityManager/tools/RoleDefinitionGenerator/bin > ll
total 36
-rw-rw-r-- 1 config config 28308 Nov 9 16:08 ODI.jar
-rwxrwxr-x 1 config config 2444 Feb 19 2021 RoleDefGenerator.bat
-rwxrwxr-x 1 config config 1671 Feb 19 2021 RoleDefGenerator.sh
As a result, roledefgenerator has generated an ODI.jar. This is the one to deploy in IM and then you will have to import the roledef for this connector using immanage console (see the provided link for the steps)
Please, validate the steps 1st in a lower environment to validate everything before doing any action in production ;)
Hope this helps,
Joffrey.