This does not work out of the box, but can be configured.
Domain:
ident_domain distinguishedname ADSDomainName
myldapdomain DC=myldap,DC=loc myldap.loc
myldapdomain2 dc=myldap,dc=loc myldap.loc
When a domain is created, a top container is created. Since this is a special setup, the second top container you create has to be renamed manually via SQL, like this:
LdapContainer:
ident_domain distinguishedname cn ObjectClass
myldapdomain dc=myldap,dc=loc myldap.loc TOP
myldapdomain2 dc=myldap,dc=loc myldapdomain2 TOP
In the mapping for each domain, you have to configure a where clause for organizationalUnit:
myldapdomain
lower(Distinguishedname) like lower(N'%DC=myldap,DC=loc%') and
ObjectClass like '%ORGANIZATIONALUNIT%'
and Ident_Domain=N'myldapdomain'
myldapdomain2
lower(Distinguishedname) like lower(N'%DC=myldap,DC=loc%') and
ObjectClass like '%ORGANIZATIONALUNIT%'
and Ident_Domain=N'myldapdomain2'
Any container that is read from LDAP which is a direct child of the top container has to be assigned to the correct top container manually via SQL.
The information in the script(s) provided is known to work successfully; however, they have not been officially tested by One Identity Quality Control. If any of these instructions are changed and/or incorrectly used, intentionally or unintentionally, this solution becomes unsupported by One Identity Support and Development. One Identity Support and Development recommend always making a backup of the current database prior to execution of any script(s) that may modify it. For customization of One Identity Manager, please contact our Professional Services Organization.