DOCSLIB.ORG

Performance Evaluation of Enterprise Service Buses Towards Support of Service Orchestration Themba Shezi, Edgar Jembere , and Mathew Adigun the Internet

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Performance Evaluation of Enterprise Service Buses Towards Support of Service Orchestration Themba Shezi, Edgar Jembere , and Mathew Adigun the Internet International Conference on Computer Engineering and Network Security (ICCENS'2012) December 26-27, 2012 Dubai (UAE) Performance Evaluation of Enterprise Service Buses towards Support of Service Orchestration Themba Shezi, Edgar Jembere, and Mathew Adigun the Internet. In most scenarios services are combined in a Abstract- The use of Enterprise Service Bus (ESB) as the process to achieve a business objective. For defining these cornerstone for system integrations has shown improvement in many processes Web Service Business Process Execution Language aspect of business information systems, including paving a way for (WS-BPEL) is used. Service Oriented computing, reusability, business to business collaboration and standard based communication infrastructure. ESB SOA implementations that were based on only endpoints as a concept defines set of capabilities which includes message fall short of the key infrastructure to support data routing, transformation, and service orchestration. However there transformation, event handling, and durable messaging. These exist different approaches towards achieving these capabilities. There additional requirements to SOA led to what is known as is much ongoing research on architectural issues and enabling Enterprise Service Bus (ESB) [3]. technologies for ESBs, but the body of knowledge regarding service ESB is a standard based integration infrastructure that automation and orchestration schemes needs some improvements. In this work we provide comparative performance evaluation of enables heterogeneous services and applications to interact by ServiceMix, Mule and JBoss ESB regarding service orchestration. combining web service technology, messaging, intelligent The results showed that the use of Apache ODE as the orchestration routing, data transformation and service orchestration [2]. The engine gave ServiceMix an advantage over the other ESBs. industrial success of ESB technology led to many products being implemented and available as both open source and Keywords— Enterprise Service Bus, Service Oriented commercial ESBs. Selecting the ESB product that will suit all Architecture, Web Services and Service orchestration the integration needs of an organization is a challenging task because different approaches used by different products to I. INTRODUCTION achieve a certain ESB capability results to different VER the past years organizations were required to cope performances [4]. In addition no single ESB is the best in all O with rapidly changing market that includes new integration requirements, so the compromise is always needed competitive pressure and threads which required information [5]. Most of the works done to assist in ESB selection focus on systems to respond quickly to support the new business models evaluating out of the box ESB capabilities such as data and requirements. With the changes becoming more and more transformation, routing and reliable messaging. In reality to frequent, organizations moved their information systems to fit achieve a complete SOA implementation external features are in Service Oriented paradigm [1]. The use of Service Oriented required in addition to ESB. For example UDDI and BPEL Architecture (SOA) brings a number of benefits including process support. The former is useful for service discovery and cost-cutting initiatives by allowing business functions to be management, the latter enables the existing enterprise created in such a way that they can be reusable throughout the functions to be composed and reused to provide new business whole organization. In this way SOA act as a key enable for logic. Most ESBs provides add-ons for these features. effective and efficient rapid application development. SOA is As a consequence, the aim of this work is to provide an mainly driven by the use of open standards which includes evaluation of Mule, ServiceMix and JBoss ESB towards Web Service technology [2]. Web services define business support of WS-BPEL processes. More concretely the logic located anywhere and accessible through Internet contribution of this work it two fold. Firstly we showed the protocols such as HTTP. A number of standards are contained method for adding external BPEL engine to support process in the Web Service technology. They include Web Service definition and execution inside the ESB. Secondly we Definition Language (WSDL) which is an XML-based provided performance evaluation of these ESBs regarding language for defining web services, Universal Description, service orchestration scenario. Discovery and Integration (UDDI) which act as a repository for storing information about web services and SOAP which II. ESB TECHNOLOGIES defines message structure for communication exchange over ESB core capabilities are supported through a number of technologies. For web service integration Apache CXF, Axis Themba Shezi is with the Department of Computer Science and Mobile e- and JBoss web services (JBoss WS) are most commonly Services in the University of Zululand, KwaDlangezwa 3886, South Africa (e- supported technologies. As an important part of any ESB, data mail: [email protected]). transformation is supported through the use of Extensible Edgar Jembere is with the Department of Computer Science and Mobile e- Services in the University of Zululand, KwaDlangezwa 3886, South Africa (e- Stylesheet Language Transformations (XSLT) which enables mail: [email protected]). XML based message transformation. In addition XQuery and Mathew Adigun is with the Department of Computer Science and Mobile XPath are query languages used to manipulate XML data. e-Services in the University of Zululand, KwaDlangezwa 3886, South Africa Message routing is supported through Enterprise Integration (e-mail: [email protected]). 260 International Conference on Computer Engineering and Network Security (ICCENS'2012) December 26-27, 2012 Dubai (UAE) Patterns as defined in [6]. A wide variety of transport implements business logics. So to achieve a certain business protocols are supported by ESBs, these include HTTP, FTP, objective, multiple services are composed to create a process. TCP, UDP and JMS. There exist different JMS Service composition can be achieved either through service implementations which include Apache ActiveMQ, MuleMQ orchestration or choreography. Most ESBs provide API’s to and JBossMQ. To support open standards some ESBs are support BPEL standard which is the orchestration language for based on Java Business Integration (JBI) specification. In JBI defining business processes. However their performances have environment components are either Service Engines (SE) or never been evaluated. This work presents comparison of ESBs Binding Components (BC). SE contains business logic and regarding service orchestration. More concretely, we used also other features such as transformation. BC enables open source BPEL engine to provide runtime environment of connectivity to external services. At the heart of JBI is the the defined processes. Normalized Message Router (NMR) which facilitates communication between SE and BC. To support short and IV. SERVICE ORCHESTRATION AND long running business processes, most ESBs have available CHOREOGRAPHY API’s for WS-BPEL. Different orchestration engines are In Service Oriented Computing there exist two approaches supported for execution of these processes. They include Open to service composition. Service Choreography is based on ESB BPEL Engine, Apache ODE and JBoss RiftSaw Engine. collaboration, all web services participating in a composition are equal, and there is no central control of the execution. III. RELATED WORKS Participants need to know exactly when to become active and ESBs share the same philosophy as Enterprise Application who to collaborate with. On the other hand we have Service Integration (EAI) which is to provide integration of Orchestration which has central controller that coordinates heterogeneous application. However, ESB since its invention invocation of different web services. In orchestration approach has been popular due its capability of integrating infrastructure services have no information about other services and they are where concept of web service and SOA coalesce [7]. The not aware that they are participating in a process. performance of ESB products has been a focus of many Service Orchestration is the most supported approach in researchers. Ueno and Tatsuburi in [8] proposed a method that ESBs, therefore it’s the focus of this work. BPEL engines have allows performance and capacity of the ESB to be tested at been implemented to provide runtime execution of BPEL planning stage before the actual deployment. Authors used processes. The next subsection provides brief description of response time, CPU utilization and throughput as their criteria Apache ODE and Riftsaw BPEL engine. to test their model. Brener proposed modeling performance of composite application using well-known SOA/ESB scenario V. APACHE ODE AND JBOSS RIFTSAW called LoanBroker application. Author showed a method of There are a number of BPEL Engines available and they evaluating performance of each service participating in a include Apache ODE, JBoss Riftsaw, Open ESB BPEL composite application using SOPM [9]. In these works Engine, OW2 Orchestra and Petals BPEL Engine. This work performance of only one ESB is evaluated, no comparison focuses on Apache ODE and JBoss Riftsaw mainly because made with the other ESBs. Researchers have attempted to fill the ESBs under review have strong support for these engines. this
Load more

