En Enterprise Service Bus (ESB) är en programvara för att binda ihop flera olika system,där man vill säkerställa att kommunikationen mellan systemen sker utan förluster av data.Detta för att minimera konsekvenserna av störningar i trafiken.Målet med det här examensarbetet är att se om det går att skapa en specialskriven ESB åtNetgain, som ser till att deras två system, det ena ett beställningsformulär på en webbsidaoch det andra en processmotor som behandlar beställningarna, kan kommunicera utan attdata försvinner vid överföringen. Detta för att få till en stabilare överföring mot vad dehar idag.Fokus för arbetet har därför varit att skriva ett system som är och känns stabilt för bådeanvändare och administratör. Önskemål fanns också att skriva en administratörsvy för attstyra systemet och att projektet skrivs i JavaScript. Hänsyn togs också till hur de tvåsystemen ser ut, då dessa inköpta system inte går att modifiera. Vi fick istället förlita osspå deras inbyggda api:er. / An Enterprise Service Bus (ESB) is a software for bridging multiple systems, where you want to ensure that communication between systems occurs without data loss. This is tominimize the consequences of traffic interference.The aim of this bachelor dissertation is to see if it is possible to create a ESB for Netgain,which ensures that their two systems, one, a web based order form, the other a processingengine, that processes the orders, can communicate without data disappearing at transfer.This to ensure a more stable transfer than what they have today. The focus of the work has therefore been to write a system that is and feels stable for bothusers and administrators. Desired was also to write an administrator view to control thesystem and to write the project in JavaScript. Consideration was also given to how thetwo systems look, as these purchased systems can not be modified, we had to rely on theirbuilt-in api:s.

The goal of this work is to allow JBoss ESB to communicate with remote applications using REST. JBoss ESB is a platform that separates application logic from the process functions and enables communication between applications with different interfaces by sending messages. REST is an architecture that provides universal interface for communication between computer systems in the network. This work describes integration of REST communication architecture with JBoss ESB platform. The integration is divided into two parts. The input part accepts REST requests, propagates their content to the JBoss ESB and generates a response. The output part waits for the messages from JBoss ESB from which it creates the REST requests, sends them to the recipients and receives responses. The implementation puts emphasis on integration with the RESTEasy project. RESTEasy provides a framework that facilitates development of applications that support REST communication.

This bachelor thesis looks into the use Enterprise Service Bus(ESB) as the central hub in system integration, which is currently the newest standard for large-scale system integration. The thesis is focused on issues with ESB integration and solutions to these problems, as the positive aspects have already been covered in other reports. There is not much available information about the issues that can occur when using a ESB architecture and how to resolve thes issues. The contribution of this thesis is gathering known issues from both academic papers and from the industry and providing solutions to these issues. Also, we present a set of guidelines for developers that are new to ESB. These guidelines was formed by answers from a questionnaire that is in turn formed by a literature review, designed to nd issues with ESB integration. The solutions we found can be used by new ESB developers to avoid common mistakes and also might also assist by providing a solution in case an issue already har occurred.

System integration is a challenging task for large organizations since they must manage complex IT infrastructures, and utilize hundreds of applications that cause a myriad of complications as a result of rapidly evolving systems and technologies. Over time customer requirements and the automation of internal business functions forced the gigantic service providers to develop and buy applications for different purposes. Not many years before, the applications in an organization were usually separated silos, specifically designed to answer a particular problem. However, this way of working was not efficient. It is not impossible to design one application that runs the total business, however, in reality it can't respond to all the needs inside an organization. In most cases the applications need to interact with each other and to reuse functionalities or data. At this point the concept of integrating systems first came to existence.The progress in computer science and information technology has also affected the way that integration between applications was developed and designed over the years. This shows that there's always some new method that should be studied and investigated. In recent years, the Enterprise Service Bus has come to the market and there are many vendors in the market claiming that they have produced the exact solution needed for requirements of organizations.In this work, the attempt was to construct an understanding of the Enterprise Application Integration practices and methods which have been utilized over the years. Mixed methods research a combination of interviews and questionnaire, and Design Science Research methods were used to generate empirical results. While the first two methods was used to supply the input for challenges of system integration, the DSR build and evaluate method was employed to test the ESB product. The criteria for the test were developed mostly as the outcome of interviews and the questionnaire as the main challenge. The aim was to verify efficiency and effectiveness of the selected and proposed ESB under special designed DSR build and evaluate phases.As a result of both theoretical and empirical studies in combination with selection of different methods in Information System research, the work presents a knowledge foundation for organizations with the aim to make a change in their current system integration practices and patterns utilizing approaches facilitated by ESB products.

