GIN ECSB. Enterprise Content Service Bus

Transcription

1 GIN ECSB Enterprise Content Service Bus

2 GIN ECSB Enterprise Content Service Bus 2 Table of contents Enterprise Content Service Bus Challenges Big Data Data diversity and dynamic Conventional data integration Solution Modular architecture for the best overall solution Simple data integration based on a modular principle From data to information by semantic analysis Cross-linking of content Semantic Information Retrieval (SIR) Uniform Information Model (UIM) Master Information Model (MIM) Benefit Flexible business objects Process-orientated support Stable services Data migration and system consolidation Data cleansing

3 GIN ECSB Enterprise Content Service Bus 3 Enterprise Content Service Bus The GIN Enterprise Content Service Bus (ECSB) delivers flexible and dynamic business objects exactly as they are required by the processes and applications in your company. It decouples the data from their sources so that it can be newly combined and reused in many ways. This results in a consistent, central and stable view of the data, making the presence of a multitude of data sources is no longer an important challenge.

4 GIN ECSB Enterprise Content Service Bus 4 Challenges Paradox: Companies have more and more data, but less valuable information can be gained Big Data Lack of overview and insight The amount of data in companies is continuously growing. The amount of generated data has reached levels that can no longer be evaluated or used through conventional methods: most of the information is hidden within document texts, and the information available on the internet increases even faster. This leads to a paradox: Companies have more data, but gain less valuable information and insights. Data diversity and dynamic Maintenance of interfaces and services The amount of data is growing fast as is its diversity. In addition to data and documents from old and new applications, the importance of data and documents in the Cloud and the internet is rising. High demand for mobility and flexibility has accelerated this development.. Mergers and partnerships additionally require a high level of system integration for the exchange of information. As data constantly changes, and fast-moving markets and software systems with short life cycles of under a year grow as a response to market demands, companies have to react quickly and flexibly. The colossal number of interfaces and services used to deliver these high dynamics lead to vast data integration and data maintenance efforts. This adds new challenges in enterprise administration, and comes with a high price tag attached with managing the multitude of existing systems.

5 GIN ECSB Enterprise Content Service Bus 5 The Linked Open Data Project alone had more than 31 trillion facts by the middle of 2012 and is still growing exponentially. Conventional data integration limits Elaborate connection (mapping) with data sources Conventional solutions for the integration of large quantities of diverse data involve a mapping between a Master Data Model and the data models of the source systems. As the number of source systems grows, the effort required for cross-source data mapping increases disproportionately, especially when the different source systems have to exchange data. Mapping complexity rises exponentially. Finally, the mapping fails to display data relations from key-based relational databases (primary and foreign key relations). In particular, crossover relations and textual relations may not be detected. Furthermore, unstructured information such as documents remain completely ignored and conventional approaches often apply solely to databases. Conflicts between Master Data Model and real data A Master Data Model may display business objects correctly from a technical perspective, but could differ enormously from the real data. Missing information details or data model differences between source systems may make direct mapping impossible. This situation arises, unfortunately, more often than not. This results in a large gap between theory and practice when it comes to required and available data. Susceptibility due to change of real data A great deal of effort is required to create the Master Data Model. Worse, as soon as the MDM is created, it is already outdated, as the data sources or processes and applications that require business objects have already changed. This is a dual challenge: changes need to be detected and then the corresponding mapping needs to be identified and adapted.

6 GIN ECSB Enterprise Content Service Bus 6 Solution Modular architecture for the best overall solution GIN ECSB consists of multiple sequential modules that are optimally harmonized for each other GIN ECSB consists of multiple sequential modules that are optimally harmonized for each other. It does not only ensure a powerful overall solution, but also allows an efficient and flexible integration into company systems and requirements through open, clearly defined interfaces. GIN Server lies at the heart of the solution, providing a semantic middleware for highly efficient data integration and a fully-automated data analysis. Modules of GIN ECSB including GIN Server sub-structure

7 GIN ECSB Enterprise Content Service Bus 7 Simple data integration based on a modular principle The approach leads to a robust integration with minimal maintenance No data modeling Data model derivation via a bottom-up approach Compared to other semantic technologies, it is not necessary to define rules, ontologies or training methods using reference data. GIN ECSB does not have data modeling as a prerequisite, allowing highly efficient data integration. Using a modular principle, data sources are connected to the GIN Server via Content Connectors, and integrated content is recorded as raw data. The sole task of the connectors is to synchronize source data with GIN Server in a coherent manner. The data is then indexed and textually evaluated. In conventional solutions for integration, a data model is defined at the beginning and then connected via a top-down approach. In GIN ECSB, the data is first read, and then a data model is created via a bottom-up approach. This simplifies data source integration, ensures that all data is read, and that changes to the source data are immediately taken into account. This approach leads to stable integration with minimal maintenance. From data to information by semantic analysis Fully automated processes GIN Server evaluates the content of all data from integrated sources. Compared to other semantic technologies, it is not necessary to define rules, ontologies or training methods using reference data. The analysis immediately starts after the integration of the sources and the synchronization of the data, and involves a combination of light-weight processes based on computer linguistics, text mining, generic rules and machine learning. These components guarantee high speed as well as accurate analyses. Harmonization of data models Normally, data in several sources is classified and described differently, even though it sometimes has the same meaning. One example is contacts within ERP and CRM systems. The semantic analysis used for data model harmonization recognizes which data has different classification designations and different descriptions, yet identical meaning. The data with the same meaning are translated into a common data model. If a user later requires contact information, GIN ECSB knows for example that this information is available in both the ERP and the CRM system.

