1 Department of Computer Science Imperial College London CERN School of Computing (icsc), 2005 Geneva, Switzerland
2 1 Fundamental Concepts Architectures & escience example 2
3 Distributed Computing Technologies Historic Review (20 years in 5 minutes!) Fundamental Concepts Architectures & escience example CORBA (OMG) It is standards-based, vendor-neutral, and language-agnostic. Very powerful but limited however by its complicated way of utilizing the power and flexibility of the Internet. DCOM (Microsoft) Distributed Computing platform closely tied to Microsoft component efforts such as OLE, COM and ActiveX. RMI (Sun Microsystems) Java based effort which doesn t play well with other languages. The J2EE platform integrated RMI with IIOP. (W3C) Web services are more of an evolution than a revolution
4 What is a Web Service? Fundamental Concepts Architectures & escience example Definition A Web Service is a standards-based, language-agnostic software entity, that accepts specially formatted requests from other software entities on remote machines via vendor and transport neutral communication protocols, producing application specific responses. Standards based Language agnostic Formatted requests Remote machines Vendor neutral Transport neutral Application specific responses
5 Benefits of Fundamental Concepts Architectures & escience example Loosely Coupled Each service exists independently of the other services that make up the application. Individual pieces of the application to be modified without impacting unrelated areas. Ease of Integration Data is isolated between applications creating silos. Web Services act as glue between these and enable easier communications within and across organisations. Service Reuse Takes code reuse a step further. A specific function within the domain is only ever coded once and used over and over again by consuming applications.
6 Architectures The simplest Web Service System Fundamental Concepts Architectures & escience example The simplest Web service system has two participants: A service producer (provider) A service consumer (requester). The provider presents the interface and implementation of the service, and the requester uses the Web service.
7 Architectures A Service Oriented Architecture (SOA) Fundamental Concepts Architectures & escience example A more sophisticated system: A registry, acts as a broker for Web services. A provider, can publish services to the registry A consumer, can then discover services in the registry
8 e-science example Web Enabled Telescope Access Requirements Fundamental Concepts Architectures & escience example In the context of escience and observatories, there are several requirements from a distributed astronomical system. For example, different people need access to subsets of the same data, data needs to be archieved for future use, same functionality implemented using different technologies, certain authorities authorize the use of resources, others are responsible for cataloging available resources.
9 e-science example Web Enabled Telescope Access Fundamental Concepts Architectures & escience example
10 extensible Markup Language () Definition The extensible Markup Language () is a W3C recommendation for creating special-purpose markup languages that enable the structuring, description and interchange of data. A simplified subset of SGML capable of describing many different kinds of data for any imaginable application domain. It facilitates the sharing of structured text and information in databases and across the Internet. Languages based on are themselves described in a formal way, allowing programs to modify and validate documents in these languages without prior knowledge of their form. Separate syntax from semantics. Inherently supports internationalization (Unicode) and platform independence.
11 Building Blocks Elements The pairing of a start tag and an end tag. Attributes A name-value pair that is part of a starting tag of an Element. Processing Instructions Special directives to the application that will process the document. Comments Messages helping a human reader understand the source code. Character Data Characters (in a specific encoding) Entities Whitespace
12 Elements Formal Definition & Rules Definition The term element is a technical name for the pairing of a start tag and an end tag in an Document. Production Rule element ::= EmptyElement STag content ETag STag ::= < Name Attribute > ETag ::= </ Name > EmptyElement ::= < Name Attribute /> Elements must be strictly nested! Element names can include letters, the underscore, hyphen and colon; they must begin with a letter. Element names are case sensitive!
13 Elements Some right & wrong examples Example <!-- Example 1: Element with two tags --> <message> Welcome! </message> <!-- Example 2: Empty Element (Single tag) --> <message/> Wrong Examples <!-- Example 1: Incorrect Nesting --> <ATag><BTag> Nesting Problem </ATag></BTag> <!-- Example 2: Invalid Element name --> <.wrong.element> some text </.wrong.element>
14 Attributes Formal Definition & Rules Definition The term attribute(s) refers to a theoretically arbitrary number of name-value pairs that can be included in the starting tag of an element. Production Rule STag ::= < TagName Attribute > Attribute ::= AttrName = Value The value part of the attribute has to be quoted. Attribute names starting with xml:are reserved by the specification. Example <!-- Single attribute --> <yacht length="60f"/>
15 Processing Instructions Definition, Rule & Example Definition A special directive to the applications processing the documents. Production Rule PI ::= <? PITarget...?> Example <!-- Example: A popular one! --> <?xml version="1.0" encoding="utf-8"?> The PI Target keyword is meaningful to the processing application and hence could be different between applications. Everything between the PI Target and the closing question mark is considered the contents of the processing instruction.
16 Comments & Character Data Definition, Rule & Example Comment A message that helps the human reader understand the program and the processing that takes place at a particular point of the source code. Production Rule Comment ::= <!-- Char --> Character Data Encoding: All characters in an document must comply with the document s encoding; those outside the encoding must be escaped and are called character references. Whitespace: Whitespace can be treated as either significant or insignificant. Most applications care little about whitespace. Entities: Like character references, they are predefined escape sequences that map to specific characters.
17 An Document Putting it all together! <?xml version="1.0" encoding="utf-8"?> <message from="yiannis" to="family"> <text>hey, I m at the icsc! </text> <!-- Attachment is optional --> <attachment> <desc>photo from Geneva</desc> <item> <?BinaryDataStart?> <?BinaryDataEnd?> </item> </attachment> </message> An Document consists of: But... Optional prolog A root element Comments Processing Instructions
18 Some Problems And how we solved them! The problems in the previous example relate with the: Physical Structure of the document Well formedness (Parsers) Logical Structure of the document Validity (Schemas). Semantics of the elements? Element Name clashes between Documents Namespaces
19 Namespaces Motivating the Problem Solve the problem of recognition and collision of elements in an Document. Recognition How does an processing application distinguish between the elements that describe the message and the elements that are part of a Purchase Order? Collision Does the element description refer to attachment descriptions in messages or order item descriptions? Does the item element refer to an item of attachment or an order item?
20 Namespaces Detailing the Solution Namespaces uses Uniform Resource Identifiers for uniquely qualifying local names. As URIs can be long and typically contain characters that arent allowed in element names, the process of including namespaces in document involved two steps: A namespace identifier is associated with a prefix, a name that contains only legal element name characters with the exception of the colon (;) Qualified names are obtained as a combination of the prefix, the colon character, and the local element name Qualified Name = Namespace Identifier + Local Name
22 Namespaces A couple more last things Default Namespaces Adding a prefix to every element in the document decreases readability and increases document size. Therefore, Namespaces allow us to use a default namespace in a document. Elements belonging to the default namespace don t require prefixes. Namespace prefixed attributes Attributes can also have namespaces associated with them. The desire to extend the information provided by an element without having to make changes directly to its document type.
23 Schema An Schema enables the following: Identification of the elements that can be in a document Identification of the order and relation between elements Identification of the attributes of every element and whether they re optional or required or have some other special properties Identification of the datatype of attribute content Think of it as an elaborate UML Class diagram where classes only have field and no methods.
24 Simple Object Access Protocol () What s the big deal? Definition is an industry accepted W3C specification for a ubiquitous distributed computing infrastructure. A mechanism for defining the unit of communication. A mechanism for error handling. An extensibility mechanism Lives above the transport layer of OSI Simply put its a mechanism that allows the transmission of documents, regardless of transport layer protocol.
25 Messages Logical & Physical Structure The root element of a message is the Envelope element. It contains an optional Header element and the required Body Elements called Faults can be used to describe exceptional situations. It can contain optional Attachments in MIME encoding for exchanging binary data.
26 Example Structure of a real Message <?xml version="1.0" encoding="utf-8"?> <soap:envelope soap:encodingstyle="http://soap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/schema" xmlns:soap="http://xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/schema-inst"> <soap:header> <!-- Transactions, priorites, etc. --> </soap:header> <soap:body> <!-- Some content --> </soap:body> </soap:envelope>
27 Message Transmission Message delivery path using Intermediaries The Message Transmission involves three main roles: The Sender creates and sends a Message to an ultimate Receiver. One or more optional Intermediaries can be positioned to intercept messages between the the sender and the receiver. They can perform filtering, logging, catching etc. The sender s intended destination is called the Ultimate Receiver.
28 Description Language () Description Language () is an format for describing all the information needed to invoke and communicate with a Web Service. It gives the answers to the questions Who? What? Where? Why? How? A service description has two major components: Functional Description Defines details of how the Web Service is invoked, where it s invoked. Focuses on the details of the syntax of the message and how to configure the network protocols to deliver the message. Nonfunctional Description Provides other details tha are secondary to the message (such as security policy) but instruct the requestor s runtime environment to include additional headers.
29 Document Structure The 6 basic building blocks A Document is a set of definitions with a single root element. Services can be defined using the following elements: Types, think Data Type Message, think Methods PortType, think Interfaces Binding, think Encoding Scheme Port, think URL Service, many URLs
30 PortType Element Definition and Usage Definition The porttype element describes the interface to a Web Service A Document can contain zero or more porttype A porttype element contains a single name attribute. Naming convention nameofwebservice PortType A porttype contains one or more operation elements, with a name attribute can contain input, output and fault elements
31 PortType Element Example Example <!-- Port Type Definition Example --> <porttype name="weathercheckporttype"> <operation name="checktemperature"> <input message="checktemperaturerequest"/> <output message="checktemperatureresponse"/> </operation> <operation name="checkhumidity"> <input message="checkhumidityrequest"/> <output message="checkhumidityresponse"/> </operation> </porttype>
32 Message Element Definition and Usage Definition A message is a collection of parts; intuitively a part is a named argument with its type. A message is a collection of these parts. A document can contain zero or more message elements. Each message element can be used as an input, output or fault message within an operation. The type attribute of part can be any standard data type from the XSD Schema or a user defined one.
34 Types Element Definition and Usage Definition Custom user data types defined in an abstract way. The default type system in is the Schema (XSD) A document can have at most one types element. The types element can contain simpletype or complextype. At the lowest level elements intuitively named (again!) element are defined with a name and a type attribute. NOTE! The diagram bellow is incomplete! This is considered an advanced topic and for more information you should look at data modelling using the Schema.
35 Types Element Example Example <!-- Type Definitions --> <types> <xsd:schema targetnamespace="http://weather.com/ns" xmlns:xsd="http://www.w3.org/2001/schema"> <xsd:complextype name="humiditytype"> <xsd:sequence> <xsd:element name="loc" type="xsd:string"> <xsd:element name="humd" type="xsd:double"> <xsd:element name="temp" type="xsd:double"> </xsd:sequence> </xsd:complextype> </xsd:schema> </types>
36 Binding Element Definition and Usage Definition The binding element specifies to the service requester how to format the message in a protocol-specific manner. Each porttype can have one or more binding elements associated with it. For a given porttype the binding element has to specify an messaging and transport pair. (/HTTP, /SMTP, etc).
38 Port Element Definition, Usage & Example Definition The port element specifies the network address of the endpoint hosting the Web Service. It associates a single protocol-specific address to an individual binding element. Ports are named and must be unique within the document. Example <port name="weathercheck" binding="wc:weathercheckbinding"> <soap:address location="http://host/weathercheck"/> </port>
39 Service Element Definition and Usage Definition The service element is a collection of related port elements identified by a single service name. A Document is allowed to contain multiple service elements, but conventionally contains a single one. Each service must be uniquely named. The naming convention is GeneralInfoService
40 Service Element Example Example <!-- Service definition --> <service name="weathercheckservice"> <port name="weathercheck" binding="wc:weathercheckbinding"> <soap:address location="http://host/weathercheck"/> </port> <port name="weatherchecksmtp" binding="wc:weatherchecksmtpbinding"> <soap:address location="http://host/weathercheck"/> </port> </service>
41 Concluding Remarks In this first lecture we saw the position of within the Distributed Computing Environment. the primitives and touched upon Namespaces and Schemas. how is used for transferring platform and language independent messages between software entities on different hosts. how to describe using....now...go FOR COFFEE!
(WS) Adomas Svirskas Agenda Background and the need for WS SOAP the first Internet-ready RPC Basic Web Services Advanced Web Services Case Studies The ebxml framework How do I use/develop Web Services?
Service Oriented Architecture Charlie Abela Department of Artificial Intelligence firstname.lastname@example.org Last Lecture Web Ontology Language Problems? CSA 3210 Service Oriented Architecture 2 Lecture Outline
T-110.5140 Network Application Frameworks and XML Web Services and WSDL 15.2.2010 Tancred Lindholm Based on slides by Sasu Tarkoma and Pekka Nikander 1 of 20 Contents Short review of XML & related specs
Internationalization and Web Services 25 th Internationalization and Unicode Conference Presented by Addison P. Phillips Director, Globalization Architecture webmethods, Inc. 25 th Internationalization
Integration of Hotel Property Management Systems (HPMS) with Global Internet Reservation Systems If company want to be competitive on global market nowadays, it have to be persistent on Internet. If we
SUB CODE:IT0407 SUB NAME:INTEGRATIVE PROGRAMMING & TECHNOLOGIES SEM : VII N.J.Subashini Assistant Professor,(Sr. G) SRM University, Kattankulathur 12/26/2012 1 UNIT V 12/26/2012 2 UNIT 5 WEB SERVICES ARCHITECTURE
Grid Computing Web s Fall 2006 The Grid: Core Technologies Maozhen Li, Mark Baker John Wiley & Sons; 2005, ISBN 0-470-09417-6 Web s Based on Oriented Architecture (SOA) Clients : requestors Servers : s
Research on the Model of Enterprise Integration with Web Services XIN JIN School of Information, Central University of Finance& Economics, Beijing, 100081 China Abstract: - In order to improve business
SOAP - A SECURE AND RELIABLE CLIENT-SERVER COMMUNICATION FRAMEWORK Marin Lungu, Dan Ovidiu Andrei, Lucian - Florentin Barbulescu University of Craiova, Faculty of Automation, Computers and Electronics,
4. Concepts and Technologies for B2C, B2E, and B2B Transaction 4.4 Exchanging Information within Open Business Communities 4.4.1 Pre-Internet B2B standards: EDI, Interactive EDI, Universal EDI, OpenEDI
Ambientes de Desenvolvimento Avançados http://www.dei.isep.ipp.pt/~jtavares/adav/adav.htm Aula 18 Engenharia Informática 2006/2007 José António Tavares email@example.com 1 Web services standards 2 1 Antes
Sections 9.1 & 9.2 Corba & DCOM John P. Daigle Department of Computer Science Georgia State University 05.16.06 Outline 1 Introduction 2 CORBA Overview Communication Processes Naming Other Design Concerns
Service Computing: Basics Monica Scannapieco Generalities: Defining a Service Services are self-describing, open components that support rapid, low-cost composition of distributed applications. Since services
Emerging Technologies Shaping the Future of Data Warehouses & Business Intelligence Service Oriented Architecture SOA and Web Services John O Brien President and Executive Architect Zukeran Technologies
What is a Web service? Many people and companies have debated the exact definition of Web services. At a minimum, however, a Web service is any piece of software that makes itself available over the Internet
A Service Oriented Architecture Supporting Data Interoperability for Payments Card Processing Systems Joseph M. Bugajski 1, Robert L. Grossman 2, and Steve Vejcik 2, 1 Visa International, P.O. Box 8999,
Embedded Web Services: Making Sense out of Diverse Sensors Introduction David E. Culler Gilman Tolle Arch Rock Corporation How many times have you heard, I just want to connect a collection of different
XML: extensible Markup Language Anabel Fraga Table of Contents Historic Introduction XML vs. HTML XML Characteristics HTML Document XML Document XML General Rules Well Formed and Valid Documents Elements
Web Service Description Language (WSDL) References 1. Grid Computing, Joshy Joseph, Craig Fellenstein, Pearson Education 2. Web Services, Alonso, Springer Web Service Description Language (WSDL) WSDL was
Adapted from: "Web Services: Principles and Technology" by Michael P. Papazoglou Pearson - Prentice Hall, July 2007 Web services: WSDL Web Service Description Language Compositional, Business Processing
Developing a Web Service Based Application for Mobile Client Ting Wu Pin Zheng Supervisor & Examiner Associate Prof. Vladimir Vlassov KTH/ICT/ECS Master of Science Thesis Stockholm, Sweden 2006 ICT/ECS-2006-138
Business Object Document (BOD) Message Architecture for OAGIS Release 9.+ an OAGi White Paper Document #20110408V1.0 Open standards that open markets TM Open Applications Group, Incorporated OAGi A consortium
March 2011 Contents 1 Oracle Service Bus Examples... 2 2 Introduction to the Oracle Service Bus Tutorials... 5 3 Getting Started with the Oracle Service Bus Tutorials... 12 4 Tutorial 1. Routing a Loan
BMC Software Inc. Technical Disclosure Publication Document Application Integration Manager (AIM) Author Vincent J. Kowalski Posted: June 2009 Overview This document describes an invention, the Application
Institut für Architektur von Anwendungssystemen Universität Stuttgart Universitätsstraße 38 D-70569 Stuttgart Diplomarbeit Nr. 3275 Web Services for Human Interaction Lina Sun Course of Study: Informatik
A Guide to Creating C++ Web Services WHITE PAPER Abstract This whitepaper provides an introduction to creating C++ Web services and focuses on:» Challenges involved in integrating C++ applications with
Middleware and the Internet Example: Shopping Middleware today Designed for special purposes (e.g. DCOM) or with overloaded specification (e.g. CORBA) Specifying own protocols integration in real world
MC7502 SERVICE ORIENTED ARCHITECTURE UNIT I : SOABASICS Part A 1. What is Service Oriented Architecture? Service oriented architecture is essentially a collection of services. These services communicate
Web Services Description Language (WSDL) Version 1.2 Web Services Description Language (WSDL) Version 1.2 W3C Working Draft 3 March 2003 This version: http://www.w3.org/tr/2003/wd-wsdl12-20030303 Latest
SW501 501: : Introduction to Web Services with IBM Rational Application Developer V6 Course description Introduction to Web Services Development with IBM Rational Application Developer V6 Duration: 2 Days
A standards-based approach to application integration An introduction to IBM s WebSphere ESB product Jim MacNair Senior Consulting IT Specialist Macnair@us.ibm.com Copyright IBM Corporation 2005. All rights
EAI OVERVIEW OF ENTERPRISE APPLICATION INTEGRATION CONCEPTS AND ARCHITECTURES Peter R. Egli INDIGOO.COM 1/16 Contents 1. EAI versus SOA versus ESB 2. EAI 3. SOA 4. ESB 5. N-tier enterprise architecture
Exploiting peer group concept for adaptive and highly available services Muhammad Asif Jan Centre for European Nuclear Research (CERN) Switzerland Fahd Ali Zahid, Mohammad Moazam Fraz Foundation University,
Iowa Immunization Registry Information System (IRIS) Web Services Data Exchange Setup Version 1.1 Last Updated: April 14, 2014 Table of Contents SSL Certificate Creation... 3 Option 1: Complete the Provider
1 OTM and SOA Mark Hagan Principal Software Engineer Oracle Product Development Content What is SOA? What is Web Services Security? Web Services Security in OTM Futures 3 PARADIGM 4 Content What is SOA?
CSI 3140 WWW Structures, Techniques and Standards Web Services: JAX-RPC, WSDL, XML Schema, and SOAP Web Services Concepts A web application uses Web technologies to provide functionality to an end user
A Technical How-to Guide for Creating Components and Web Services in Rational Rapid Developer June, 2003 Rev. 1.00 IBM Rational Rapid Developer Glenn A. Webster Staff Technical Writer Executive Summary
Introduction to WebSphere Process Server and WebSphere Enterprise Service Bus Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 4.0.3 Unit objectives
Page 1 de 9 What Is the Java TM 2 Platform, Enterprise Edition? This document provides an introduction to the features and benefits of the Java 2 platform, Enterprise Edition. Overview Enterprises today
Architectures Computing & 2009-11-06 Architectures Computing & SERVICE-ORIENTED COMPUTING (SOC) A new computing paradigm revolving around the concept of software as a service Assumes that entire systems
Principles and Foundations of Web Services: An Holistic View (Technologies, Business Drivers, Models, Architectures and Standards) Michael P. Papazoglou (INFOLAB/CRISM, Tilburg University, The Netherlands)
About the tutorial Tutorial Simply Easy Learning 2 About the tutorial DTD Tutorial XML Document Type Declaration commonly known as DTD is a way to describe precisely the XML language. DTDs check the validity
3. XML Namespaces 3-1 Chapter 3: XML Namespaces References: Tim Bray, Dave Hollander, Andrew Layman: Namespaces in XML. W3C Recommendation, World Wide Web Consortium, Jan 14, 1999. [http://www.w3.org/tr/1999/rec-xml-names-19990114],
The presentation explains how to create and access the web services using the user interface. Page 1 of 14 The aim of this presentation is to familiarize you with the processes of creating and accessing
Departament d Arquitectura de Computadors Invocación remota (based on M. L. Liu Distributed Computing -- Concepts and Application http://www.csc.calpoly.edu/~mliu/book/index.html) Local Objects vs. Distributed
The Enterprise Service Bus: Making Service-Oriented Architecture Real M.T. Schmidt et al. Presented by: Mikael Fernandus Simalango SOA in Early Days Introduction Service Requester bind find Service Registry
Part I EAI: Foundations, Concepts, and Architectures 5 Example: Mail-order Company Mail order Company IS Invoicing Windows, standard software IS Order Processing Linux, C++, Oracle IS Accounts Receivable
Introduction to Testing Webservices Author: Vinod R Patil Abstract Internet revolutionized the way information/data is made available to general public or business partners. Web services complement this
Web services (WS) Outline Intro on Middleware SOAP, HTTP binding WSDL UDDI Development tools References 2 Programming Trends Programming languages and software system evolve towards: higher levels of abstraction
WhitePaper Web services: Benefits, challenges, and a unique, visual development solution Altova, Inc. l 900 Cummings Center, Suite 314-T l Beverly, MA, 01915-6181, USA l Tel: 978-816-1600 l Fax: 978-816-1606
An Introduction to J2EE by Mark Johnson The Java 2, Enterprise Edition (J2EE) platform has been a global market-leading enterprise platform for the past several years. But like any large technology, J2EE
ARI The Bulletin of the Istanbul Technical University VOLUME 54, NUMBER 2 Communicated by Sondan Durukanoğlu Feyiz An XML Based Data Exchange Model for Power System Studies Hasan Dağ Department of Electrical
Extensible Markup Language (XML): Essentials for Climatologists Alexander V. Besprozvannykh CCl OPAG 1 Implementation/Coordination Team The purpose of this material is to give basic knowledge about XML
Web Services Description Language (WSDL) Version 1.2 Part 1: Core Language Web Services Description Language (WSDL) Version 1.2 Part 1: Core Language W3C Working Draft 11 June 2003 This version: http://www.w3.org/tr/2003/wd-wsdl12-20030611
Oracle Service Bus Situation A service oriented architecture must be flexible for changing interfaces, transport protocols and server locations - service clients have to be decoupled from their implementation.
VIRTUAL LABORATORY: MULTI-STYLE CODE EDITOR Andrey V.Lyamin, State University of IT, Mechanics and Optics St. Petersburg, Russia Oleg E.Vashenkov, State University of IT, Mechanics and Optics, St.Petersburg,
Middleware and the Internet Middleware today Designed for special purposes (e.g. DCOM) or with overloaded specification (e.g. CORBA) Specifying own protocols integration in real world network? Non-performant
Web Services Technologies: State of the Art Definitions, Standards, Case Study W O R K I N G P A P E R A B D A L D H E M A L B R E S H N E, P A T R I K F U H R E R, JACQUE S P A S Q U I E R September 2009
NAI Labs #0768 Architecture of a Distributed Object Firewall Proxy July 16, 2000 Gary Lamperillo Gary_Lamperillo@NAI.com NAI Labs - The Security Research Division Network Associates 3415 S. Sepulveda Blvd.
Software Engineering, Lecture 4 Decomposition into suitable parts Cross cutting concerns Design patterns I will also give an example scenario that you are supposed to analyse and make synthesis from The
Page 1 of 5 Developing Java Web Services Hands On 35 Hours Online 5 Days In-Classroom A comprehensive look at the state of the art in developing interoperable web services on the Java EE platform. Students
Distributed Objects and Components Introduction This essay will identify the differences between objects and components and what it means for a component to be distributed. It will also examine the Java
Paper TS07 Using Web Services to exchange information via XML Edward Foster, Oxford Pharmaceutical Sciences, UK ABSTRACT Web Services have evolved over the past 4 years and are a key component of Service
WEB SERVICES Revised 9/29/2015 This Page Intentionally Left Blank Table of Contents Web Services using WebLogic... 1 Developing Web Services on WebSphere... 2 Developing RESTful Services in Java v1.1...
Table of Contents Introduction Audience At Course Completion Prerequisites Certified Professional Exams Student Materials Course Outline Introduction J-410, Deploying Java Web Services introduces the next
Protocols and Architecture 1 Protocol Architecture Layered structure of hardware and software that supports the exchange of data between systems as well as a distributed application (e.g. email or file
Common definitions and specifications for OMA REST interfaces Candidate Version 1.0 11 Jan 2011 Open Mobile Alliance OMA-TS-REST_Common-V1_0-20110111-C OMA-TS-REST_Common-V1_0-20110111-C Page 2 (20) Use
Introduction to CORBA 1. Introduction 2. Distributed Systems: Notions 3. Middleware 4. CORBA Architecture 1. Introduction CORBA is defined by the OMG The OMG: -Founded in 1989 by eight companies as a non-profit
Cloud Computing & Service Oriented Architecture An Overview Sumantra Sarkar Georgia State University Robinson College of Business November 29 & 30, 2010 MBA 8125 Fall 2010 Agenda Cloud Computing Definition
SOFT 437 Software Performance Analysis Ch 5:Web Applications and Other Distributed Systems Outline Overview of Web applications, distributed object technologies, and the important considerations for SPE
Oracle Service Bus User Guide 10g Release 3 Maintenance Pack 1 (10.3.1) June 2009 Oracle Service Bus User Guide, 10g Release 3 Maintenance Pack 1 (10.3.1) Copyright 2007, 2008, Oracle and/or its affiliates.
Terminology A local area network (LAN) is a computer network covering a small physical area, like a home, office, or small group of buildings, such as a school, or an airport. The defining characteristics
BASI DI DATI II 2 modulo Parte II: XML e namespaces Prof. Riccardo Torlone Università Roma Tre Outline What is XML, in particular in relation to HTML The XML data model and its textual representation The
Enterprise Application Designs In Relation to ERP and SOA DESIGNING ENTERPRICE APPLICATIONS HASITH D. YAGGAHAVITA 20 th MAY 2009 Table of Content 1 Introduction... 3 2 Patterns for Service Integration...