Connecting via 'Universal Cloud Interface' vs 'Custom Target System'

What are the cons/pros when choosing to connecting a target system via a Universal Cloud Interface vs Custom Target System.

As I understand the main advantage of using the 'Universal Cloud Interface' (CMSUser <> UCIUser <> Target system)
is the ability to synchronize between another OneIM instance so: sync from CMSUSER@OneIM_A <> UCIUSER@OneIM_B <> Target System A)

But when your environment consist of just one OneIM instance.
Then the case for using the Custom Target System looks far more favorable (Universal Cloud Interface has that extra sync layer)

Especially when you also want to use a custom tabel from which you want to provision/sync: UNSAccountB <> CCC_TSA_User <> Target system A
For a lot of target systems I create a custom table that represent the data structure/formating of the target system.
So it's much easier to understand/troubleshoot things instead of doing all the data conversions in "runtime" via virtual attributes/scripts.

Any input will be greatly appreciated!

Parents
  • Hello Niels,

    I didn't even know that was possible to use the Custom Target System only. 

    In that case, does it mean we can get rid of the UCIUser layer and we can work with something more classical like this : PERSON<>CMSUSER<>Target System ? 

    Is it contradictory with the tool philosophy to work like this ? To be honest, the added value of the UCI layer is especially doubtful to me. 

    Many thanks for you help / advice. 
     
    Michel 

Reply
  • Hello Niels,

    I didn't even know that was possible to use the Custom Target System only. 

    In that case, does it mean we can get rid of the UCIUser layer and we can work with something more classical like this : PERSON<>CMSUSER<>Target System ? 

    Is it contradictory with the tool philosophy to work like this ? To be honest, the added value of the UCI layer is especially doubtful to me. 

    Many thanks for you help / advice. 
     
    Michel 

Children
No Data