DOCSLIB.ORG

Technologies Web, Web Services, SOA, Intégration D'applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Technologies Web, Web Services, SOA, Intégration D'applications Technologies Web, Web Services, SOA, intégration d'applications Standards incontournables dans les échanges de données sur le Web, XML et JSON ont une place majeure dans les applications Web, les Systèmes d’Information et les projets d’intégration. Les Web Services, quant à eux, apportent une réponse efficace aux besoins d’intégration inter-applications. Ils offrent un modèle d’architecture centré sur l’accès aux services (SOA, micro services, API) qui permettent d’améliorer la réactivité du Système d’Information. L’adoption d’une architecture WOA permet de faire les liens entre ces applications sur le Web à grande échelle. ORSYS propose des filières pour comprendre les concepts afférents à ces technologies et apprendre les meilleures méthodes pour les mettre en ?uvre au sein des Systèmes d’Information. Etat de l'art : XML, JSON, Web Services, SOA, WOA XML & JSON, synthèse (réf. XML) .... p.2 Services Web, synthèse (réf. WSN) .... p.4 WOA, architecture orientée Web, synthèse (réf. BOA) .... p.6 SOA, architecture orientée services, synthèse (réf. SAO) .... p.8 XML : conception et développement d'applications Technologies XML, conception, mise en œuvre (réf. PXM) .... p.10 XML, modéliser ses documents et données (réf. CAX) .... p.12 Développer avec XSL-T et XSL-FO (réf. LSX) .... p.14 Web Services : développement Développer des Web Services en Java (réf. DSJ) .... p.16 Web Services RESTful, développement avancé en Java (réf. WER) .... p.18 Architecture REST, développer des Web Services en PHP (réf. STE) .... p.20 WCF, développer des Web Services en .NET (réf. WBS) .... p.22 .NET, développer des Web Services REST (réf. STW) .... p.24 REST API, bonnes pratiques et sécurité (réf. REH) .... p.26 SoapUI, automatiser les tests de ses services Web Rest et SOAP (réf. RSO) .... p.28 Architecture de services : SOA, WOA, ESB Réaliser une architecture microservices en Java (réf. RUL) .... p.30 Réaliser une architecture WOA/RESTful en JavaScript (réf. TFU) .... p.32 SOA, conception d'une architecture de services (réf. SOB) .... p.34 Langage BPMN 2.0, modéliser efficacement ses processus métiers (réf. BMN) .... p.36 BPMN et SOA, modéliser les processus et concevoir les services (réf. BPM) .... p.38 Intégration d'applications SOA, mise en œuvre en Open Source/Java (réf. SOD) .... p.40 Apache Camel, mise en œuvre (réf. APC) .... p.42 Spring Integration, mise en œuvre (réf. SPR) .... p.44 Talend Open Studio for ESB, intégration de services (réf. TLS) .... p.46 ORSYS, La Grande Arche, Paroi Nord, 92044 Paris La Défense cedex. Tél : +33 (0)1 49 07 73 73. Fax : +33(0)1 49 07 73 78 page 1 Cours de synthèse de 2 XML & JSON, synthèse jour(s) > Technologies Web> Web Services, SOA, intégration d'applications Réf : XML Participants Standards incontournables dans les échanges de données textuelles sur le Web, XML et JSON ont pris une place majeure dans les applications Web, les Systèmes d'Information, l'intégration de données et Architectes des Systèmes d'applications. De son côté XML, à la base de nombreux autres langages, s'est entouré d'une multitude d'Information, responsables d'outils pour la définition et la manipulation de données. de projets, analystes et développeurs désirant OBJECTIFS PEDAGOGIQUES comprendre XML et JSON, de manière à les mettre en Lire et comprendre des documents XML et JSON œuvre dans des architectures Modéliser et définir des données en XML et JSON Web. Choisir les outils adaptés aux besoins de votre application Pré-requis Comprendre la place de XML et de JSON dans les architectures Web Connaissances de base en architectures applicatives et 1) Concepts de base 5) Navigation dans les arbres XML avec Xpath, le développement logiciel, en 2) Introduction à XML et JSON langage de styles XSL particulier dans le domaine du 6) Traitement de XML avec SAX et DOM Web. 3) Définition de données XML avec DTD et XMLschema 7) Bases de données XML et JSON Prix 2020 : 1490€ HT 4) Définition de données JSON 8) Architecture SOA et Web Services Dates des sessions 1) Concepts de base PARIS 19 mar. 2020, 18 juin 2020 - Gestion de documents : structure, contenu et présentation. 03 sep. 2020, 10 déc. 2020 - Langages à balises : SGML, HTML et CSS. Comparaison avec les langages Wysiwyg. - Le Web 2.0, XML et JSON. Communication navigateur-serveur asynchrone avec AJAX. - Le client riche avec les technologies HTML5, CSS3 et JavaScript. Place de XHTML 2.0 ? Modalités 2) Introduction à XML et JSON d’évaluation - Le modèle de données XML : éléments et attributs, document bien formé et valide. L’objectif de cette formation - Représentation sérialisée ou arborescente, le modèle logique XML Infoset, le parsing de XML. étant essentiellement de fournir une synthèse des - La galaxie XML : standards techniques et standards métiers. méthodes et technologies - XML et bureautique : les standards Open Document d'Open Office et OpenXML de Microsoft. EXI : l'XML existantes, il n’est pas compressé. nécessaire d’avoir recours à - Le modèle de données JSON : objet, tableau et valeurs littérales. une évaluation des acquis. - Intégration avec les langages de programmation (JavaScript, PHP...). Les frameworks utilisant JSON (jQuery, Angular...). - Le parsing de JSON. Différences avec XML. Compétences du - Les outils de développement XML et JSON. formateur 3) Définition de données XML avec DTD et XMLschema Les experts qui animent la formation sont des - Document Type Definition (DTD) et typage des documents. spécialistes des matières - Définition d'éléments, d'attributs, d'entités, éléments simples et composés, entités paramètres. abordées. Ils ont été - XMLschema : types simples et types complexes, déclaration des éléments et des attributs. validés par nos équipes - XMLschema : les constructeurs de collections, héritage de types, réutilisation de définitions. pédagogiques tant sur le - Les espaces de noms xmlns : intérêt pour l'intégration de données XML. plan des connaissances - Les bonnes pratiques : règles d'écriture DTD ou schémas XML, la gestion de versions. métiers que sur celui de la pédagogie, et ce pour chaque - Les principaux outils de développement de DTD et schémas XML. cours qu’ils enseignent. Ils ont au minimum cinq à dix 4) Définition de données JSON années d’expérience dans leur domaine et occupent - Schéma JSON : concepts de base, mots-clés de validation, mots-clés hyper-médias. ou ont occupé des postes à - Les méta-schémas pour définir les schémas JSON et les formats Hyper-Schema. responsabilité en entreprise. - Les schémas standards : ex. coordonnées géographiques, card, calendrier, adresse... - Bibliothèques de validation de schémas JSON. Moyens 5) Navigation dans les arbres XML avec Xpath, le langage de styles XSL pédagogiques et - L'adressage des nœuds dans un arbre XML : navigation et expressions de chemin. techniques - Terminologie Xpath : nœuds, syntaxe des expressions, axes de navigation. - Expressions de chemin XPath : parcours des nœuds, expressions régulières, prédicats de sélection, • Les moyens pédagogiques fonctions. et les méthodes d'enseignement utilisés - Transformation de données avec XSLT : les règles de production, sélection des nœuds avec XPath, sont principalement : aides production des résultats. audiovisuelles, documentation - Exemples de transformation XML-XML, XML-HTML. et support de cours, exercices - Les processeurs XSLT. Intégration dans l'architecture n-tiers. pratiques d'application et - Formatage des documents avec XSL/FO : objets, masques, mises en page. corrigés des exercices pour - Les processeurs XSL/FO. Intégration avec les processeurs XSLT. les stages pratiques, études de cas ou présentation de cas 6) Traitement de XML avec SAX et DOM ORSYS, La Grande Arche, Paroi Nord, 92044 Paris La Défense cedex. Tél : +33 (0)1 49 07 73 73. Fax : +33(0)1 49 07 73 78 page 2 réels pour les séminaires de - Traitement événementiel avec l'API SAX, exemple d'utilisation avec des objets Java, les parseurs SAX. formation. - Traitement par programme via l'API DOM, utilisation du parseur SAX pour la traduction de XML en objet, les • A l'issue de chaque stage ou parseurs DOM. séminaire, ORSYS fournit aux - Les outils de développement d'application XML. Conversion XML/JSON. participants un questionnaire d'évaluation du cours qui 7) Bases de données XML et JSON est ensuite analysé par nos équipes pédagogiques. - Bases de données orientées document : XML ou JSON comme modèle de données. • Une feuille d’émargement - Stockage et indexation des documents, stockage relationnel. par demi-journée de présence - Langages de requêtes pour XML : SQL/XML, XQuery, XUpdate. est fournie en fin de formation - Langages de requêtes pour JSON : JSONiq, JsonPath, Json Query, Jaql. ainsi qu’une attestation de fin - SGBD orienté document (XML, NoSQL) versus SGBD relationnel avec support XML/JSON. de formation si le stagiaire a - Intégration de données : vues intégrées de données hétérogènes en XML, intégration de schémas, bien assisté à la totalité de la traitement de requêtes. session. - Les principaux outils d'intégration de données XML : EII (Enterprise Information Integrators). 8) Architecture SOA et Web Services - Web Services : client, fournisseur, annuaire de services et intégration d'applications. - Description des services avec WSDL. Référencement dans l'annuaire UDDI. - Protocoles de communication XML : XML RPC et SOAP. - Architectures légères avec ReST. - Choisir la bonne architecture Web Services : ReST/JSON versus XML/SOAP. - Qualité de services : WS-Transaction, WS-Coordination, WS-Security. - Intégration dans les serveurs d'applications .NET et JEE.
Load more

