enterprise information integration
DESCRIPTION
This about Enterprise Information Integration, A tool for analysisTRANSCRIPT
Enterprise Information Integration
By
Sharbani Bhattacharya
03 October 2008
Enterprise Information Integration
• Enterprise Information Integration or EII, is a process of information integration, using data abstraction to provide a single interface (known as uniform data access) for viewing all the data within an organization, and a single set of structures and naming conventions (known as uniform information representation) to represent this data; the goal of EII is to get a large set of heterogeneous data sources to appear to a user or system as a single, homogeneous data source.
EII Challenges
Data within an enterprise can be stored in various formats, including
• Relational Databases (which themselves come in a large number of varieties),
• Text files, • XML files, • Spreadsheets and a variety of proprietary storage
methods, each with their own indexing and data access methods.
Data Access Technologies
• ADO.NET
• JDBC
• ODBC
• OLE DB
• XQuery
• Service Data Objects (SDO) for Java, C++ and .Net clients and any type of data source
EII Architecture
EII Characteristics
• Support for a variety of data sources, including relational database management systems (DBMSs), non-relational DBMSs, files, XML documents, and others
• SQL-based API • Ability to join, union, aggregate, and otherwise correlate
data from multiple sources in a single query • Ability to create individual views or virtual data objects
based on data integrated from multiple sources • Location transparency • Automatic data type conversion services • Real-time programming model
Data Integration vs. Information Integration
• Some of the emerging EII tools will handle both structured and unstructured information.
• Provide metadata management solutions in more open repositories.
• EII is fast becoming the part of the infrastructure that manages the information across the enterprise.
Information Integration Solutions
• Creating a single view of a customer or other business entity • Enterprise data inventory and management • Real-time reporting and analysis, and creating management
dashboards • Updating a data warehouse • Creating a virtual data warehouse • Updating common information across information sources • Creating portal applications containing both structured and
unstructured data from disparate systems • Integrating unstructured data, including documents, audio, video
and other electronic media, into applications. • Providing an infrastructure for enterprise information management,
including all forms of digital me
EII
• The workhorse of data integration has been ETL tools. They were created to extract the information, transform it into a consolidated view, and then load it into a data warehouse in a batch mode
Best Practices for Information Integration
• Conduct design reviews
• Create an enterprise metadata repository
• Manage metadata at an enterprise level
• Move toward semantically rich metadata
EII And Applications
• EII for Banking
• EII for Capital Markets
• EII for Life Sciences
• EII for Corporate Performance Dashboards
• EII for Business Intelligence and Reporting
• EII for Single Customer View
Commercial Implementations
• WebSphere Studio Application Developer
• WebSphere Information Integrator
WebSphere Information Integrator
federated database architecture
The SDO and EII architecture Enables
• Reach a wider variety of data sources immediately with SDO applications, including mainframe data sources, industry-specific data sources, and data managed by popular third party application packages, such as SAP, PeopleSoft, and Siebel
• Reduce design, development, and maintenance complexity by employing fewer data mediator services and fewer data source connections
• Shorten development cycles and promote rapid release schedules • Minimize performance tuning of data access tasks. WebSphere Information Integrator
automatically analyzes the costs of various possible data access strategies and selects an efficient one for execution.
• Automatically adjust execution strategy to accomodate changes in underlying database schemas, such as the addition of new indexes.
• Eliminate the need for calling applications to manually aggregate, summarize or convert data (WebSphere Information Integrator handles all of the above)
• Reduce network traffic and resource consumption. Greater amounts of data integration and filtering work can be performed by the WebSphere Information Integrator server and back-end data sources rather than within SDO applications.
• Support SOA, promote code reuse, enhance programming productivity, and contribute to a more flexible software environment with the virtual data access services layer
VOTE OF THANKS