wordpress-themes.org wordpress themes wordpress themes

Connected Government: An Exploration of the UAE’s Identity Management Integration Strategy: Integration Models, Services, Governance

Various integration models needed to be supported by the integration platform to meet possible business and functional requirements and to provide various options for external entities to connect through the four distinct models of integration that were developed for the implementation of the integration strategy. See Figure 7.

The enterprise integration needed to be supported by a series of business integration services that allow external entities to integrate with the national population register systems. The business services taxonomy was organized into several service groups to provide integration capabilities to the national population register. These services were mainly post-issuance services, i.e., services that could be provided after a national ID number and ID card were issued. Figure 8 below shows the various business integration services groups. 

To enable seamless, secure, and flexible integration within the internal environment and between the external entities, a standards-based and an SOA-based enterprise integration were seen as important to implement to enable the functionality of the integration platform. A reference architecture was developed as depicted in Figure 9 below. Each of the four reference architecture layers is described in Table 1.

The enterprise integration governance model was needed to ensure control over the life cycle of services exposed through the platform and consumed by the different stakeholders. Enterprise integration governance defines and enforces policies related to service contracts, data quality, data and information privacy protection, authorized access to services, non-repudiation, and logging. For the successful implementation and operation of enterprise integration, these governance principles needed to be adhered to. The diagram below illustrates the data and integration governance principles that needed to be defined and enforced to control access to the enterprise integration platform.

Figure 7

Figure 7. The four integration models

Figure 8

Figure 8. Business integration service groups

Figure 9

Figure 9. Integration platform architecture

Table 1. Reference architecture layers

Layer Description
Channels This layer is the presentation layer of the enterprise integration. It allows external entities to use the identity authority’s services through various
Business channels such as Web services, file transfer (FTP), and remote access.This layer provides the functionality for service modeling, service orchestration, SOA governance, transformation, and remote access
Services (needed for special security operations) where all services provided to
Platform government entities are defined and maintainedThis layer is the key enabler of SOA-based enterprise integration. It provides messaging capabilities, integration services (adapters, APIs, etc.),
Services monitoring and management services, and data services (ODSs, DWs, and
Applications & Data Stores DBs) to facilitate internal and external integration.This layer is not considered a part of the enterprise integration to be implemented. This layer contains applications and data stores that will be
integrated with each other via the enterprise integration, as well as
facilitating external entities’ integration for the purpose of accessing the population register.
This post was written by , posted on December 3, 2013 Tuesday at 11:11 am