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

Available scripts and objects in synchronization engine mapping scripts

 I am not finding any documentation that discusses the available scripts, objects, and functions that are able to be referenced from within a synchronization engine mapping script.  I would like to be able to reference the custom schema type (filter), the mapping object name, or other properties of the mapping or workflow that should be available at run time.  The goal in this scenario is to be able to connect to an LDAP system that doesn't natively have groups exposed.  I have created a custom filtered schema class and a mapping that references the new class, but the value for vrtStructuralObjectClass (in browse) shows the parent schema class instead of the one selected during the mapping creation.  I need some way of determining which mapping is currently running so that I can use that information in a property mapping script (OU selection).

Parents
  • True, but I was using it only as a simple example.

    Maybe a better example:

    Suppose you have a custom target system in a SQL database which stores information about a container structure without giving us the full DN. (For each row, it exposes the CN and parent CN only).

    I've mocked this up in a VM.

    If Identity Manager is not given a DN at all, it will construct a DN for each container which will look like this:

    CN=container, CN=ParentContainer, system=TargetSystem

    However, that might not match the container structure from the target system's perspective - which might be like this:

    OU=Container, OU=ParentContainer, DC=TargetSystem, DC=Company, DC=com
Reply
  • True, but I was using it only as a simple example.

    Maybe a better example:

    Suppose you have a custom target system in a SQL database which stores information about a container structure without giving us the full DN. (For each row, it exposes the CN and parent CN only).

    I've mocked this up in a VM.

    If Identity Manager is not given a DN at all, it will construct a DN for each container which will look like this:

    CN=container, CN=ParentContainer, system=TargetSystem

    However, that might not match the container structure from the target system's perspective - which might be like this:

    OU=Container, OU=ParentContainer, DC=TargetSystem, DC=Company, DC=com
Children
No Data