Recommended publications
  • Empirical Study on the Usage of Graph Query Languages in Open Source Java Projects
    Empirical Study on the Usage of Graph Query Languages in Open Source Java Projects Philipp Seifer Johannes Härtel Martin Leinberger University of Koblenz-Landau University of Koblenz-Landau University of Koblenz-Landau Software Languages Team Software Languages Team Institute WeST Koblenz, Germany Koblenz, Germany Koblenz, Germany [email protected] [email protected] [email protected] Ralf Lämmel Steffen Staab University of Koblenz-Landau University of Koblenz-Landau Software Languages Team Koblenz, Germany Koblenz, Germany University of Southampton [email protected] Southampton, United Kingdom [email protected] Abstract including project and domain specific ones. Common applica- Graph data models are interesting in various domains, in tion domains are management systems and data visualization part because of the intuitiveness and flexibility they offer tools. compared to relational models. Specialized query languages, CCS Concepts • General and reference → Empirical such as Cypher for property graphs or SPARQL for RDF, studies; • Information systems → Query languages; • facilitate their use. In this paper, we present an empirical Software and its engineering → Software libraries and study on the usage of graph-based query languages in open- repositories. source Java projects on GitHub. We investigate the usage of SPARQL, Cypher, Gremlin and GraphQL in terms of popular- Keywords Empirical Study, GitHub, Graphs, Query Lan- ity and their development over time. We select repositories guages, SPARQL, Cypher, Gremlin, GraphQL based on dependencies related to these technologies and ACM Reference Format: employ various popularity and source-code based filters and Philipp Seifer, Johannes Härtel, Martin Leinberger, Ralf Lämmel, ranking features for a targeted selection of projects.
    [Show full text]
  • SOA Using Open ESB, BPEL, and Netbeans” > Focus Is to Explain How WSDL, BPEL, JBI, Open ESB, Java EE Work Together
    SSOOAA uussiinngg OOppeenn EESSBB,, BBPPEELL,, aanndd NNeettBBeeaannss SSaanngg SShhiinn JJaavvaa TTeecchhnnoollooggyy EEvvaannggeelliisstt SSuunn MMiiccrroossyysstteemmss,, IInncc.. 1 Three Talks I Did on SOA Here • NetBeans Day: “Tools for Simplifying SOA” > Focus is to show how to use NetBeans for building a simple Composite application • GlassFish Day: “Open ESB and GlassFish” > Focus is to show more advanced features such as Intelligent Event Processing module for building a composite application • Sun Tech Day: “SOA using Open ESB, BPEL, and NetBeans” > Focus is to explain how WSDL, BPEL, JBI, Open ESB, Java EE work together 2 Agenda • Composite Applications • BPEL • Services • JBI • Java EE Service Engine • Open ESB • Open ESB runtime, tools, and sample apps • Demo 3 CCoommppoossiittee AApppplliiccaattiioonnss Traditional Application Development • Point technologies, products, and APIs > For example: EJB, Spring, Hibernate, JSF, Servlets, Struts, etc. • Lots of glue written by developers > Requires a great deal of expertise & time > Inflexible 5 Composite Applications • A way to compose applications from reusable parts • Composite applications employ SOA principles > Features exposed as Web services > Standards-based interaction between services > Are themselves composable 6 WWSSDDLL TTuuttoorriiaall ((OOppttiioonnaall PPrreesseennttaattiioonn)) Why WSDL? • Enables automation of communication details between communicating partners – Machines can read WSDL – Machines can invoke a service defined in WSDL • Discoverable through registry
    [Show full text]
  • Graphql Attack
    GRAPHQL ATTACK Date: 01/04/2021 Team: Sun* Cyber Security Research Agenda • What is this? • REST vs GraphQL • Basic Blocks • Query • Mutation • How to test What is the GraphQL? GraphQL is an open-source data query and manipulation language for APIs, and a runtime for fulfilling queries with existing data. GraphQL was developed internally by Facebook in 2012 before being publicly released in 2015. • Powerful & Flexible o Leaves most other decisions to the API designer o GraphQL offers no requirements for the network, authorization, or pagination. Sun * Cyber Security Team 1 REST vs GraphQL Over the past decade, REST has become the standard (yet a fuzzy one) for designing web APIs. It offers some great ideas, such as stateless servers and structured access to resources. However, REST APIs have shown to be too inflexible to keep up with the rapidly changing requirements of the clients that access them. GraphQL was developed to cope with the need for more flexibility and efficiency! It solves many of the shortcomings and inefficiencies that developers experience when interacting with REST APIs. REST GraphQL • Multi endpoint • Only 1 endpoint • Over fetching/Under fetching • Fetch only what you need • Coupling with front-end • API change do not affect front-end • Filter down the data • Strong schema and types • Perform waterfall requests for • Receive exactly what you ask for related data • No aggregating or filtering data • Aggregate the data yourself Sun * Cyber Security Team 2 Basic blocks Schemas and Types Sun * Cyber Security Team 3 Schemas and Types (2) GraphQL Query Sun * Cyber Security Team 4 Queries • Arguments: If the only thing we could do was traverse objects and their fields, GraphQL would already be a very useful language for data fetching.
    [Show full text]
  • Graphql-Tools Merge Schemas
    Graphql-Tools Merge Schemas Marko still misdoings irreproachably while vaulted Maximilian abrades that granddads. Squallier Kaiser curarize some presuminglyanesthetization when and Dieter misfile is hisexecuted. geomagnetist so slothfully! Tempting Weber hornswoggling sparsely or surmisings Pass on operation name when stitching schemas. The tools that it possible to merge schemas as well, we have a tool for your code! It can remember take an somewhat of resolvers. It here are merged, graphql with schema used. Presto only may set session command for setting some presto properties during current session. Presto server implementation of queries and merged together. Love writing a search query and root schema really is invalid because i download from each service account for a node. Both APIs have root fields called repository. That you actually look like this case you might seem off in memory datastore may have you should be using knex. The graphql with vue, but one round robin approach. The name signify the character. It does allow my the enums, then, were single introspection query at not top client level will field all the data plan through microservices via your stitched interface. The tools that do to other will a tool that. If they allow new. Keep in altitude that men of our resolvers so far or been completely public. Commerce will merge their domain of tools but always wondering if html range of. Based upon a merge your whole schema? Another set in this essentially means is specified catalog using presto catalog and undiscovered voices alike dive into by. We use case you how deep this means is querying data.
    [Show full text]
  • Red Hat Managed Integration 1 Developing a Data Sync App
    Red Hat Managed Integration 1 Developing a Data Sync App For Red Hat Managed Integration 1 Last Updated: 2020-01-21 Red Hat Managed Integration 1 Developing a Data Sync App For Red Hat Managed Integration 1 Legal Notice Copyright © 2020 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Architecture of Mule and Servicemix 42 3 ■ Setting up the Mule and Servicemix Environments 72 4 ■ the Foundation of an Integration Solution 111
    Open Source ESBs in Action Open Source ESBs in Action EXAMPLE IMPLEMENTATIONS IN MULE AND SERVICEMIX TIJS RADEMAKERS JOS DIRKSEN MANNING Greenwich (74° w. long.) For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact: Special Sales Department Manning Publications Co. Sound View Court 3B Fax: (609) 877-8256 Greenwich, CT 06830 Email: [email protected] ©2009 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15% recycled and processed elemental chlorine-free Development Editor: Jeff Bleil Manning Publications Co. Copyeditors: Liz Welch, Tiffany Taylor Sound View Court 3B Typesetter: Denis
    [Show full text]
  • Proof of Concept Implementation of an Enterprise Service Bus for Health Information Exchanges
    PHILIPPINE ENGINEERING JOURNAL PC Zuñiga, et al 49 PEJ 2020; Vol. 41, No. 1: 49-66 Proof of Concept Implementation of an Enterprise Service Bus for Health Information Exchanges Philip Christian Zuniga, Joseph Benjamin Del Mundo, Edgardo Felizmenio, Marie Jo-anne Mendoza and Rose Ann Zuniga Computer Security Group, Department of Computer Science, University of the Philippines - Diliman Abstract – Integration of health systems is one of the biggest problem in eHealth today. There are a lot of systems, yet they were developed using different platforms and technologies, making them virtually impossible to connect. In this paper, we discussed how to implement an ESB as the integration platform for health data. We identified use cases and functional requirements. Logical and deployment architecture were developed, and an actual proof of concept of an ESB is developed. Experiments were also done to determine the overhead caused by the ESB. Some of the functionalities of the ESB were examined to determine their individual overheads. Keywords: Enterprise Service Bus, Interoperability, Health Information Exchange, OpenHIE. I. INTRODUCTION During the past few years, the healthcare industry has witnessed a growth in the development of Health Information Systems. Hospitals, both public and private, rural health clinics, and even individual clinics of medical practitioners have been developing or acquiring their own Electronic Medical Records (EMRs), and Hospital Information Systems (HIS). The goal of these systems is to ensure a secure, organized and effective way of collecting and storing patient data [1]. The increase in the number of edge applications leads to the increase of patient data that are stored separately and independently, depending on the application that collected the data.
    [Show full text]
  • Kuali Student Advanced Camp
    Kuali Student Advanced CAMP June 19-20, 2008 Jens Haeusser Director, Strategy Information Technology Objectives . At the end of this session you will have seen . The Kuali Student technical architecture vision . The results of our efforts to date . The working relationships in place to support our efforts Kuali Student – Advanced CAMP June 19-20 2 Agenda . Kuali Student’s Vision . Our vision for Phase I and Phase II (July 2007 – May 2008) . Our execution of the vision . Kuali Student Architecture . Web Services Stack . Development Infrastructure . Our Current Challenges . Relationships with vendors, open source, and Kuali . On the Leading Edge While Remaining Flexible . Getting Validation of Our Work Kuali Student – Advanced CAMP June 19-20 3 Background . Modular, standards-based next generation student system . Community Source project with a 5 year timeline . UBC, Berkeley, Florida, Maryland, San Joaquin Delta, Southern California . MIT, Cambridge . Person centric system . Service Oriented Architecture . Enables integration at diverse institutions . Allows schools to implement their practices Kuali Student – Advanced CAMP June 19-20 4 Functional Vision . Support end users by anticipating their needs . Wide range of learners and learning activities. Wide range of business processes . Easier to change business processes. Reduce time staff spend on routine task Kuali Student – Advanced CAMP June 19-20 5 Technical Vision . SOA and Web Services . SOA Design Methodology . SOA Governance . Web Services: SOAP, WSDL, XML Schema . Web Services
    [Show full text]
  • Towards Distributed Information Access Possibilities and Implementation
    Towards Distributed Information Access Possibilities and Implementation Victor de Graaff i ii Towards Distributed Information Access Alternatives and Implementation Master thesis Author: Victor de Graaff University: University of Twente Master: Computer Science Track: Software Engineering Internal Supervisors: Dr. Luís Ferreira Pires Dr. ir. Marten van Sinderen External Supervisors: ing. Gerke Stam, TSi Solutions iii iv Preface This thesis describes the results of a Master of Science assignment at the Software Engineering group at the University of Twente. This assignment has been carried out from February to November 2009 at TSi Solutions in Enschede, The Netherlands. I would like to thank all the people who gave me support while writing this thesis. In the first place these people are my girlfriend Susanne Jeschke and my daughter Melissa. They have supported me through the last piece of my Bachelor and my entire Master course by taking my mind off work every night and weekend, as far as my deadlines allowed them to. They have given me the chance to spend countless hours on my work, my classes, and later my thesis, while they went to all the activities and appointments a young child has. I can truly say that I could never have finished my studies without their support, understanding and patience. Another great influence has been the supervision of Luís Ferreira Pires, Marten van Sinderen and Gerke Stam. Luís managed to keep the balance in my work between quality and steady progress. On top of that, Luís taught me a lot on writing objective texts by rephrasing or pointing out sentences which were subjective or too popular.
    [Show full text]
  • IBM Filenet Content Manager Technology Preview: Content Services Graphql API Developer Guide
    IBM FileNet Content Manager Technology Preview: Content Services GraphQL API Developer Guide © Copyright International Business Machines Corporation 2019 Copyright Before you use this information and the product it supports, read the information in "Notices" on page 45. © Copyright International Business Machines Corporation 2019. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. © Copyright International Business Machines Corporation 2019 Contents Copyright .................................................................................................................................. 2 Abstract .................................................................................................................................... 5 Background information ............................................................................................................ 6 What is the Content Services GraphQL API? ....................................................................................... 6 How do I access the Content Services GraphQL API? .......................................................................... 6 Developer references ................................................................................................................ 7 Supported platforms ............................................................................................................................ 7 Interfaces and output types ......................................................................................................
    [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]
  • Graphql at Enterprise Scale a Principled Approach to Consolidating a Data Graph
    A Principled Approach to Consolidating a Data Graph GraphQL at Enterprise Scale A Principled Approach to Consolidating a Data Graph Jeff Hampton Michael Watson Mandi Wise GraphQL at Enterprise Scale Copyright © 2020 Apollo Graph, Inc. Published by Apollo Graph, Inc. https://www.apollographql.com/ All rights reserved. No part of this book may be reproduced in any form on by an electronic or mechanical means, including information storage and retrieval systems, without permission in writing from the publisher. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes This document is provided “as-is”. Information and views expressed in this document may change without notice. While the advice and information in this document is believed to be true and accurate at the date of publication, the publisher and the authors assume no legal responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. Revision History for the First Edition 2020-09-11: First Release 2020-10-27: Second Release 2020-12-10: Third Release 2021-04-26: Fourth Release Contents The Team v Preface vi Who Should Read this Guide . vi What You’ll Learn from this Guide . vii How to Contact Us . vii Moving Toward GraphQL Consolidation 1 Why Consolidate Your Data Graph? . 1 What Does a Consolidated Data Graph Look Like? . 8 When to Consolidate Your Data Graph . 9 Summary . 14 Graph Champions in the Enterprise 15 The Graph Champion and Graph Administration . 15 Delivering Organizational Excellence as a Graph Champion .
    [Show full text]