The thesis deals with enterprise service bus (ESB). In theoretical part there are described ESB and other technologies relevant to this topic. Next there are described advantages and disadvantages of the deployment and mapped current market of ESB solutions. Last chap-ter briefly discusses other technologies recovered for the practical part. The second part deals with the design and implementation ESB using framework SwitchYard. I describe the systems to be integrated, further progress in the development such as preparation envi-ronment, server configuration and description of the most important parts of the developed system. The last chapter deals with the practical part of the evaluation framework. It in-cludes the description of the errors that I have encountered in the development and verbal evaluation on the basis of general ESB functionality described in the theoretical part.

<p>Validerat; 20101217 (root)</p>

Les collaborations inter-organisationnelles relèvent généralement de circonstances opportunistes et s’avèrent par conséquent éphémères. Les organisations doivent alors être disposées à s’intégrer dans ce type de collaboration tout en gardant leur identité propre. Ce constat est le point de départ du projet MISE (Mediation Information System Engineering), qui aborde cette notion de collaboration d’organisations selon l’angle du système d’information, en proposant une démarche de conception d’un SIM (système d’information de médiation). Ce SIM constitue un système tiers, médiateur des SI des diverses organisations, destiné à prendre en charge, d’une part la coordination des actions des partenaires (orchestration de la dynamique collective) et d’autre part, de gérer la circulation de l’information au sein de la collaboration (acheminement et traduction des données). La conception du SIM repose sur une démarche d’ingénierie dirigée par les modèles (IDM). Par ailleurs, la notion de crise, reposant par définition sur la sollicitation d’acteurs hétérogènes concernés par une collaboration opportuniste (qui plus est dans le cadre d’un phénomène évolutif d’une durée indéterminée), fait du domaine de la gestion de crise un parfait cas d’étude pour le projet MISE. Ces travaux de thèse, liés au projet ANR-CSOSG ISyCri, présentent cette démarche de conception du SIM appliqué au domaine de la gestion de crise. Le manuscrit parcourt la démarche MISE appliquée au domaine de la gestion de crise depuis la définition conceptuelle jusqu’à la réalisation technique selon les trois étapes de cette démarche IDM : (i) au niveau « métier » : l’utilisation d’une base de connaissance, représentée par une ontologie, permet, à partir des caractéristiques de la situation de crise et du savoir-faire des partenaires de la collaboration, de définir le processus collaboratif représentatif de la succession des activités à exécuter dans le cadre de la réponse à la crise. (ii) au niveau « logique » : une transformation de modèle permet de construire, à partir du modèle de processus collaboratif obtenu au niveau « métier », une architecture logique du SIM (orientée service, selon les préceptes SOA). (iii) au niveau « technique » : une deuxième transformation de modèles permet de générer les éléments nécessaires à la configuration du SIM, notamment le fichier BPEL. L’agilité du SIM ainsi déployé constitue une exigence incontournable. Les travaux présentés dans ce manuscrit proposent donc d’intégrer ces différentes étapes de conception du SIM sous la forme de composants logiciels indépendants, sollicités à loisir au sein d’une architecture orientée service. Cette solution apporte une grande flexibilité structurelle à la démarche, en autorisant la reconfiguration partielle du SIM à partir du niveau adapté à la situation. / Organizations should be able to take part into opportunistic and brief collaborative networks. However, they should also control their identity. The MISE project (Mediation Information System Engineering) aims at dealing with that issue from the information system point of view. The main principle is to design a specific third part mediation information system (MIS) in charge of, first, orchestrating the collaborative workflow of the collaborative network and, second, managing information (carrying and translating data). Designing such a MIS is based on a model-driven engineering approach (MDE). Considering crisis management field, it is obvious that such a domain requires opportunistic collaboration of heterogeneous partners involved in the crisis response (furthermore, crisis management is a very dynamic process where agility is a crucial point). Directly linked to the French funded ISyCri project, this PhD research work presents the overall approach for MIS design in a crisis management context.That MDE approach is based on three steps: (i) “Business” level: a collaborative process model is deduced from a knowledge base represented through an ontology. (ii) “Logical” level: an abstract service-oriented architecture of MIS is built, based on a model transformation from the previously obtained collaborative process model. (iii) “Technical” level: all the required deployment files are generated (including BPEL file), based on another model transformation, from the logical architecture. Besides, agility is a strong requirement for such a MIS. Therefore, these three steps are integrated, as independent software components, in a service-oriented architecture of a MIS-design tool. This solution brings structural flexibility to the overall approach by allowing partial redesign of the MIS (at theexpected step)