Recommended publications
  • The State of the Feather
    The State of the Feather An Overview and Year In Review of The Apache Software Foundation The Overview • Not a replacement for “Behind the Scenes...” • To appreciate where we are - • Need to understand how we got here 2 In the beginning... • There was The Apache Group • But we needed a more formal and legal entity • Thus was born: The Apache Software Foundation (April/June 1999) • A non-profit, 501(c)3 Corporation • Governed by members - member based entity 3 “Hierarchies” Development Administrative PMC Members Committers Board Contributors Officers Patchers/Buggers Members Users 4 At the start • There were only 21 members • And 2 “projects”: httpd and Concom • All servers and services were donated 5 Today... • We have 227 members... • ~54 TLPs • ~25 Incubator podlings • Tons of committers (literally) 6 The only constant... • Has been Change (and Growth!) • Over the years, the ASF has adjusted to handle the increasing “administrative” aspects of the foundation • While remaining true to our goals and our beginnings 7 Handling growth • ASF dedicated to providing the infrastructure resources needed • Volunteers supplemented by contracted out SysAdmin • Paperwork handling supplemented by contracted out SecAssist • Accounting services as needed • Using pro-bono legal services 8 Staying true • Policy still firmly in the hands of the ASF • Use outsourced help where needed – Help volunteers, not replace them – Only for administrative efforts • Infrastructure itself is a service provided by the ASF • Board/Infra/etc exists so projects and people
    [Show full text]
  • Orchestra User Guide
    Orchestra User Guide This document contains an installation and user guide for Orchestra4.9.0-M3 Orchestra Team - September 2011 - Copyright © 2010 Bull SAS - OW2 Consortium Table of Contents Introduction ....................................................................................................................... v 1. General information ........................................................................................................ 1 1.1. Orchestra Overview .............................................................................................. 1 1.2. Features list ......................................................................................................... 1 1.3. Restrictions ......................................................................................................... 1 1.4. Next steps ........................................................................................................... 2 2. Prerequisites ................................................................................................................... 3 2.1. Hardware ............................................................................................................ 3 2.2. Software ............................................................................................................. 3 3. Installation guide ............................................................................................................ 4 3.1. Web Service Frameworks .....................................................................................
    [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]
  • 7.1 Oracle Bpel Process Manager
    Institute of Architecture of Application Systems University of Stuttgart Universitätsstraße 38 D–70569 Stuttgart Diplomarbeit Nr. 2728 Fault Handling Across the Web Services Stack Pablo Fuentetaja Abad Course of Study: Computer Science Examiner: Prof. Dr. Frank Leymann Supervisor: Dipl.-Inf. Oliver Kopp Commenced: January ,14 2008 Completed: July, 15 2008 CR-Classification: C.2.0, C.2.1, C.2.2, C.2.4, D.2.11 Acknowledgments To my family and friends. Their support has helped me during the difficult moments. Without them this would have not been possible. To Prof. Dr. F. Leymann. For offer me the opportunity of developing this work in the Institut für Architektur von Anwendungssystemen. To Dipl.-Inf. O. Kopp. For his work, help, and supervision during these months. To Dipl.-Inf. Matthias Wieland. For his last supervision and comments. Abstract The Business Process Execution Language (BPEL) is an XML based language for describing business process behaviour based on Web services. The BPEL notation includes flow control, variables, concurrent execution, input and output, transaction scoping/compensation, and error handling. These processes are executed on a BPEL engine which calls and receives messages from external parties. The BPEL process is suspended or terminated if such communication fails, not providing any detailed information about the cause. The aim of this diploma thesis is the description of the different communication faults that can be found throughout the Web Services Stack, how they are reflected and describe a general concept of fault handling. Two BPEL engines are use on this thesis “Oracle BPEL Process Manager” and “Apache ODE”.
    [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]
  • Kuali Student Service System: Technical Architecture Phase 1 Recommendations
    Kuali Student Service System Technical Architecture Phase 1 Recommendations Kuali Student Service System Technical Architecture Phase 1 Recommendations December 31 2007 Kuali Student Technical Team Technical Architecture Phase 1 deliverables 2/14/2008 1 Kuali Student Service System Technical Architecture Phase 1 Recommendations Table of Contents 1 OVERVIEW ........................................................................................................................ 4 1.1 REASON FOR THE INVESTIGATION ................................................................................... 4 1.2 SCOPE OF THE INVESTIGATION ....................................................................................... 4 1.3 METHODOLOGY OF THE INVESTIGATION .......................................................................... 4 1.4 CONCLUSIONS ............................................................................................................... 5 1.5 DECISIONS THAT HAVE BEEN DELAYED ............................................................................ 6 2 STANDARDS ..................................................................................................................... 7 2.1 INTRODUCTION .............................................................................................................. 7 2.2 W3C STANDARDS .......................................................................................................... 7 2.3 OASIS STANDARDS ......................................................................................................
    [Show full text]
  • A Mediator Architecture for Context-Aware Composition in SOA
    A Mediator Architecture for Context-aware Composition in SOA Hicham Baidouri, Hatim Hafiddi, Mahmoud Nassar and Abdelaziz Kriouile IMS Team, SIME Laboratory, ENSIAS, Rabat, Morocco Keywords: Context, Ubiquitous Computing, Context-aware Service, Context-aware Composite Service, Aspect Paradigm, Context-Aware Composition, Model Driven Engineering. Abstract: The emergence of wireless technologies, intelligent mobile devices and service oriented architectures has enabled the development of the context-aware service oriented systems. This evolution has put the light on a challenging problem: how to dynamically compose services in SOA based systems to perform more complicated functionalities and provide richer user experience? As observed from the literature, several researches focus mainly on context-aware service design and modelling, but few studies have worked on the composition of this new kind of service to provide more complicated features. In this paper, we aim to present our proposal of adapting service composition by the integration of context during the composition process. This dynamic context-aware composition of services is realized through our Mediator Architecture for Context-Aware Composition (MACAC). 1 INTRODUCTION aware composition computing emphasizes more open-endedness in terms of analysis, design and Over the last few years, adaptive service implementation phases. composition has emerged as one of the most desired CACS development can profit from existing features that allow the integration and cooperation paradigms and technologies such as process between pre-existing services to bring out new orchestration language (e.g., BPEL (OASIS, 2007)) features. This process, known as contextual service and Model Driven Engineering (MDE (Favre, composition, requires from the composite services to 2004)).
    [Show full text]
  • Sc Collaborator: a Service Oriented Framework for Construction Supply Chain Collaboration and Monitoring
    SC COLLABORATOR: A SERVICE ORIENTED FRAMEWORK FOR CONSTRUCTION SUPPLY CHAIN COLLABORATION AND MONITORING A DISSERTATION SUBMITTED TO THE DEPARTMENT OF CIVIL AND ENVIRONMENTAL ENGINEERING AND THE COMMITTEE ON GRADUATE STUDIES OF STANFORD UNIVERSITY IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF DOCTOR OF PHILOSOPHY Chin Pang Cheng November 2009 © Copyright by Chin Pang Cheng 2009 All Rights Reserved ii I certify that I have read this dissertation and that, in my opinion, it is fully adequate in scope and quality as a dissertation for the degree of Doctor of Philosophy. ___________________________________ (Kincho H. Law) Principal Adviser I certify that I have read this dissertation and that, in my opinion, it is fully adequate in scope and quality as a dissertation for the degree of Doctor of Philosophy. ___________________________________ (Hans C. Bjornsson) I certify that I have read this dissertation and that, in my opinion, it is fully adequate in scope and quality as a dissertation for the degree of Doctor of Philosophy. ___________________________________ (John Haymaker) Approved for the University Committee on Graduate Studies. iii Abstract Importance of supply chain integration has been shown in many industry sectors. The construction industry is one of the least integrated among all major industries. One of the major reasons is that construction supply chains are unstable and often consist of numerous distributed members, most of which are small and medium construction companies. With the proliferation of the Internet and the current maturity of web services standards, service oriented architecture (SOA) with open source technologies is a desirable computing model to support construction supply chain integration and collaboration due to its flexibility and low cost.
    [Show full text]
  • Apache Buildr in Action a Short Intro
    Apache Buildr in Action A short intro BED 2012 Dr. Halil-Cem Gürsoy, adesso AG 29.03.12 About me ► Round about 12 Years in the IT, Development and Consulting ► Before that development in research (RNA secondary structures) ► Software Architect @ adesso AG, Dortmund ► Main focus on Java Enterprise (Spring, JEE) and integration projects > Build Management > Cloud > NoSQL / BigData ► Speaker and Author 29.03.12 2 Scala für Enterprise-Applikationen Agenda ► Why another Build System? ► A bit history ► Buildr catchwords ► Tasks ► Dependency management ► Testing ► Other languages ► Extending 3 Apache Buildr in Action – BED-Con 2012 Any aggressive Maven fanboys here? http://www.flickr.com/photos/bombardier/19428000/4 Apache Buildr in Action – BED-Con 2012 Collected quotes about Maven “Maven is such a pain in the ass” http://appwriter.com/what-if-maven-was-measured-cost-first-maven-project 5 Apache Buildr in Action – BED-Con 2012 Maven sucks... ► Convention over configuration > Inconsistent application of convention rules > High effort needed to configure ► Documentation > Which documentation? (ok, gets better) ► “Latest and greatest” plugins > Maven @now != Maven @yesterday > Not reproducible builds! ► Which Bugs are fixed in Maven 3? 6 Apache Buildr in Action – BED-Con 2012 Other buildsystems ► Ant > Still good and useful, can do everything... but XML ► Gradle > Groovy based > Easy extensible > Many plugins, supported by CI-Tools ► Simple Build Tool > In Scala for Scala (but does it for Java, too) 7 Apache Buildr in Action – BED-Con 2012 Apache
    [Show full text]
  • Programme and Challenge
    Deliverable D6.2: Adaptive Execution Infrastructure Version 1.0 – User Guide Date: Monday, 20. December 2010 Author(s): A. Tsalgatidou, G. Athanasopoulos, I. Pogkas, P. Kouki (NKUA) Dissemination level: PU WP: WP6 - Adaptive execution infrastructure Version: 1.0 Keywords: Execution Infrastructure, User Guide Description: Envision Adaptive Execution Infrastructure User Guide ICT for Environmental Services and Climate Change Adaption Small or Medium-scale Focused Research Project ENVISION (Environmental Services Infrastructure with Ontologies) Project No: 249120 Project Runtime: 01/2010 – 12/2012 Copyright ENVISION Consortium 2009-2012 Document metadata Quality assurors and contributors Quality François Tertre (BRGM), Iker Larizgoitia (UIBK) assuror(s) Contributor(s) Version history Version Date Description 0.1 5/10/2010 Initial TOC proposal. 0.2 4/11/2010 Preliminary Input. 0.3 23/11/2010 Draft version with input in most sections. 0.4 30/11/2010 1st completed internal version. 0.6 08/12/10 Version ready for internal review. Version updated according to internal review 0.7 16/12/10 comments. 0.9 20/12/10 Version approved by the technical coordinator. 1.0 22/12/2010 Version approved by the project coordinator. Copyright ENVISION Consortium 2009-2012 Page 2 / 23 Executive Summary A core component of Envision is the Execution Infrastructure, which according to the DoW [1] is responsible for supporting the execution of environmental service chains, their data-driven adaptation and the semantic-based mediation among the constituent services. These features constitute the operational core of Envision and will support the functionality of the Envision Portal. The goal of this deliverable is to - provide an overview of the features of the Envision Execution Infrastructure implemented in version 1.0 and - provide a user-guide with details on the installation and use of the Infrastructure.
    [Show full text]
  • Code Smell Prediction Employing Machine Learning Meets Emerging Java Language Constructs"
    Appendix to the paper "Code smell prediction employing machine learning meets emerging Java language constructs" Hanna Grodzicka, Michał Kawa, Zofia Łakomiak, Arkadiusz Ziobrowski, Lech Madeyski (B) The Appendix includes two tables containing the dataset used in the paper "Code smell prediction employing machine learning meets emerging Java lan- guage constructs". The first table contains information about 792 projects selected for R package reproducer [Madeyski and Kitchenham(2019)]. Projects were the base dataset for cre- ating the dataset used in the study (Table I). The second table contains information about 281 projects filtered by Java version from build tool Maven (Table II) which were directly used in the paper. TABLE I: Base projects used to create the new dataset # Orgasation Project name GitHub link Commit hash Build tool Java version 1 adobe aem-core-wcm- www.github.com/adobe/ 1d1f1d70844c9e07cd694f028e87f85d926aba94 other or lack of unknown components aem-core-wcm-components 2 adobe S3Mock www.github.com/adobe/ 5aa299c2b6d0f0fd00f8d03fda560502270afb82 MAVEN 8 S3Mock 3 alexa alexa-skills- www.github.com/alexa/ bf1e9ccc50d1f3f8408f887f70197ee288fd4bd9 MAVEN 8 kit-sdk-for- alexa-skills-kit-sdk- java for-java 4 alibaba ARouter www.github.com/alibaba/ 93b328569bbdbf75e4aa87f0ecf48c69600591b2 GRADLE unknown ARouter 5 alibaba atlas www.github.com/alibaba/ e8c7b3f1ff14b2a1df64321c6992b796cae7d732 GRADLE unknown atlas 6 alibaba canal www.github.com/alibaba/ 08167c95c767fd3c9879584c0230820a8476a7a7 MAVEN 7 canal 7 alibaba cobar www.github.com/alibaba/
    [Show full text]
  • Orchestra User Guide
    Orchestra User Guide This document contains an installation and user guide for Orchestra 4.6.0 Orchestra Team - May 2010 - Copyright © 2010 Bull SAS - OW2 Consortium Table of Contents Introduction ...................................................................................................................... iv 1. General information ........................................................................................................ 1 1.1. Orchestra Overview .............................................................................................. 1 1.2. Features list ......................................................................................................... 1 1.3. Restrictions ......................................................................................................... 1 1.4. Tooling ............................................................................................................... 2 2. Prerequisites ................................................................................................................... 3 2.1. Hardware ............................................................................................................ 3 2.2. Software ............................................................................................................. 3 3. Installation guide ............................................................................................................ 4 3.1. Web Service Frameworks .....................................................................................
    [Show full text]