8 GIN ECSB Enterprise Content Service Bus 8 Cross-linking of content Connections between data create meaning: Isolated contact information is only significant when, for example, it is associated to related orders or invoices. Therefore, GIN Server s semantic analysis detects which connections exist between content, why they exist, and how closely they relate to each other. GIN Server changes data objects into content objects, which in turn are textual units, such as contacts. This provides meaning to content, giving it significance and differentiating it from a mere technical data object. The semantic analysis makes all textual connections transparent without the need to define them in advance Relationships between data objects are precisely determined through conventional technologies such as relational databases. Often, such technologies completely disregard other important relations. In distributed data sources, these relations are completely lost. The semantic analysis makes all textual connections transparent without the need to define them in advance. This creates new knowledge and turns isolated data into information. Extensions of the basic components for GIN Enterprise Content Service Bus

9 GIN ECSB Enterprise Content Service Bus 9 A basic component of GIN ECSB allows central access to data of all integrated sources, regardless of whether it is structured data from databases or unstructured data from documents. Semantic Information Retrieval (SIR) Central access to all data of heterogeneous sources A basic component of GIN ECSB allows central access to data of all integrated sources, regardless of whether it is structured data from databases or unstructured data from documents. This can be done semantically (e.g. querying data by its meaning without having to know the source systems, data model or data format). Thus, contacts for example can be called only by its semantic classification (content type) and its attributes, such as an address of the contact. Reasoning of dynamic connections All textual connections resulting from the semantic analysis can be specifically used to query content objects. Reasoning is derived from connections, for example when premium customers are queried to determine which customers bought specific products under a signed service contract. Potential customers are identified by their interest in certain products through their correspondence. In this process, the reasons for connections within data, as well as the weight of each connection, are evaluated. For example, the connection between a contact and an may be more important than the connection between a contact and a text where this contact is mentioned. Uniform Information Model (UIM) Generic harmonized data model From the analyzed integrated source content, GIN Server derives a generic and harmonized data model the Uniform Information Model (UIM) which forms a basic component of GIN ECSB. If the data model changes in one of the source systems, or another source system is connected, the derived data model will change as well. The latter informs which content is available in GIN Server, how it is described and how it is connected. For example, the UIM describes which information exists about customers, orders, deliveries and invoices and how customers are defined by their name and address. Furthermore, the UIM lets you know that customers are connected to orders by their customer number, and deliveries are connected by order numbers. If you wish to connect another data source which also administers customers, these will be classified as customers during the harmonization as well. Equivalent description elements receive the same name.

10 GIN ECSB Enterprise Content Service Bus 10 Applications (client systems) and services (data consumers) can use completely generic content and process it exclusively according to its meaning without taking into consideration its source systems. Uniform data model Due to the UIM, content objects always have the same data format no matter whether the content comes from one database, represents a document, or originates from the internet. GIN ECSB takes a simple approach to providing content integrated via GIN Server. Applications (client systems) and services (data consumers) can use completely generic content and process it exclusively according to its meaning without taking into consideration its source system. Master Information Model (MIM) Stable services for your business objects GIN ECSB is a GIN Server extension enabling it with a Master Information Model (MIM). It contains a description of your business objects exactly as you need them for your processes and applications. GIN ECSB obtains specific business objects for your MIM from the available data sources. Thereby, a business object can be a combination of content objects created by different content types or different sources, making it more reliable. Processes and applications remain flexible and stable even when source systems are replaced or consolidated. Reading and writing for your productivity The reverse is also possible: Applications can dynamically retrieve data from various sources and modify or even create them. GIN ECSB then is responsible for translating business objects into data for one or several source systems, and to save them in the respective systems. At the same time, business objects are saved into revision history. Intelligent modeling with implicit mapping You can define your business objects with an intuitive graphical user interface, the Intelligent Information Modeler (IIM). Content types and attributes in the Uniform Information Model (UIM) serve as components, which can be constructed into business objects in a graphical drag-and-drop user interface. The corresponding mapping between data and the integrated sources takes place done implicitly. An implicit mapping requireing knowledge of each source system s interface is no longer necessary. As soon as a business object is defined in this way, it can be used by GIN ECSB service. Even when source systems change, the implicit mapping remains stable because it determines the business objects with the help of the UIM. It has never been easier to instantly provide processes and applications with required information.