<p>För att dagens system och deras allt mer komplexa applikationer ska kunna integreras med</p><p>varandra krävs det att de kommunicerar via tjänster. Denna tjänsteorienterade integration</p><p>uppnås genom att man använder sig av Service Oriented Architecture (SOA) som bygger på</p><p>löst kopplade tjänster som kommunicerar med varandra på ett standardiserat sätt. En viktig</p><p>del i en integrationslösning är Enterprise Service Bus (ESB). I denna rapport kommer vi</p><p>förklara grunderna i tjänsteorienterad integration och sedan fördjupa oss i ESB. Då ESB är ett</p><p>luddigt begrepp ska vi på ett enkelt och lättbegripligt sätt ge vår syn på begreppet, samt dess</p><p>fördelar och nackdelar. Vi kommer även att ge marknadens syn på ESB genom en</p><p>enkätundersökning som innefattar både leverantörer, konsulter och kunder.</p> / <p>If today’s software systems and their complex applications shall be able to integrate with each</p><p>other, they have to communicate through services. This service oriented integration can be</p><p>accomplished by using Service Oriented Architecture (SOA) where all components are</p><p>loosely coupled and communicate in a standardized way. An important part when building an</p><p>integrated solution is the Enterprise Service Bus (ESB). In this report we will explain the</p><p>basics of SOA and take a more detailed look at the world of ESB. The concept of ESB is not</p><p>well defined and hence means different things to different people. We are going to present an</p><p>interpretation of the ESB and its benefits and disadvantages. To find out what the market</p><p>thinks about ESB we have been talking to producers, consultants and customers.</p>

<p>This thesis emphasizes on investigating the relationship between the quality attributes and service oriented architecture (SOA). Due to quality attributes requirements drive the design of software architecture, it is necessary to maintain the positive quality of SOA and improve the negative quality of SOA. This thesis gives an introduction to SOA, Enterprise Service Bus (ESB) and MULE. Then, it covers information on quality of systems and tactics for achieving each quality attribute. Finally, we discuss the quality of SOA in detail, and illustrate how to set up a SOA and how to improve its quality using a case of an order for supermarket.</p> / Order of supermarket

Virtual Organizations (VO)—a network of independent organizations collaborating to address specific business opportunities—have become popular in today’s technology driven business environment. Due to their autonomous and interdependent nature, management of collaboration among such organizations is a challenging task. Although many solutions have been proposed over the past two decades to support inter-organizational interactions, VOs still face several challenges due to their dynamic and temporal nature that cannot be addressed by traditional solutions such as ebXML, RosettaNet and EDI. In this research, we present a framework for process management in service oriented virtual organizations and a distributed architecture for a flexible infrastructure that supports collaborative business process execution, monitoring and management. The framework contains 6 layers with multiple components within each layer. In designing the components of the framework, standard reference architecture such as the Open-EDI reference model and the S3 service oriented architecture, as well as best practices such as ITIL V3 and PMBOK are used. The infrastructure supports the common topologies of inter-organizational collaboration (e.g. peer-to-peer, star, linear), and responds well to changes due to its loosely coupled components. The proposed infrastructure is based on federating multiple SOA infrastructures with the Enterprise Service Bus (ESB) as its core. It is implemented using IBM WebSphere ™ products. We demonstrate that VOs built with our framework and implementation architecture facilitate flexibility, rapid process integration and dynamic evolution.