| View500 - FAQ - Data Upload | |||
|
How do I get my user identity data into View500? View500 provides a number of ways for populating the Directory as follows: a) View500 has an integrated web based Directory User Agent (webDUA) that can be used as a Self Service portal to allow users to update their own user data. What gets updated can be controlled. Similarly what gets deleted or changed can also be controlled b) View500 can accept LDIF files (Lightweaght Directory Interface Files) allowing data produced from another Directory or Directory aware application to be loaded into View500 c) View500 fully support X.525 replication. This allows View500 to receive in real time data from another Directory server supporting X.525. As an example View500 has been deployed by a number of Defence Agencies and used in the coalition Border directory role providing linkage to both the US Defence and UK Ministry of Defence Directory servers with both these being from different suppliers but both using the X.525 replication protocol d) View500 has an Integrated synchronisation and integration tool called the Stream DUA (sDUA). This allows View500 to be linked up to external data sources with some data mapping and correlatisation providing object to object synchronisation. As an example for one Australian customer the sDUA has been used to provide a synchronisation and correlisation link with a Lotus Notes LDAP directory in Denver in the US and Notes LDAP Directories in Chile and Sweden e) For more complex integration and synchronisation tasks, eB2Bcom View500 partners with Radiant Logic utilising Radiant Logic's ICS server (Integration & Correlation). RadiantOne ICS simplifies managing the life cycle of a user's digital identity by providing identity synchronization. ICS builds a common identity and provides a global profile out of existing identity sources, providing metadirectory-type functionality with easy integration of disparate data sources and without the strain of costly data replication. Within ICS, data sources are mapped, data is virtualized into a common schema, and correlations between identity profiles are established. Identity data is aggregated into a central hub and synchronized across the enterprise according to customized business logic. So RadiantOne ICS provides two key services to an identity infrastructure: 1) Object Synchronization - supporting object replication ("directory to directory" or "database to database") as well as complex identity synchronization across heterogeneous systems. 2) Identity Correlation - correlate, link identities, and match them to application requirements Great, but can I also synchronise that data from my authoritative sources? IHow do I handle the situation where I have multiple identity sources but How do I handle changes in the Directory such as moving Non Leaf entries? Can I run a number of different schemas in the one directory server? | ||
|
|||