11 GIN ECSB Enterprise Content Service Bus 11 Intelligent control of modifications The UIM changes when data models are modified. Changes occur when data sources are added, modified, disconnected or deleted. The Intelligent Model Monitor (IMM) controls all modifications and checks if the Master Information Model (MIM) is affected. The model owner is actively informed if a conflict occurs because attributes or content types for business objects are missing or deleted. If a conflict such as this occurs, the IMM informs the responsible person for the affected business object, who can then make the required adjustments in the MIM. Simulations for safeguarding the operation The consolidation of source systems can now be planned and gradually implemented without threatening running operations. IMM can also be used to simulateand verify how the consolidation, the modification or deletion of a source system affects the Master Information Model (MIM). Thus, conflicts can be identified in advance and failures avoided. The consolidation of source systems can now be planned and gradually implemented without jeopardizingrunning operations. Administration and versioning for the documentation The Master Information Model (MIM) is not only created, but also administered with the Intelligent Information Modeler (IIM). In order to record modifications and extensions, it allows versioning of MIM models. In this way, modifications remain traceable and auditable. The MIM is stored in a future-proof open standard which allows the combined use of other software products from other producers.

12 GIN ECSB Enterprise Content Service Bus 12 Benefit Flexible business objects The GIN ECSB allows business objects to be delivered exactly as needed for the application Often, data objects from the sources do not correspond to business objects which are required in a process or application. More often than not, business objects require more details or are classified more precisely. Thus, an application can distinguish between prospective customers, regular customers and premium customers, even when the database only manages contacts. Sometimes a business object is comprised of multiple data objects. For example, a contract number required for a customer may be saved in a document. GIN ECSB allows business objects to be delivered exactly as needed for the application. Modification or adaption of technical requirements is possible at any time. Comparison of relations in databases and in GIN Server Conventional data mapping Datafield Data Key Na Muster * AD Tel Musterhausen Datafield Data Key Name Muster * Adrress Musterhausen Tel 8675 Datafield Data Key Kunde Muster * Adrress Phone Musterhausen Semantic data mapping Datafield Data Key Na Muster * AD Tel Musterhausen Datafield Data Key Name Muster * Adrress Musterhausen Tel 8675 Datafield Data Key Kunde Muster * Adress Phone Musterhausen

13 GIN ECSB Enterprise Content Service Bus 13 Process-orientated support Flexible and dynamic business objects can be integrated in processes without the consideration of various data models and data sources Flexible and dynamic business objects can be integrated in processes without the consideration of various data models and data sources. GIN ECSB even allows the modification and creation of business objects that are later be stored back into the original data source, or in a newly created one. Thus, GIN ECSB offers an optimal basis for process execution. Stable services The GIN ECSB is extremely reliable. When data source models are changed, replaced, or added, GIN ECSB recognizes these modifications and secures a stable and highly-available service. This allows processes and applications to run in a critical, stable environment and contribute to your business success. Data migration and system consolidation GIN ECSB supports IT systems interface removal and consolidation. It can also perform simulations to identify the impact of system removal. If a system is replaced by a new one, GIN ECSB automatically ensures that business objects are harmonized, allowing downstream processes and applications to continue operations in a stable condition. The GIN ECSB helps to create a solid base of data for all business-critical systems and existing processes in the company. Data cleansing The GIN ECSB helps to create a solid base of data for all business-critical systems and existing processes in the company. System updates or introduction of new software are easier and faster to implement due to reasonable data quality. User acceptance depends on data quality.

14 GIN ECSB Enterprise Content Service Bus 14 The following key functions are available: Access to a variety of systems Analysis of information with automatic derivation of the data model Automatic classification and tagging of documents Standardization of data formats Automatic classification and tagging of documents Standardization of data formats Harmonized classification and description of data With GIN ECSB, you can evaluate and improve data quality. GIN ECSB identifies which data is held redundantly in various systems, and whether conflicts resulting from incorrect and outdated data exist. For example, contacts in an ERP system can be more up-to-date or better managed than in a sales department s CRM system, causing them to miss their targets. This knowledge can be used to consolidate the two systems, compare them, or synchronize them. Using smart modeling with the Master Information Model (MIM), you can locate where the missing data that is critical to your business processes is. Long-term cost-savings: Advantages due to fast changeable business processes and shorter time-to-market. More value through better processes with higher quality. Lower project costs when implementing new requirements. Cost-effective project management through better understanding and transparency of IT systems, services and dependencies. Decoupling business objects from systems ensures an extension and exchangeability of services without any problems. Reduced administration and maintenance costs, as the side effects triggered by data modifications are manageable. Higher future-proofing and cost-saving for future process integration and new software integration as a result of consequent decoupling of business objects. This helps ensure independence from changing technologies. Easier and more cost-effective integration of new organizational units (acquisitions and fusions) Easier outsourcing of sub-processes.

15 Contact iqser GmbH Schloßweg 4 D Walldorf Germany Phone Fax info@iqser.com Web