DOCSLIB.ORG

Simon Laws Mark Combellack Raymond Feng Haleh Mahbod Simon Nash

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Simon Laws Mark Combellack Raymond Feng Haleh Mahbod Simon Nash SAMPLE CHAPTER Simon Laws Mark Combellack Raymond Feng Haleh Mahbod Simon Nash MANNING Tuscany SCA in Action by Simon Laws, Mark Combellack, Raymond Feng, Haleh Mahbod and Simon Nash Chapter 1 Copyright 2011 Manning Publications brief contents PART 1UNDERSTANDING TUSCANY AND SCA............................ 1 1 ■ Introducing Tuscany and SCA 3 2 ■ Using SCA components 33 3 ■ SCA composite applications 71 PART 2USING TUSCANY....................................................... 107 4 ■ Service interaction patterns 109 5 ■ Implementing components using the Java language 132 6 ■ Implementing components using other technologies 175 7 ■ Connecting components using bindings 197 8 ■ Web clients and Web 2.0 232 9 ■ Data representation and transformation 257 10 ■ Defining and applying policy 284 PART 3DEPLOYING TUSCANY APPLICATIONS ........................ 309 11 ■ Running and embedding Tuscany 311 12 ■ A complete SCA application 329 PART 4EXPLORING THE TUSCANY RUNTIME ........................ 355 13 ■ Tuscany runtime architecture 357 14 ■ Extending Tuscany 382 Part 1 Understanding Tuscany and SCA Tuscany SCA In Action teaches you to use the Service Component Architec- ture (SCA) through practical examples developed using the Java SCA runtime from the Apache Tuscany open source project. This part of the book provides a broad introduction to SCA and Apache Tuscany using a travel-booking scenario. It presents an overview of Apache Tuscany and helps you to set up your environ- ment so that you can develop and run the examples in this book. This is all cov- ered in three chapters. In chapter 1, “Introducing Tuscany and SCA,” you’ll learn about the Apache Tuscany open source project and the travel-booking scenario and be introduced to SCA at a high level. By the end of this chapter, you’ll have an appreciation of SCA and will be able to run a small part of our travel-booking application. Chapter 2, “Using SCA components,” covers SCA in greater detail. You’ll gain a better understanding of SCA and use it to create more of the components that compose the travel-booking application. Chapter 3, “SCA composite applications,” covers the deployment of SCA- based applications. Here, you’ll learn about the flexible deployment model that Tuscany SCA offers and experiment with deploying the travel application in a local or distributed environment. By the end of part 1, you’ll know about Tuscany and SCA and will have built and deployed a simple travel application. Introducing Tuscany and SCA This chapter covers ■ Exploring SCA and Tuscany ■ Learning basic SCA concepts ■ Developing your first SCA application Businesses are always looking for ways to lower the cost of creating and maintaining business applications. One popular approach to business application development, often called Service Oriented Architecture (SOA), is to adopt a model where busi- ness functions are described as well-defined services that can be used to compose working applications. SOA is an attractive idea, but putting it into practice can be difficult. Business computing environments typically contain many different technologies, and the integration of these technologies can be complex. In a single application you can be joining Java objects, Business Process Execution Language (BPEL) processes, browser-based clients, and Ruby scripts using web services, as well as Java Message Service (JMS) and JSON-RPC protocols, to name but a few. 3 4 CHAPTER 1 Introducing Tuscany and SCA What’s needed is a common way to describe an assembly of distributed services regardless of the technology used to implement and connect them. Step forward the Service Component Architecture (SCA) and the Apache Tuscany project. Apache Tuscany is an open source project developed by the Apache Software Foundation. The Tuscany software is freely available from the project website (http:// tuscany.apache.org) under the Apache 2.0 License. The software is a lightweight infra- structure that implements Service Component Architecture (SCA), Service Data Objects (SDO), and Data Access Service (DAS) technologies and provides seamless integration with many other technologies. This book is about Tuscany’s Java imple- mentation of SCA, which is what we mean when we use the term Tuscany SCA. The SCA specifications are the foundation upon which Tuscany SCA is built. The first version of SCA specifications (v1.0) was developed by a consortium of companies called the Open Service Oriented Architecture (OSOA) collaboration. The specifica- tions are published via the collaboration’s website (http://www.osoa.org). These are the specifications that the Tuscany Java SCA v1.x runtime and this book use. OSOA and OASIS versions of the SCA specifications Following the release of the SCA v1.0 specifications from OSOA, the SCA specifications were donated to the OASIS Open Composite Services Architecture (CSA) Member Sec- tion (http://www.oasis-opencsa.org/). Work is ongoing at OASIS to standardize v1.1 of the SCA specifications. The Tuscany 1.x runtime and this book are based on the completed v1.0 specifications from OSOA. Appendix B covers the direction that Tus- cany 2.x is taking beyond what’s available in Tuscany 1.x. The fundamentals of what you learn about SCA in this book apply to both versions. SCA provides a technology-neutral assembly capability for composing applications from business services. The services themselves can be developed and connected using many different technologies. If you look at the Tuscany project website, you’ll find subprojects providing Java language and C++ (also known as native) implementa- tions of SCA. You’ll also find Java language and native implementations of SDO and DAS, which provide ways of handling and persisting data. SDO and DAS aren’t prereq- uisites for using SCA. Although this book concentrates on Tuscany’s Java SCA runtime, in chapter 9 we do use SDO when building SCA service interfaces. If you want to know more about SDO, DAS, or the native runtimes, then the Apache Tuscany website (http://tuscany.apache.org) is a good place to start. We’ll start this chapter by taking our first high-level look at SCA and Tuscany. Then we’ll look at how an example travel-booking application can be described using SCA. This exercise sets the scene for building and running your first SCA application in sec- tion 1.3. There are already many SOA-related technology choices out there. In the last sec- tion of this chapter we look at how Tuscany and SCA are able to integrate with and complement other popular SOA technologies. The big picture 5 The samples used in this chapter, and in the rest of this book, can be downloaded following the instructions in appendix A. The source code for the samples is available in the Tuscany project, and the samples are accompanied by a README file that describes the structure and the operation of the samples. In this chapter you’ll gain a high-level understanding of the Tuscany software and the advantages of SCA, and you’ll build your first composite application. This will get you ready to dive into the rest of the book and explore what else Tuscany SCA has to offer. 1.1 The big picture SCA uses a range of terms, some of which will sound familiar and others that are new. It’s important to appreciate what SCA means when it talks about such things as compo- nents, services, references, and composites. These terms will be used repeatedly throughout the book, so we’ll start here by giving a high-level introduction of what it means to assemble applications from SCA components and what the various parts of the resulting assembly are called. Assembly is at the core of SCA, so much so that the central SCA specification con- centrates on defining what’s called the Assembly Model. The SCA Assembly Model defines an XML language for assembling components into applications and provides the framework into which extensions are plugged to support the wide variety of imple- mentation and communication technologies that are available today. In the next sec- tions, we’ll first provide an overview of the SCA Assembly Model and then give a quick summary of how Tuscany is architected to support SCA. This will provide sufficient background for understanding the details throughout the rest of the book. 1.1.1 The basics of SCA SOA promotes the benefits of constructing large and complex enterprise systems out of well-defined and sometimes replaceable component parts called component services. SCA describes an Assembly Model for doing just that. An SCA service provides a reusable piece of business function and has a well- defined interface that identifies how it can be called to provide that function. An application broken down into a set of well-defined services significantly reduces the complexity of development as well as its long-term maintenance by isolating change and simplifying testing. The challenge then becomes how to assemble the cooperat- ing network of services to provide maximum flexibility and reuse while maintaining the integrity of each service. Figure 1.1 shows a web shopping application that uses a set of connected services to allow the user to browse a catalog, add items to a shopping cart, and then pay for the items at checkout time. Figure 1.1 demonstrates that the web shopping example is made up of services that are developed in various technologies and communicate using different protocols. This mix of technologies is typical of today’s applications. The danger with the usual approach to application development is that technology integration logic can often become intermingled with business logic. For example, we may call remote web services by using a web service provider API directly from business 6 CHAPTER 1 Introducing Tuscany and SCA Figure 1.1 A web shopping application built from cooperating services showing the typical variety of technologies use to implement and connect services logic.
Load more

Recommended publications
  • Microsoft Powerpoint
    FraSCAti ««Open SCA Platform »» Outline • From SOA to SCA • FraSCAti • SCOrWare • Conclusion 2 2 From SOA to SCA From SOA challenges… • IT architectures • Complexity • Managing 10 n lines of code • Monolithic • Breaking application «silos» • Seldom evolvable • Freeing systems from immutable dependencies Source: oasis-open.org 4 4 …to existing SOA, but… SOA leverages complexity and promotes flexibility • Loose coupling • Service composition and orchestration • Well defined and contractualized interfaces • Standard tools and technologies Source: oasis-open.org 5 5 …Still a partial solution Today's SOA need to be… • Deployable in different environments • Ensure security and reliability • Adaptable to changing business needs …and thus, SOA lack… • Structured architectures – What is behind the scene? • Reuse capabilities – Reuse the wheel when possible… • Flexibility support You want SCA! – …Or tune it if not! for your business 6 6 SCA in a Nutshell SCA (Service Component Architecture) • Aka a « Component Model for SOA » • Since 11/2005 Hosted by the Open SOA consortium • http://www.osoa.org Community connected to OASIS • http://www.oasis-opencsa.org Existing platform providers • Open Source (4) : Apache Tuscany, Newton, Fabric3, FraSCAti • Vendors (7) : IBM WebSphere FP for SOA, TIBCO ActiveMatrix, Covansys SCA Framework, Paremus, Rogue Wave HydraSCA, Oracle Fusion Middleware 7 7 SCA in a Nutshell 15 focused specifications (09/2008) + SDO to access data sources Assembly model specification (structured architectures ☺) • How to structure composite
    [Show full text]
  • Opening Plenary State of the Feather
    Opening Plenary Lars Eilebrecht V.P., Conference Planning at ASF and Lead for ApacheCon Europe 2009 State of the Feather Jim Jagielski Chairman, The Apache Software Foundation Welcome to Amsterdam Presented by The Apache Software Foundation Produced by Stone Circle Productions, Inc. Conference Program • Detailed conference program guide available as a PDF from the ApacheCon Web site – www.eu.apachecon.com • Printed Conference-at-a- Glance program available at registration desk Presentations • 4 Tracks every day starting at 9:00 • Presentation slides provided by speakers will be made available on the ApacheCon Web site during the conference Wednesday Special Events • 9:15-9:30: Jim Jagielski “State of the Feather” • 9:30-10:30: Raghu Ramakrishnan “Data Management in the Cloud” • 10:30-11:30: Arjé Cahn, Ajay Anand, Steve Loughran, and Mark Brewer “Panel: The Business of Open Source”, moderated by Sally Khudairi • 13:00-14:00: Lars Eilebrecht “Behind the Scenes of The ASF” Wednesday Special Events • 18:30-20:00: Welcome Reception and ASF 10th Anniversary Party – Celebrating a Decade of Open Source Leadership • 19:30: OpenPGP Key Signing – [email protected] – moderated by Jean-Frederic Clere Thursday Special Events • 13:00-14:00: Jim Jagielski “Sponsoring the ASF at the Corporate and Individual Level” • 17:30-18:30: James Governor “Open Sourcing The Analyst Business – Turning Prop. Knowledge Inside Out” • 18:30-20:00: “Lightning Talks”, mod. by Danese Cooper and Rich Bowen Friday Special Events • 11:30-13:00: Lars Eilebrecht, Dirk- Willem van Gulik, Jim Jagielski, Sally Khudairi, Cliff Skolnick, “Apache Pioneer's Panel – 10 years of the ASF”, mod.
    [Show full text]
  • Return of Organization Exempt from Income
    OMB No. 1545-0047 Return of Organization Exempt From Income Tax Form 990 Under section 501(c), 527, or 4947(a)(1) of the Internal Revenue Code (except black lung benefit trust or private foundation) Open to Public Department of the Treasury Internal Revenue Service The organization may have to use a copy of this return to satisfy state reporting requirements. Inspection A For the 2011 calendar year, or tax year beginning 5/1/2011 , and ending 4/30/2012 B Check if applicable: C Name of organization The Apache Software Foundation D Employer identification number Address change Doing Business As 47-0825376 Name change Number and street (or P.O. box if mail is not delivered to street address) Room/suite E Telephone number Initial return 1901 Munsey Drive (909) 374-9776 Terminated City or town, state or country, and ZIP + 4 Amended return Forest Hill MD 21050-2747 G Gross receipts $ 554,439 Application pending F Name and address of principal officer: H(a) Is this a group return for affiliates? Yes X No Jim Jagielski 1901 Munsey Drive, Forest Hill, MD 21050-2747 H(b) Are all affiliates included? Yes No I Tax-exempt status: X 501(c)(3) 501(c) ( ) (insert no.) 4947(a)(1) or 527 If "No," attach a list. (see instructions) J Website: http://www.apache.org/ H(c) Group exemption number K Form of organization: X Corporation Trust Association Other L Year of formation: 1999 M State of legal domicile: MD Part I Summary 1 Briefly describe the organization's mission or most significant activities: to provide open source software to the public that we sponsor free of charge 2 Check this box if the organization discontinued its operations or disposed of more than 25% of its net assets.
    [Show full text]
  • Apache Harmony Project Tim Ellison Geir Magnusson Jr
    The Apache Harmony Project Tim Ellison Geir Magnusson Jr. Apache Harmony Project http://harmony.apache.org TS-7820 2007 JavaOneSM Conference | Session TS-7820 | Goal of This Talk In the next 45 minutes you will... Learn about the motivations, current status, and future plans of the Apache Harmony project 2007 JavaOneSM Conference | Session TS-7820 | 2 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 3 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 4 Apache Harmony In the Beginning May 2005—founded in the Apache Incubator Primary Goals 1. Compatible, independent implementation of Java™ Platform, Standard Edition (Java SE platform) under the Apache License 2. Community-developed, modular architecture allowing sharing and independent innovation 3. Protect IP rights of ecosystem 2007 JavaOneSM Conference | Session TS-7820 | 5 Apache Harmony Early history: 2005 Broad community discussion • Technical issues • Legal and IP issues • Project governance issues Goal: Consolidation and Consensus 2007 JavaOneSM Conference | Session TS-7820 | 6 Early History Early history: 2005/2006 Initial Code Contributions • Three Virtual machines ● JCHEVM, BootVM, DRLVM • Class Libraries ● Core classes, VM interface, test cases ● Security, beans, regex, Swing, AWT ● RMI and math 2007 JavaOneSM Conference | Session TS-7820 |
    [Show full text]
  • Avaliando a Dívida Técnica Em Produtos De Código Aberto Por Meio De Estudos Experimentais
    UNIVERSIDADE FEDERAL DE GOIÁS INSTITUTO DE INFORMÁTICA IGOR RODRIGUES VIEIRA Avaliando a dívida técnica em produtos de código aberto por meio de estudos experimentais Goiânia 2014 IGOR RODRIGUES VIEIRA Avaliando a dívida técnica em produtos de código aberto por meio de estudos experimentais Dissertação apresentada ao Programa de Pós–Graduação do Instituto de Informática da Universidade Federal de Goiás, como requisito parcial para obtenção do título de Mestre em Ciência da Computação. Área de concentração: Ciência da Computação. Orientador: Prof. Dr. Auri Marcelo Rizzo Vincenzi Goiânia 2014 Ficha catalográfica elaborada automaticamente com os dados fornecidos pelo(a) autor(a), sob orientação do Sibi/UFG. Vieira, Igor Rodrigues Avaliando a dívida técnica em produtos de código aberto por meio de estudos experimentais [manuscrito] / Igor Rodrigues Vieira. - 2014. 100 f.: il. Orientador: Prof. Dr. Auri Marcelo Rizzo Vincenzi. Dissertação (Mestrado) - Universidade Federal de Goiás, Instituto de Informática (INF) , Programa de Pós-Graduação em Ciência da Computação, Goiânia, 2014. Bibliografia. Apêndice. Inclui algoritmos, lista de figuras, lista de tabelas. 1. Dívida técnica. 2. Qualidade de software. 3. Análise estática. 4. Produto de código aberto. 5. Estudo experimental. I. Vincenzi, Auri Marcelo Rizzo, orient. II. Título. Todos os direitos reservados. É proibida a reprodução total ou parcial do trabalho sem autorização da universidade, do autor e do orientador(a). Igor Rodrigues Vieira Graduado em Sistemas de Informação, pela Universidade Estadual de Goiás – UEG, com pós-graduação lato sensu em Desenvolvimento de Aplicações Web com Interfaces Ricas, pela Universidade Federal de Goiás – UFG. Foi Coordenador da Ouvidoria da UFG e, atualmente, é Analista de Tecnologia da Informação do Centro de Recursos Computacionais – CERCOMP/UFG.
    [Show full text]
  • How SOA… 26 Summary 31 Table of Contents
    Service Oriented Architecture with Java Using SOA and web services to build powerful Java applications Binildas CA Malhar Barai Vincenzo Caselli BIRMINGHAM - MUMBAI Service Oriented Architecture with Java Copyright © 2008 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, Packt Publishing, nor its dealers or distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: June 2008 Production Reference: 1180608 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-847193-21-6 www.packtpub.com Cover Image by Nik Lawrence ([email protected]) Credits Authors Project Manager Binildas CA Abhijeet Deobhakta Malhar Barai Vincenzo Caselli Project Coordinator Abhijeet Deobhakta Reviewer Shyam Sankar S Indexer Monica Ajmera Acquisition Editor Bansari Barot Proofreader Petula Wright Technical Editor Dhiraj Chandiramani Production Coordinator Shantanu Zagade Editorial Team Leader Akshara Aware Cover Work Shantanu Zagade About the Authors Malhar Barai is a senior systems analyst with Satyam Computer Services Ltd., one of India's leading IT services organizations.
    [Show full text]
  • Full-Graph-Limited-Mvn-Deps.Pdf
    org.jboss.cl.jboss-cl-2.0.9.GA org.jboss.cl.jboss-cl-parent-2.2.1.GA org.jboss.cl.jboss-classloader-N/A org.jboss.cl.jboss-classloading-vfs-N/A org.jboss.cl.jboss-classloading-N/A org.primefaces.extensions.master-pom-1.0.0 org.sonatype.mercury.mercury-mp3-1.0-alpha-1 org.primefaces.themes.overcast-${primefaces.theme.version} org.primefaces.themes.dark-hive-${primefaces.theme.version}org.primefaces.themes.humanity-${primefaces.theme.version}org.primefaces.themes.le-frog-${primefaces.theme.version} org.primefaces.themes.south-street-${primefaces.theme.version}org.primefaces.themes.sunny-${primefaces.theme.version}org.primefaces.themes.hot-sneaks-${primefaces.theme.version}org.primefaces.themes.cupertino-${primefaces.theme.version} org.primefaces.themes.trontastic-${primefaces.theme.version}org.primefaces.themes.excite-bike-${primefaces.theme.version} org.apache.maven.mercury.mercury-external-N/A org.primefaces.themes.redmond-${primefaces.theme.version}org.primefaces.themes.afterwork-${primefaces.theme.version}org.primefaces.themes.glass-x-${primefaces.theme.version}org.primefaces.themes.home-${primefaces.theme.version} org.primefaces.themes.black-tie-${primefaces.theme.version}org.primefaces.themes.eggplant-${primefaces.theme.version} org.apache.maven.mercury.mercury-repo-remote-m2-N/Aorg.apache.maven.mercury.mercury-md-sat-N/A org.primefaces.themes.ui-lightness-${primefaces.theme.version}org.primefaces.themes.midnight-${primefaces.theme.version}org.primefaces.themes.mint-choc-${primefaces.theme.version}org.primefaces.themes.afternoon-${primefaces.theme.version}org.primefaces.themes.dot-luv-${primefaces.theme.version}org.primefaces.themes.smoothness-${primefaces.theme.version}org.primefaces.themes.swanky-purse-${primefaces.theme.version}
    [Show full text]
  • Open Source SOA
    Jeff Davis MANNING Open Source SOA Licensed to Venkataramanan Tharagam <[email protected]> Licensed to Venkataramanan Tharagam <[email protected]> Open Source SOA JEFF DAVIS MANNING Greenwich (74° w. long.) Licensed to Venkataramanan Tharagam <[email protected]> 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 Greenwick, 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 percent recycled and processed without the use of elemental chlorine. Development Editor: Cynthia Kane Manning Publications Co. Copyeditor: Liz Welch Sound View Court 3B Typesetter: Krzysztof Anton Greenwich, CT 06830 Cover designer: Leslie Haimes ISBN 978-1-933988-54-2 Printed in the United States of America 12345678910–MAL–16151413111009 Licensed to Venkataramanan Tharagam <[email protected]> brief contents PART 1HISTORY AND PRINCIPLES ...........................................
    [Show full text]
  • Open Source SOA with Service Component Architecture and Apache Tuscany
    Open Source SOA with Service Component Architecture and Apache Tuscany Open Source SOA: SCA, SDO & DAS http://incubator.apache.org/Tuscany Learn how to build and deploy Composite Service Applications using Service Component Architecture (SCA) and Apache Tuscany Goal Open Source SOA: SCA, SDO & DAS 2 http://incubator.apache.org/Tuscany Agenda SCA in a Nutshell Apache Tuscany Overview Demo – Business Value Scenarios SCA Quick Tour Tuscany SCA Implementation New and Notable Tuscany Community Summary Open Source SOA: SCA, SDO & DAS 3 http://incubator.apache.org/Tuscany SCA in a Nutshell A development and deployment model for SOA Service-based models for the • Construction • Assembly • Deployment of composite service applications In a distributed and heterogeneous environment of • Multiple languages • Multiple container technologies • Multiple service access methods Open Source SOA: SCA, SDO & DAS 4 http://incubator.apache.org/Tuscany SCA Specifications - History Dec 2003: BEA and IBM start collaborating on SCA Nov 2005: 0.9 specs published • BEA, IBM, Oracle, SAP, IONA, and Sybase July 2006: 0.95 specs and OSOA.org (Open SOA) • Added: Cape Clear, Interface21, Primeton Technologies, Progress Software, Red Hat, Rogue Wave, Siemens AG, Software AG, Sun, TIBCO Mar 2007: 1.0 specs published • Submitted to OASIS April 2007: OASIS Forms Open CSA Member Section Sept 2007: Formal standardization starts in OASIS Open CSA Open Source SOA: SCA, SDO & DAS 5 http://incubator.apache.org/Tuscany Open SOA - http://www.osoa.org Open Source SOA: SCA, SDO & DAS
    [Show full text]
  • Deliverable D6.3.1
    Grant Agreement Number: 257528 KHRESMOI www.khresmoi.eu State of the art, concepts and specification for the “Early software architecture” Deliverable number D6.3.1 Dissemination level public Delivery date 10th of May 2011 Status Version 1.1 Emmanuel Jamin, Vassil Montchev, Author(s) Konstantin Pentchev, revised by Allan Hanbury This project is supported by the European Commission under the Information and Communication Technologies (ICT) Theme of the 7th Framework Programme for Research and Technological Development. D6.3.1: State of the art, Concepts, and specification of the Early Prototype Executive summary This document reports on the foundations of the architecture and integration aspects of the Khresmoi project. This includes the technical and functional requirements that imply technical choices and integration decisions for the architecture design. To provide the architecture description and the system specification, an iterative approach has been followed. The structure of the document reflects the main aspects of this approach. At first, two kinds of state of the art are presented. The first one compiles the systems that use similar technologies into four different domains (information retrieval, semantic web systems, multimedia search engines, and platforms for natural language processing). This permits to situate the technical position of the Khresmoi system and provides recommendations in terms of technical requirements. The second state of the art retraces the main technologies for the system integration. Based on this state of the art, the decision is made to adopt the SOA approach, as it offers the best features in terms of flexibility and scalability to be used in the Khresmoi system.
    [Show full text]
  • SCA and Apache Tuscany
    IBM Software Group Service Component Architecture (SCA) and Service Data Objects (SDO) Apache Tuscany: Open Source SOA Jean-Sebastien Delfino [email protected] Open Source SOA: SCA, SDO and DAS 1 http://incubator.apache.org/tuscany IBM Software Group Agenda What are SCA and SDO? SCA: Programming Model Overview Apache Tuscany: Open Source SOA Runtime Latest SCA and SDO releases and work in progress Demo Q&A Open Source SOA: SCA, SDO and DAS 2 http://incubator.apache.org/tuscany IBM Software Group What is SCA? Architectural framework for service definition, assembly, and composition Separation of implementation technology choices from business service definitions Provides a variety of protocol bindings, implementation types, interface definitions and data bindings Extensible framework for defining new protocol bindings, implementation types, interface definitions and data bindings Multiple language support Intent-based policy support for applying qualities of service An industry standard developed by 17 companies at www.osoa.org and now going through a formal standardization process at OASIS OpenCSA (www.oasis-opencsa.org) Open Source SOA: SCA, SDO and DAS 3 http://incubator.apache.org/tuscany IBM Software Group Bird View: Service Component Architecture Service Interface Reference Interface - Java Property - Java interface - WSDL - WSDL PortType Composite A property setting Component Component Service A B Reference promote wire promote Service Binding Implementation Reference Binding Web Service Java Web Service JMS BPEL JMS SLSB PHP
    [Show full text]
  • Sommaire Fl Fevrier 91
    METHODS & TOOLS Practical knowledge for the software developer, tester and project manager ISSN 1661-402X Winter 2008 (Volume 16 - number 4) www.methodsandtools.com From Finger in the Air Estimating to Finger Pointing Tracking As Giovanni Asproni says it "estimation is a fundamental activity of every project". Or at least it should be. The meaning of "estimation" varies however often for the different participants to software development projects. For the customer, "estimation" means an almost accurate amount of money he will spend and time it will need before he gets what he wants. For the project manager, it is an early commitment to the customer and from the developer to do something for a deadline. For the developer, it is the amount of time that he thinks he could do the stuff, if everything goes right. The experienced developer will often add a 50% cushion to his estimates, knowing that not everything goes right. You can have an additional meaning in the case of outsourcing. For the salesperson, the estimation is the maximum price he can ask, while still having a lot of chances to sign a deal. A lot of young engineers will remind with astonishment hearing in a pre-sales meeting a salesperson answering to the customer that everything he wants is indeed possible... and for a cheap price too ;o) For a developer, estimation is often equaled to fixing deadlines. He could then feel trapped by the original commitment that created expectations for management and customers. Customers have often two fixed expectations: delivery date and functionalities. Therefore, the effort is the only variable left to adjust the project activity.
    [Show full text]