DOCSLIB.ORG

Porovnání Výkonu Switchyard a Jiných OSS ESB Implementací

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Porovnání Výkonu Switchyard a Jiných OSS ESB Implementací MASARYKOVA UNIVERZITA FAKULTA INFORMATIKY Û¡¢£¤¥¦§¨ª«¬­Æ°±²³´µ·¸¹º»¼½¾¿Ý Porovnání výkonu SwitchYard a jiných OSS ESB implementací BAKALÁRSKA PRÁCA Pavol Bako Brno, 2013 Prehlásenie Prehlasujem, že táto bakalárska práca je mojím pôvodným autorským die- lom, ktoré som vypracoval samostatne. Všetky zdroje, pramene a literatúru, ktoré som pri vypracovaní používal alebo z nich ˇcerpal,v práci riadne citu- jem s uvedením úplného odkazu na príslušný zdroj. Pavol Bako Vedúci práce: Mgr. Marek Grác i Kl’úˇcovéslová SOA, ESB, SCA, servisne orientovaná architektúra, service oriented archi- tecture, enterprise service bus, integraˇcnýsystém, výkonnostné testovanie, podniková zbernica služieb ii Pod’akovanie Chcel by som sa pod’akovat’ pánovi JiˇrímuPechancovi, ktorý ma sprevá- dzal po celú dobu práce, a ktorý mal strpenia na moje otázky. Takisto by som sa chcel pod’akovat’, že mi umožnil po dobu niekol’ko mesiacov pra- covat’ na bakalárskej práci v priestoroch spoloˇcnostiRed Hat vo svojej do- stupnosti a umožnil mi tak efektívnejšie riešit’ problémy. iii Obsah 1 Úvod ................................... 1 2 Služobne orientovaná architektúra (SOA) ............. 3 2.1 Integraˇcnésystémy a SOA pravidlá . 3 2.1.1 Point-to-point model . 4 2.1.2 Hub-and-spoke model . 5 2.1.3 Bus model (ESB) . 6 2.1.4 SCA OASIS architektúra . 6 3 Podniková zbernica služieb (ESB) .................. 7 3.1 Charakteristika posielania správ . 7 3.2 Prehl’ad základných vlastností . 7 3.3 Hl’adanie definície ESB . 9 4 Metodika testovania .......................... 10 4.1 Scenáre testovania a prostredie testovania . 10 4.1.1 DirectProxy . 11 4.1.2 CBRProxy . 11 4.1.3 XSLTProxy . 13 4.2 ESB Performance framework . 13 4.2.1 Výkonnostné testovanie v ESB Performance . 13 4.2.2 ESB Performance framework . 14 4.3 Amazon AWS EC2 . 16 4.3.1 Parametre AMI . 16 4.3.2 Spúšt’anie testov - všeobecne . 17 5 SwitchYard - implementácia ..................... 18 5.1 Základné vlastnosti frameworku . 18 5.2 Postup pri implementácii . 20 5.2.1 Príprava nástrojov na implementáciu . 20 5.3 Implementácia scenárov . 21 5.3.1 DirectProxy . 21 5.3.1.1 DirectProxy bug a workaround . 22 5.3.2 CBRProxy . 22 5.3.2.1 CBRProxy bug a workaround . 22 5.3.3 CBRSOAPHeaderProxy . 23 5.3.4 CBRTransportHeaderProxy . 23 5.3.5 XSLTProxy . 23 5.4 Nasadenie do Amazon EC2 . 24 6 Testovanie ................................ 25 6.1 Mule ESB . 25 iv 6.1.1 Výsledky a chybové situácie . 26 6.2 SwitchYard v0.7 . 26 6.2.1 Výsledky a chybové situácie . 26 6.3 UltraESB v1.7.1-Vanilla . 27 6.4 WSO2 v4.6.0 . 28 6.4.1 Rozdiel v testovaní WSO2 v4.6.0 oproti ostatným ESB 29 7 Vyhodnotenie výsledkov ....................... 31 7.1 Vyhodnotenie na základe vel’kosti správy . 31 7.2 Vyhodnotenie na základe súbežného prístupu . 32 7.3 Vyhodnotenie z pohl’adu testových scenárov . 33 7.4 Výsledné porovnanie . 35 8 Záver ................................... 37 A Ostatné grafy výkonnostného testovania . 42 B Zát’až CPU na Amazon EC2 po dobu testu . 47 v 1 Úvod Heterogénnost’ súˇcasných informaˇcných technológií môžme považovat’ v dvoch perspektívach za pozitívne a negatívne. Za pozitívum môžeme považovat’ existenciu zdravej konkurencie medzi softvérovými spoloˇcnos- t’ami a priestor pre širšu škálu vol’by spomedzi technologických ponúk. Na druhej strane heterogénnost’ a vzájomná nekompatibilita prináša nutnost’ dodatoˇcnejintegrácie, ktorá predstavuje zbytoˇcnúzát’až navyše. Momen- tálne kl’úˇcovýmslovom na poli integrácie je ESB (Enterprise Service Bus), ktorý v slovenˇcinepoznáme ako podniková zbernica služieb. Systém pod týmto pomenovaním si môžme predstavit’ ako funkˇcnýinteg- raˇcnýsystém postavený na princípoch službovo orientovanej architektúry (SOA - Service Oriented Architecture) so svojbytnou topologiou, ktorá vy- užíva zbernicu dát. Vzhl’adom na to, že máme na trhu celú škálu proprietárnych alebo open source ESB, vyhodnotenie vhodného výberu ESB pre potreby daného pod- niku môže byt’ nel’ahkou úlohou. Hoci majú všetky ESB základné vlast- nosti spoloˇcné,ich realizácia používa úplne diverzné prístupy, štandardy a protokoly. To sa samozrejme odráža i v jednom zo základných kritérii pri porovnávaní ESB, ˇcímje výkon. Našou úlohou bolo priniest’ trochu svetla do danej oblasti touto prácou, ktorá práve poskytne objektívne vý- sledky výkonov od niektorých open source ESB. Hoci v ˇcasepísania tejto práce už niekol’ko podobných testovaní prebehlo, táto práca je jedineˇcná v tom, že prvýkrát prezentuje výkon nováˇcikana poli integraˇcnýchsys- témov a to SwitchYard. SwitchYard je vydávaná pod taktovkou najväˇcšej ˇcistoopen source spoloˇcnostiRed Hat. Na SwitchYard sa teraz upriamuje zvýšená pozornost’, lebo ho Red Hat plánuje nahradit’ za ich doterajší JBoss ESB[3]. Dalejˇ táto práca sumarizuje a sprehl’adˇnujeteoretické pozadie ESB a pravidiel SOA. Ponúka detailnú dokumentáciu, ktorá v prípade potreby testovania d’alších verzii môžu poslúžit’ vývojárom. Pri tvorbe tejto práce sme prechádzali tromi fázami, konkrétne teore- tickou ˇcast’ou, praktickou ˇcast’ou a testovaním. V teoretickej ˇcastisi vy- svetl’ujeme základné poznatky zo strany integraˇcnýchsystémov, do kto- rých spadá aj architektúra ESB a špecifikácie SCA, o ktorých budeme mat’ samostatné kapitoly. Dalejˇ našu pozornost’ upriamím na vysvetlenie SOA pravidel a k definovaniu pojmu ESB, ktorý i dnes býva nesprávne chápaný. V praktickej ˇcastisa venujeme metodike testovania, implementácii testova- cích scenárov SwitchYardu a prezentovaniu výsledkov. Metodiku testova- nia v mnohom ovplyvnil open source testovací framework od AdroitLogic 1 1. ÚVOD s názvom ESB Performance. Dané scenáre, ktoré framework podporuje pat- ria do dnešných najˇcastejšíchscenárov, s ktorými je možné sa stretnút’ v ESB systémoch. Vel’kú ˇcast’ našej energie sme vložili do implementácie SwitchYard sce- nárov kvôli nášmu nedostatku znalostí s používaním tejto technológie a im- plementaˇcnouzávislost’ou, ktorá je daná požiadavkami ESB Performance. Ostatné ESB boli nakonfigurované už v spustitel’nej podobe, preto sme sa jej vývojom nezaoberali. Náš projekt bude poskytnutý tvorcom testovacieho frameworku a tiež bude sprístupnený open source pre zaistenie d’alšieho vývoja. V ˇcastitestovania sa venujeme priebehu testovania a prezentovaniu výsledkov vo forme ˇciarových grafov. Jednu kapitolu venujeme prezen- tovaniu štyroch ESB, ktoré sme považovali za najvhodnejšie vzhl’adom na spol’ahlivost’ výsledkov. Sú to SwitchYard v0.7, Mule ESB v3.3.0., Ul- traESB v1.7.1. a WSO2ESB v4.6.0. V jednoduchosti si predstavujeme zá- kladné špecifiká daných ESB a následne prezentujeme samostatné výsledky každého z nich. V siedmej a poslednej kapitole koneˇcne sp´lˇnamepod- statu práce danou v názve. Porovnanie výkonu prebieha z niekol’kých per- spektív: zo strany scenárou použitia, zo strany vel’kosti posielaných správ a zo strany súbežných prístupov (používatel’ov). Na záver si zhrnieme vý- sledky. Dalšieˇ grafy vrátane celkového grafu je možné nájst’ v prílohovej ˇcasti. 2 2 Služobne orientovaná architektúra (SOA) Aplikaˇcnéprostredie dnešných podnikových systémov je mimoriadne he- terogénne ak vezmeme do úvahy množstvo protokolov a štandardov, ktoré používa. Vzniká tak vel’ký problém nekonzistencie rôznych apliká- cií od rôznych dodávatel’ov. Integrácia týchto aplikácií je pritom jednou z podmienok pre dosiahnutie prosperujúcej organizácie, a preto je nutné hl’adat’ riešenia na tieto požiadavky[1]. Ciastoˇcnériešenieˇ prinieslo stano- venie SOA pravidiel, podl’a ktorých sa každý podnikovo orientovaný sys- tém mohol budovat’, aby bol neustále integrovatel’ný. Na základe týchto pravidiel vznikali rôzne integraˇcnériešenia, ktoré však prechádzali neustá- lym vývinom. Viac k tejto téme si povieme v tejto kapitole. 2.1 Integraˇcnésystémy a SOA pravidlá Zaistenie prepojenosti systému znamenalo pre podniky nemalé finanˇcné prostriedky. Integrácia systémov bola zaist’ovaná ad-hoc podl’a potreby a bez pravidiel alebo postupov. Následne vzniknuté komplikácie vo sfére integrácie viedli postupne k definovaniu pravidiel SOA. Zámerne uvádzam slovo „postupne”, pretože princípy SOA nevznikli revoluˇcne,ale evoluˇcne a stále sa uˇciliz chýb svojich predchodcov. V priebehu rokov sa vyskytli nové technológie ako napr. XML a webové služby (web services)1[2], ktoré boli taktiež doplˇnovanédo spomínaných pravidiel. SOA je sada princípov a metodológií, ktoré pomáhajú k integrácii zložitých aplikácií, ktoré posky- tujú služby[6]. SOA pravidlá by mali slúžit’ k tomu, aby sa daný systém navrhol tak, aby sa v budúcnosti mohol agilne vyvíjat’ a rozširovat’. Agilný prístup je schopnost’ tvorit’ a reagovat’ na zmeny k dosiahnutiu úžitku v turbulentnom podnikatel’skom prostredí[4]. Pristúpime teraz k jej 8-mim hlavným princípom[5]: 1. Štandardizovaný kontrakt služby (Standardized Service Contract) – Kontrakt služby je presne definovaný. To znamená, že už pri ná- vrhu SOA komponenty treba zvážit’ jej technické rozhranie a formát dát. Kontrakt je považovaný za istý sl’ub danej služby svojmu oko- liu, ˇcobude poskytovat’. 2. Slabé väzby medzi komponentami (Service Loose Coupling) – Väzby medzi službami by mali byt’ ˇconajtenšie. To sa dá docielit’ 1. Web Service (WS) je systém pre komunikáciu elektronických zariadení po internetovej sieti. 3 2. SLUŽOBNE ORIENTOVANÁ ARCHITEKTÚRA (SOA) tým, že sú závislosti komponent dodatoˇcnedefinované tesne pred použitím a naviac externe, teda mimo vyvinutú službu, ˇcímsa re- dukuje závislost’ kontraktu služby, jej implementaˇcnejlogiky a kon- zumentov. 3. Princíp abstrakcie (Service Abstraction) – Jeho ciel’om je ˇconajviac
Load more

