Hybrid Solution for Integrated Trading

Integrated applications are complex solutions, whose complexity are determined by the economic processes they implement, the amount of data employed (millions of records grouped in hundreds of tables, databases, hundreds of GB) and the number of users. Service oriented architecture (SOA), is now the most talked-about integration solution in mainstream journals, addressing both simple applications, for a department but also at enterprise level. SOA can refer to software architecture or to a way of standardizing the technical architecture of an enterprise and it shows its value when operating in several distinct and heterogeneous environments.System Integration, Data Integration, Web Services, Java, XML, Stock Market

Ontology-based patterns for the integration of business processes and enterprise application architectures

Increasingly, enterprises are using Service-Oriented Architecture (SOA) as an approach to Enterprise Application Integration (EAI). SOA has the potential to bridge the gap between business and technology and to improve the reuse of existing applications and the interoperability with new ones. In addition to service architecture descriptions, architecture abstractions like patterns and styles capture design knowledge and allow the reuse of successfully applied designs, thus improving the quality of software. Knowledge gained from integration projects can be captured to build a repository of semantically enriched, experience-based solutions. Business patterns identify the interaction and structure between users, business processes, and data. Specific integration and composition patterns at a more technical level address enterprise application integration and capture reliable architecture solutions. We use an ontology-based approach to capture architecture and process patterns. Ontology techniques for pattern definition, extension and composition are developed and their applicability in business process-driven application integration is demonstrated

New Developments in Practice II: Enterprise Application Integration

The term enterprise application integration (EAI) refers to the plans, methods, and tools aimed at modernizing, consolidating, integrating and coordinating the computer applications within an enterprise. The need to integrate across applications is being driven by customer demand for access to information and the desire of the business for a single point of contact with their customer base. The challenges are significant because of the variety of technologies in need of integration and because integration cuts across lines of business. This paper distinguishes among four different (but related) targets of EAI: Data-level integration Application-level integration Process-level integration Inter-organizational-level integration The paper then discusses the technologies that assist with this integration (the EAI toolkit ) under the following categories: Asynchronous Event/Message Transport Transformation Engines Integration Brokers Business Process Management Frameworks The paper concludes by outlining six key strategies for managing EAI suggested by a group of senior IT managers from leading-edge firms

SLA-Oriented Resource Provisioning for Cloud Computing: Challenges, Architecture, and Solutions

Cloud computing systems promise to offer subscription-oriented, enterprise-quality computing services to users worldwide. With the increased demand for delivering services to a large number of users, they need to offer differentiated services to users and meet their quality expectations. Existing resource management systems in data centers are yet to support Service Level Agreement (SLA)-oriented resource allocation, and thus need to be enhanced to realize cloud computing and utility computing. In addition, no work has been done to collectively incorporate customer-driven service management, computational risk management, and autonomic resource management into a market-based resource management system to target the rapidly changing enterprise requirements of Cloud computing. This paper presents vision, challenges, and architectural elements of SLA-oriented resource management. The proposed architecture supports integration of marketbased provisioning policies and virtualisation technologies for flexible allocation of resources to applications. The performance results obtained from our working prototype system shows the feasibility and effectiveness of SLA-based resource provisioning in Clouds.Comment: 10 pages, 7 figures, Conference Keynote Paper: 2011 IEEE International Conference on Cloud and Service Computing (CSC 2011, IEEE Press, USA), Hong Kong, China, December 12-14, 201

IDL-XML based information sharing model for enterprise integration

CJM is a mechanized approach to problem solving in an enterprise. Its basis is intercommunication between information systems, in order to provide faster and more effective decision making process. These results help minimize human error, improve overall productivity and guarantee customer satisfaction. Most enterprises or corporations started implementing integration by adopting automated solutions in a particular process, department, or area, in isolation from the rest of the physical or intelligent process resulting in the incapability for systems and equipment to share information with each other and with other computer systems. The goal in a manufacturing environment is to have a set of systems that will interact seamlessly with each other within a heterogeneous object framework overcoming the many barriers (language, platforms, and even physical location) that do not grant information sharing. This study identifies the data needs of several information systems of a corporation and proposes a conceptual model to improve the information sharing process and thus Computer Integrated Manufacturing. The architecture proposed in this work provides a methodology for data storage, data retrieval, and data processing in order to provide integration at the enterprise level. There are four layers of interaction in the proposed IXA architecture. The name TXA (DDL - XML Architecture for Enterprise Integration) is derived from the standards and technologies used to define the layers and corresponding functions of each layer. The first layer addresses the systems and applications responsible for data manipulation. The second layer provides the interface definitions to facilitate the interaction between the applications on the first layer. The third layer is where data would be structured using XML to be stored and the fourth layer is a central repository and its database management system

Legacy System Integration using a Grammar-Based Transformation System

Enterprise information system management is the operation of different corporate databases, applications, and more and more often of integration and interoperability of legacy systems, acquired through mergers and acquisitions. These legacy systems produce structured or semi-structured data that add to the vast amounts of data a company generates every day. This data needs to be communicated between heterogeneous systems within the same company and eventually beyond the company’s walls. Transformations of communicated data are required to enable companies to tightly integrate their systems into a cohesive infrastructure without changing their applications and systems. This article presents a transformation system that uses a grammar-based approach to provide direct integration of applications and systems at the data level. Sequences of transformations allow flexible and effective exchange of data between heterogeneous systems resulting in a single information network

Evaluating the integration of supply chain information systems: A case study

Supply chain management (SCM) is the integrated management of business links, information flows and people. It is with this frame of reference that information systems integration from both intra- and inter-organisational levels becomes significant. Enterprise application integration (EAI) has emerged as software technologies to address the issue of integrating the portfolio of SCM components both within organisations and through cross-enterprises. EAI is based on a diversity of integration technologies (e.g. message brokers, ebXML) that differ in the type and level of integration they offer. However, none of these technologies claim to be a panacea to overcoming all integration problems but rather, need to be pieced together to support the linking of diverse applications that often exist within supply chains. In exploring the evaluation of supply chain integration, the authors propose a framework for evaluating the portfolio of integration technologies that are used to unify inter-organisational and intra-organisational information systems. The authors define and classify the permutations of information systems available according to their characteristics and integration requirements. These, classifications of system types are then adopted as part of the evaluation framework and empirically tested within a case study

Exploring knowledge management integration through EAI in local government domain

Information Technology (IT) infrastructure integration and knowledge management share communal objectives e.g. to make organisations more effective and efficient, agile and innovative, and more responsive to market changes. Such association when assimilates bona fide knowledge management philosophy, it offers the IT departments a headship opportunity for organisational transformation in affiliation with the rest of the establishment. Notwithstanding, in the context of Local Government Authorities (LGAs), the non-integrated nature of the IT infrastructure is associated with inefficient data and knowledge exchange and reduction in LGA services’ quality. Therefore, numerous data inconsistencies and redundancies occur that impact LGA services to their citizenry. LGAs have deployed Enterprise Application Integration (EAI) technological solutions to integrate their legacy with new developed Information Systems (IS). Literature indicates that EAI achieves integration at five layers namely: (a) connectivity, (b) transportation, (c) transformation, (d) process integration and (e) knowledge integration. This research adapts a Revised Model for Integration Layers (REAL) and tests through a case study in a local authority. The results indicate that cases leading to data inconsistencies and replication can be prevented by integrating knowledge through EAI