IDStar Processes



'Agents' attached to operational database and files systems are notified of  changes to the source data and forward these to the IDStar core services

  • Relational databases (DB2, Oracle, SQL Server) provide standard services to notify an application (the agent) when database field(s) are changed
  • IMS DB can use a 'data propagator' service to notify the agent of change
  • Other heritage database and file systems (IDMS, VSAM etc) need an application-level compare of current and previous versions of the data to detect changes and advise the agent

The agent is notified of the 'before' and 'after' form of the source data. Agents can use industry-standard middleware to notify changes to IDStar, which uses the 'before' version of the notified change to find the corresponding entry in its Source Data. It  re-parses the source to find the data entries in the index and searches the index to find other matches for this customer. Candidate matches can have a user-defined 'confidence level' or 'matching threshold' set, so that a specified level of commonality must be met before index entries are accepted as being for the same customer.

The index points back to other Source Data rows for the same customer. The IDStar generator creates XML format updates to send to the other operational systems, based on the specific data formats expected by those systems. The 'agent' application attached to the operational systems can either directly update the database or call the operational system application to perform the update.


[IDStar Technical Overview]
[IDStar Repository Architecture]
[IDStar Processing Updates]
[IDStar Additional Capabilities]
[IDStar Technical Environment]


Copyright © 2000-2005, IDentity Software Pty Ltd. Terms of use. Privacy policy.

Site design by Southern Cross Systems