Recommended publications
  • ESB and SOA Infrastructure
    eBook ESB and SOA Infrastructure The Enterprise Service Bus (ESB) is a form of plumbing that enables effective SOA implementation. But understanding the ESB remains an industry-wide quest. Open source consultant Jeff Genender lists a message bus first on his list of the basic building blocks of a successful SOA infrastructure. And yet, some recent Forrester survey results show that first-time SOA infrastructure purchases maybe shifting from ESBs to other SOA technologies. Read this eBook to learn more about ESBs including: • The role of ESBs in application integration • Tips on open source and SOA infrastructure from Jeff Genender • Forrester's take on where the ESB fits in today's enterprise architecture Sponsored By: SearchSOA.com eBook ESB and SOA Infrastructure eBook ESB and SOA Infrastructure Table of Contents The ESB and its role in application integration architecture Working with ActiveMQ – Tips from TSSJS presenter Jeff Genender part one On SOA infrastructure – Tips from TSSJS presenter Jeff Genender part two Forrester analysts: SOA still strong Resources from FuseSource Sponsored By: Page 2 of 10 SearchSOA.com eBook ESB and SOA Infrastructure The ESB and its role in application integration architecture By Alan Earls Although enterprise service busses (ESBs) are not new, they can continue to be a nexus for confusion. After many years and many implementations, what they do, how they do it and whether specific products can help create a SOA are all still matters of contention. Chris Harding, a forum director for SOA and client computing at The Open Group, argues that there isn’t always clarity regarding the nature of ESBs.
    [Show full text]
  • Performance Comparison of Jboss Integration Platform Implementations
    Masarykova univerzita Fakulta}w¡¢£¤¥¦§¨ informatiky !"#$%&'()+,-./012345<yA| Performance comparison of JBoss integration platform implementations Master Thesis Elena Medvedeva Brno, May 2014 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Elena Medvedeva Advisor: Mgr. Marek Gr´ac,Ph.D. ii Acknowledgement I would like to thank my technical supervisor from Red Hat, Ing. Pavel Mac´ıkfor sharing his vast experience in the field of performance testing, and for valuable pieces of advice given to me during the preparation of this work. I am grateful to my supervisor Mgr. Marek Gr´ac,Ph.D. for the comments and consultations. Besides, I want to thank all my colleagues who work with me in the JBoss Fuse QA team, for support, and the company Red Hat, which provided me the opportunity to write this thesis. iii Abstract We present the results of our investigation in the field of performance testing of JBoss integration platforms to compare performance of JBoss Fuse and SwitchYard. We design a basic set of performance scenarios to cover basic usage patterns of integration platforms. We formalize the scenarios that are already implemented for SwitchYard, and we develop three new sce- narios. All fifteen scenarios are implemented for JBoss Fuse using Per- fCake and tweaked to be optimal from the performance point of view. In addition performance test execution is automated in distributed en- vironment using Jenkins and SmartFrog.
    [Show full text]
  • Hänninen, Arttu Enterprise Integration Patterns in Service Oriented Systems Master of Science Thesis
    CORE Metadata, citation and similar papers at core.ac.uk Provided by Trepo - Institutional Repository of Tampere University Hänninen, Arttu Enterprise Integration Patterns in Service Oriented Systems Master of Science Thesis Examiner: Prof. Tommi Mikkonen Examiners and topic approved in the council meeting of Faculty of Information Technology on April 3rd, 2013. II TIIVISTELMÄ TAMPEREEN TEKNILLINEN YLIOPISTO Tietotekniikan koulutusohjelma Hänninen, Arttu: Enterprise Integration Patterns in Service Oriented Systems Diplomityö, 58 sivua Kesäkuu 2014 Pääaine: Ohjelmistotuotanto Tarkastajat: Prof. Tommi Mikkonen Avainsanat: Enterprise Integration Patterns, Palvelukeskeinen arkkitehtuuri (SOA), Viestipohjainen integraatio Palvelupohjaisen integraation toteuttaminen mihin tahansa tietojärjestelmään on haas- tavaa, sillä integraatioon liittyvät järjestelmät voivat muuttua jatkuvasti. Integraatiototeu- tusten tulee olla tarpeeksi joustavia, jotta ne pystyvät mukautumaan mahdollisiin muu- toksiin. Toteutukseen voidaan käyttää apuna eri sovelluskehyksiä, mutta ne eivät vält- tämättä takaa mitään standardoitua tapaa tehdä integraatio. Tätä varten on luotu joukko ohjeita (Enterprise Integration Patterns, EIP), jotka kuvaavat hyväksi havaittuja tapoja tehdä integraatioita. Tässä työssä keskitytään näiden mallien tutkimiseen ja siihen, miten niitä voidaan hyödyntää yritysjärjestelmissä. Jotta tutkimukseen saadaan konkreettinen vertailutulos, erään järjestelmän integraatioratkaisu tullaan päivittämään uuteen. Uusi ratkaisu hyödyntää sovelluskehystä,
    [Show full text]
  • Les Meilleures Solutions Open Source
    ESB Les meilleures solutions open source I . T IS OP E N I.1 SMILE Smile est une société d’ingénieurs experts dans la mise en œuvre de solutions open source et l’intégration de systèmes appuyés sur l’open source. Smile est membre de l’APRIL, l’association pour la promotion et la défense du logiciel libre, du PLOSS – le réseau des entreprises du Logiciel Libre en Ile-de-France et du CNLL – le conseil national du logiciel libre. Smile compte plus de 1200 collaborateurs dans le monde ce qui en fait le premier intégrateur français et européen de solutions open source. Depuis 2000 environ, Smile mène une action active de veille technologique qui lui permet de découvrir les produits les plus prometteurs de l’open source, de les qualifier et de les évaluer, de manière à proposer à ses clients les produits les plus aboutis, les plus robustes et les plus pérennes. Cette démarche a donné lieu à toute une gamme de livres blancs couvrant différents domaines d’application. La gestion de contenus (2004), les portails (2005), la business intelligence (2006), la virtualisation (2007), la gestion électronique de documents (2008), les PGIs/ERPs (2008), les VPN open source (2009), les Firewall et Contrôle de flux (2009), les Middleware orientés messages (2009), l’ecommerce et les Réseaux Sociaux d'Entreprise (2010), le Guide de l’open source et NoSQL (2011), Mobile et Recensement et audit (2012) et plus récemment Big Data et ERP open source pour l’e- commerce (2014). Chacun de ces ouvrages présente une sélection des meilleures solutions open source dans le domaine considéré, leurs qualités respectives, ainsi que des retours d’expérience opérationnels.
    [Show full text]
  • ESB Application for Effective Synchronization of Large Volume Measurements Data
    AGH University of Science and Technology Faculty of Electrical Engineering, Automatics, Computer Science and Electronics Department of Computer Science Kraków, Poland Master thesis ESB application for effective synchronization of large volume measurements data Przemysław Wyszkowski Major: Computer science Speciality: Computer networks and distributed systems Thesis supervisor: Register No.: 203792 Dominik Radziszowski, Ph.D. Eng. Kraków, Gen´eve, Dresden 2011 Oświadczenie autora Oświadczam, świadomy odpowiedzialności karnej za poświadczenie nieprawdy, że niniejszą pracę dyplomową wykonałem osobiście i samodzielnie i że nie korzystałem ze źródeł innych niż wymienione w pracy. .................................... (Podpis autora) Contents Streszczenie .........................................4 Zusammenfassung .....................................5 Abstract ...........................................6 Acknowledgements ....................................7 1. Introduction ......................................8 1.1. The Large Hadron Collider . .8 1.2. Scope . 10 1.2.1. Thesis aim . 10 1.2.2. Thesis structure . 11 2. Background information ............................... 12 2.1. Massive data processing in High Energy Physics experiments . 12 2.1.1. Measurement data life-cycle in HEP . 12 2.1.2. The TOTEM experiment . 15 2.2. Used technologies overview . 16 2.2.1. SOA - ESB - OSGi . 16 2.2.2. MOM - JMS - ActiveMQ . 21 2.2.3. EIP - Camel . 24 2.2.4. IoC - DI - Spring . 25 2.2.5. ORM - JPA - Hibernate . 27 2.3. Clarification summary . 28 2.4. Selected frameworks . 29 2.4.1. Apache ServiceMix 4.x . 30 2.4.2. FUSE ESB 4 . 31 2.5. Related works . 31 2.6. Chapter summary . 32 3. System model ..................................... 33 3.1. Current state of art analysis . 33 3.1.1. Current processing model . 33 3.1.2. Existing state evaluation . 35 3.2. The TOTEM Offline Database Project .
    [Show full text]
  • Buenas Prácticas Para La Orquestación De Servicios BPM-SOA Para La
    MARCO DE REFERENCIA PARA LA ORQUESTACION DE SERVICIOS SOBRE ESBs OPEN SOURCE SUMINISTRANDO UN CONJUNTO DE BUENAS PRACTICAS QUE SIRVAN COMO INSTRUMENTO A UN ARQUITECTO DE SOFTWARE PARA LA IMPLEMENTACION DE UNA SOA Andrés Camilo Rojas Mariño David Alfonso Tafur Ramírez Universidad Piloto de Colombia Ingeniería de Sistemas Bogotá D.C. 2014 3 MARCO DE REFERENCIA PARA LA ORQUESTACION DE SERVICIOS PARA LA IMPLEMENTACION DE UNA SOA Coinvestigadores Andrés Camilo Rojas Mariño David Alfonso Tafur Ramírez Trabajo de tesis para optar por el título de Ingeniero de Sistemas Docente Investigador Ingeniero Andrés Mauricio Marín Restrepo Asesor metodológico: Sociólogo Ignacio Hernández Molina Universidad Piloto de Colombia Ingeniería de Sistemas Bogotá D.C. 2014 4 A nuestras familias, profesores y amigos quienes pusieron entre todos un grano de arena para hacer de este trabajo una realidad. 5 AGRADECIMIENTOS A nuestras familias quienes nos apoyaron a lo largo de nuestra carrera y a quienes les debemos nuestro trabajo y el fruto de lo que somos en este momento, sin su apoyo el desarrollo de nuestras carreras profesionales no hubiese sido el mismo. A nuestro director de tesis, Ing. Andres Mauricio Marín por su esfuerzo y dedicación, quien con sus conocimientos, su experiencia, su paciencia, su motivación, por sus consejos y el excelente desempeño de su profesión como docente ayudo a formarnos como personas e investigadores y ha logrado hacer de este proyecto una realidad. A la Universidad Piloto de Colombia por darnos la oportunidad de estudiar y ser profesionales. También nos gustaría agradecer a nuestros profesores los cuales durante toda la carrera profesional de Ingeniera de Sistemas aportaron con sus conocimientos aportaron en nuestro crecimiento en las diferentes áreas profesionales y de la vida.
    [Show full text]
  • Governing a Distributed SOA
    Header 1 Governing a Distributed SOA IONA Technologies September 2007 Governing a Distributed SOA 2 Executive Summary While the advantages of a service-oriented architecture (SOA) are apparent to most organizations, the challenge of governing the SOA infrastructure still remains a concern for leading enterprises. As organizations incorporate their IT assets into networks of reusable services they are challenged with how to enforce service reuse and how to govern proper usage. Information about what services exist and how to use them are often inconsistently documented in multiple locations and formats, making it difficult to reuse services and enforce policies. Compounding the challenge of SOA governance is the advent of the distributed architecture, which analysts predict will become the prevailing deployment model for SOA in the coming years. A distributed, microkernel design delivers a lightweight, flexible runtime that can be deployed at the endpoints, as opposed to the centralized, hub-and-spoke middleware solutions traditionally offered by most SOA vendors today. These vendors are racing to deliver microkernel-based SOA infrastructure solutions to market, proving distributed architecture is a superior SOA design model. While a distributed architecture allows organizations to better leverage existing IT investments, adopt SOA incrementally and avoid vendor lock-in, its distributed nature creates additional governance challenges. Organizations must drive and streamline the deployment of services into a distributed SOA network across many systems and locations, as opposed to governing services in the more centralized architecture created using traditional middleware solutions. While the challenge of SOA governance with a distributed SOA may seem daunting at first, innovative tools are available today to help leading enterprises achieve SOA success.
    [Show full text]
  • Open Geospatial Consortium, Inc
    Open Geospatial Consortium, Inc. Date: 2010-08-18 Reference number of this document: OGC 10-130 Category: OGC® Public Engineering Report Editor: Debbie Wilson OGC® OWS-7 Aviation – FUSE Deployment Engineering Report . Copyright © 2010 Open Geospatial Consortium, Inc. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. Warning This document is not an OGC Standard. This document is an OGC Public Engineering Report created as a deliverable in an OGC Interoperability Initiative and is not an official position of the OGC membership. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an OGC Standard. Further, any OGC Engineering Report should not be referenced as required or mandatory technology in procurements. Document type: OpenGIS® Engineering Report Document subtype: NA Document stage: Approved for public release Document language: English OGC 10-130 Preface This public Engineering Report (ER) is a deliverable of the Open Geospatial Consortium (OGC) Interoperability Program Open Web Service (OWS) Testbed phase 7 (OWS-7). The document describes the integration results of deploying an OGC Web Feature Service onto the FUSE Enterprise Service Bus. FUSE ESB is the Federal Aviation Administration service bus of choice for its System Wide Information Management (SWIM) program. The changes made in this document version, relative to the previous version, are tracked by Microsoft Word, and can be viewed if desired. If you choose to submit suggested changes by editing this document, please first accept all the current changes, and then make your suggested changes with change tracking on.
    [Show full text]
  • Progress Announces Availability of Fuse™ ESB 4.0
    October 14, 2008 Progress Announces Availability of Fuse™ ESB 4.0 Major Release Combines Standards-Based Apache Open Source Projects with World-Class Enterprise Support, Developer Tools and Certified Software Packaging for the Enterprise BEDFORD, Mass.--October 14, 2008--Progress Software Corporation (NASDAQ: PRGS), a provider of leading application infrastructure software to develop, deploy, integrate and manage business applications, today released its FUSE™ ESB 4.0, an enterprise version of Apache ServiceMix 4.0, the most widely-deployed, standards based, open source enterprise service bus (ESB). FUSE 4.0 comprises important new capabilities that will help the productivity of developers, including support for the Java™ Business Integration (JBI) 2.0 standard and backwards compatibility with JBI 1.0, which ensures that FUSE 3.X (and ServiceMix 3.X) components are seamlessly deployable onto FUSE ESB 4.0. FUSE 4.0 also supports the emerging OSGI standard giving users greater flexibility in packaging and deploying infrastructure components across the enterprise. A new FUSE Integration Designer is introduced with FUSE 4.0 that provides easy point and click creation of Enterprise Integration Patterns (EIPs), the debugging and validation of EIPs and the visualization of pre-existing routes (allowing reverse engineering). Moreover, several standards-based improvements and powerful features have been added. FUSE ESB 4.0 is a tested and certified release of the ServiceMix open source project at the Apache Software Foundation. Progress selects specific releases from the project, which it tests, fully documents, and distributes under the Apache License, complemented by 24x7 enterprise support, consulting, and training for customers looking to deploy open source SOA technology in mission-critical business applications.
    [Show full text]
  • ESB Application for Effective Synchronization of Large Volume Measurements Data
    AGH Univeristy of Science and Technology Faculty of Electrical Engineering, Automatics, Computer Science and Electronics Department of Computer Science Kraków, Poland Master thesis ESB application for effective synchronization of large volume measurements data Przemysław Wyszkowski CERN-THESIS-2011-098 15/09/2011 Major: Computer science Speciality: Computer networks and distributed systems Thesis supervisor: Register No.: 203792 Dominik Radziszowski, Ph.D. Eng. Kraków, Gen´eve, Dresden 2011 Oświadczenie autora Oświadczam, świadomy odpowiedzialności karnej za poświadczenie nieprawdy, że niniejszą pracę dyplomową wykonałem osobiście i samodzielnie i że nie korzystałem ze źródeł innych niż wymienione w pracy. .................................... (Podpis autora) Contents Streszczenie .........................................4 Zusammenfassung .....................................5 Abstract ...........................................6 Acknowledgements ....................................7 1. Introduction ......................................8 1.1. The Large Hadron Collider . .8 1.2. Scope . 10 1.2.1. Thesis aim . 10 1.2.2. Thesis structure . 11 2. Background information ............................... 12 2.1. Massive data processing in High Energy Physics experiments . 12 2.1.1. Measurement data life-cycle in HEP . 12 2.1.2. The TOTEM experiment . 14 2.2. Used technologies overview . 16 2.2.1. SOA - ESB - OSGi . 16 2.2.2. MOM - JMS - ActiveMQ . 21 2.2.3. EIP - Camel . 24 2.2.4. IoC - DI - Spring . 25 2.2.5. ORM - JPA - Hibernate . 27 2.3. Clarification summary . 28 2.4. Selected frameworks . 29 2.4.1. Apache ServiceMix 4.x . 30 2.4.2. FUSE ESB 4 . 31 2.5. Related works . 31 2.6. Chapter summary . 32 3. System model ..................................... 33 3.1. Current state of art analysis . 33 3.1.1. Current processing model . 33 3.1.2.
    [Show full text]
  • When to Use Open Source
    When to Use Open Source Making the right decisions about open source and commercially licensed SOA software Large corporations have traditionally relied on commercially licensed (“closed source”) software for mission-critical infrastructure, but open source solutions are increasingly common in enterprise architecture. As open source technologies have earned a reputation for reliability and performance, enterprise IT organizations now deploy a mix of open and closed source software with great success. Open source software is developed collaboratively and is owned by a community rather than a single vendor. The source code is freely available, and users are permitted and encouraged to change, improve, and redistribute the software – subject to the terms of the open source license. The benefits of open source software include: Code Transparency – Enterprises enjoy full access to the source code of an open source solution, so their IT infrastructure isn’t running on a black box of proprietary code. Standards Support – Open source projects tend to be designed to support industry standards, and to interoperate with other open source and commercial technologies. Cost savings – Users do not pay a license fee to adopt open source software nor do they pay for updates, significantly reducing total cost of the project. Vendor-neutrality – True open source software is developed and owned by a developer community, so open source adopters are not locked in to a vendor’s platform by proprietary modules and technical prerequisites. Innovation – With a large community that includes end users contributing to the project, open source software provides a practical vehicle for the latest technology advancements. Despite these benefits, deploying open source software can introduce some risk: open source solutions do not always have the support and services typically provided by commercial software vendors.
    [Show full text]
  • FUSE™ Integration Designer User Guide
    FUSE™ Integration Designer FUSE™ Integration Designer User Guide Version 1.2 May 2009 FUSE™ Integration Designer User Guide Progress Software Version 1.2 Publication date 23 Jul 2009 Copyright © 2001-2009 Progress Software Corporation and/or its subsidiaries or affiliates. Legal Notices Progress Software Corporation and/or its subsidiaries may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this publication. Except as expressly provided in any written license agreement from Progress Software Corporation, the furnishing of this publication does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Any rights not expressly granted herein are reserved. Progress, IONA, IONA Technologies, the IONA logo, Orbix, High Performance Integration, Artix, FUSE, and Making Software Work Together are trademarks or registered trademarks of Progress Software Corporation and/or its subsidiaries in the US and other countries. Java and J2EE are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. CORBA is a trademark or registered trademark of the Object Management Group, Inc. in the US and other countries. All other trademarks that appear herein are the property of their respective owners. While the information in this publication is believed to be accurate Progress Software Corporation makes no warranty of any kind to this material including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Progress Software Corporation shall not be liable for errors contained herein, or for incidental or consequential damages in connection with the furnishing, performance or use of this material.
    [Show full text]