Naming & Design Requirements (NDR)
|
|
- Bryan Wilkins
- 6 years ago
- Views:
Transcription
1 The Standards Based Integration Company Systems Integration Specialists Company, Inc. Naming & Design Requirements (NDR) CIM University San Francisco October 11, 2010 Margaret Goodrich, Manager, Systems Engineering SISCO, Inc ½ Mile Road Sterling Heights, MI USA Tel: Fax: Topics: Purpose System Context Notation and Terminology Mappings References Edits and Change Requests 2
2 Purpose NDR will be coming out WG 19 IEC Currently in CD form Describes Mapping from CIM Profiles to W3C XML Schemas Mapping Facilitates Information Exchange of XML Documents with IEC CIM Semantics and W3C XML Schema Syntax. Define the rules needed to create XSDs that comply with both W3C and UN/CEFACT specifications 3 System Context & Profile Definition Map Contextual Model or CIM Profile to W3C XML Schema Contextual Model Concept is Borrowed From UN/CEFACT In CIM, Contextual Model is Referred to as a CIM profile or, more simply, a Profile A Profile is a Restricted Subset of the CIM A Profile is used to define the semantics of a single type of message encoded in XML Mapping Determines: A single, standalone XML schema (XSD) for a given contextual model (profile). Indirectly, the syntax of the instance XML documents to be exchanged. The relationship between definitions in the XML schema and definitions in the contextual model. Indirectly, the relationship between elements in the XML documents exchanged and the definitions in the CIM. 4
3 Notation and Termination Provides Definitions for the following Contextual Model Concepts: Classes: Structured, Concrete, Abstract, Root, Anonymous, Compound, and Enumeration Types: Simple and Basic; Quantity (as a simple type) Union: union members are structured classes Properties: Object, By-Reference, Compound and Simple SuperClass, Subclass, Categorized Documentation, Stereotype and Documentation XML Schema Mappings Use XML Representation Summary Notation Notation consists of an XML Schema construct with the following conventions (not all are listed here): Mandatory attributes are shown in bold, e.g. count Optional attributes are shown in standard, e.g. size Literal attribute values are shown in italics e.g. medium 5 Mappings A single CIM profile is mapped to a single XML Schema with the following form: <xs:schema targetnamespace = namespace-uri elementformdefault = qualified attributeformdefault = unqualified version = version-string > Content: (annotation, envelope-elem, envelope-type, (complex-type simple-type enum-type)*) </xs:schema> The envelope-elem is the single top-level element definition in the schema, as follows: <xs:element name= envelope-name type= envelope-name> </xs:element> 6
4 Mappings The envelope-type is the type definition for the envelope as follows: <xs:complextype name = envelope-name> <xs:sequence> Content: (root-elem*) </xs:sequence> </xs:complextype> Each root-elem is defined as follows: <xs:element name = root-name type = root-name minoccurs = min maxoccurs = max> </xs:element> 7 Mappings Each abstract or concrete class in the profile, including each root class, and each compound class is mapped to a complex-type definition as follows: <xs:complextype name = class-name abstract = abstract-value sawsdl:modelreference = class-ref> Content: (annotation, (whole-class derived-class)) </xs:complextype> 8
5 References Normative References Extensible Markup Language (XML) 1.1 (Second Edition)W3C Recommendation 16 August 2006 Namespaces in XML 1.1 (Second Edition) W3C Recommendation 16 August 2006 XML Schema Part 1: Structures Second Edition W3C Recommendation 28 October 2004 XML Schema Part 2: Datatypes Second Edition W3C Recommendation 28 October 2004 Semantic Annotations for WSDL and XML Schema W3C Recommendation 28 August 2007 Non-Normative References OWL Web Ontology Language Reference W3C Recommendation 10 February 2004 Unified Modeling Language (UML) Specification V2.2, Object Management Group UN/CEFACT XML Naming and Design Rules Version 3.0 Implementation Verification, 30 January Edits and Change Requests R06.1, R06.2 & R06.3 R06.1 provides for some general edits that are proposed R06.2 adds all changes from R06.1 plus DataTypes as a Structured Class R06.3 adds all changes from R0.1 and R06.2 plus the DataType Class Property 10
6 The Standards Based Integration Company Systems Integration Specialists Company, Inc : ESB Implementation Profile CIM University San Francisco October 11, 2010 Margaret Goodrich, Manager, Systems Engineering SISCO, Inc ½ Mile Road Sterling Heights, MI USA Tel: Fax: Introduction Scope/Purpose Some Definitions Use Case Sequence Diagrams Integration Patterns Message Flows 12
7 Scope/Purpose To Define an Implementation Profile for integration using an ESB that supports both JMS and Web Services. This standard defines how message payloads are conveyed using Web Services and the Java Message Service (JMS) The Goal is to provide sufficient information to enable implementations to be interoperable. Will be used as an integral part of the interoperability tests for distribution management systems in 2009 and beyond. 13 Some Definitions Enterprise Service Bus (ESB) refers to a software architecture construct that provides foundational services via an event-driven and standards-based messaging engine. Java Message Service (JMS) - is an API that supports request/reply, publish/subscribe, and point-to-point messaging patterns. Service Oriented Architecture (SOA) is an architectural style for creating and using business processes, packaged as services. Simple Object Access Protocol (SOAP) is a standard that defines the formatting of XML messages and serves as a foundation layer of the Web Services Protocol stack. 14
8 Some Definitions - Continued Web Services Definition Language (WSDL) is an XML-based language that is used to describe Web Services. WSDL is used in combination with SOAP or XML schema to provide Web Services over the internet. XML Schema is one of several XML schema languages. Provides a set of rules to which an XML document must conform in order to be considered valid. An XML Schema instance is an XML Schema Definition (XSD). 15 Some Definitions - Continued JMS Elements: JMS Provider an implementation of the JMS interface for Message Oriented Middleware (MOM) JMS Client an application or process that produces and/or receives messages JMS Producer A JMS Client that creates and send messages JMS Consumer A JMS Client that receives messages JMS Message An object that contains the data being transferred between JMS clients. 16
9 Some Definitions - Continued JMS Elements - Continued: JMS Queue Staging area for message that have been sent and are waiting to be read. Messages are delivered in the order sent. A message is removed once it is read. JMS Topic A distribution mechanism for publishing messages that are delivered to multiple subscribers. 17 Some Definitions - Continued Differences and Similarities between JMS Topics and JMS Queues: Topics are used when the destination of a message is potentially more than one process Queues are used when the destination of a message is at most one process Topics and Queues are organized and named hierarchically Except for the use of a durable subscription, a process can only receive a copy of a message published to a topic if it is running and has an active subscription Message published to queues will remain on the queue until de-queued by a receiving process 18
10 Use Case Sequence Diagrams The document describes several use cases related to the interactions between components with a set of systems. Use Cases presented are from the perspective of the integration of systems; that is, the actors are defined in terms of the software systems that need to interact: (1) Client; (2) Server; (3) ESB, and; (4) Adapter Use Cases are described using Sequence Diagrams Three key terms related to messaging are request, reply and event and are reflected in terms of the verbs used to define the information flows. 19 Sequence Diagrams Request/Reply Client makes query request & server returns a set of objects Client makes a transaction request & server creates or modifies a set of objects Request uses get, create, update, delete, close or cancel as the verbs. 20
11 Sequence Diagrams Request/Reply w/esb Client processes can subscribe to listen for events Events use past tense verbs: (1) created; (2) updated; (3) deleted; (4) cancelled, and; (5) closed 21 Sequence Diagrams Events ESB decouples client from server Client does not have to know the location of the server or conform to the exact interface since the ESB completes the transformation Routing and mapping takes place in the integration layer 22
12 Sequence Diagrams Transactions Typically a combination of a request/reply for a message exchange with a consequential publication of events Requests related to transactions use the verbs: (1) create; (2) update; (3) delete; (4) cancel, and; (5) close 23 Sequence Diagrams Middleware Adapters When a System cannot directly connect to an ESB, an adapter is used to handle the connection. The system may be a database or a file directory. Adapter can generate events on behalf of the system 24
13 Sequence Diagrams Complex Messaging Used when a request involves many asynchronous replies to return information as it becomes available. Results are returned in the form of asynchronous events. These messages may take significant time to obtain results. 25 Sequence Diagrams Application Level Application-level messages are defined in the form of VERB(Noun) Verbs are Get, Reply, Create and Created Nouns are MeterReading and EndDeviceControls 26
14 Sequence Diagrams Application Level w/synchronous Replies For Synchronous Request/Reply message, the REPLY messages are assumed to be immediately returned. 27 Integration Patterns Four basic integration patterns are provided: Synchronous request/reply using Web Service Interface Synchronous request/reply using JMS Messages Asynchronous request/reply using JMS Messages Publish/Subscribe where the client is listening for JMS Messages referred to as events or notifications These patterns support the described Use Cases Allows more complex integration patterns using intermediaries within an ESB 28
15 Basic Web Service Pattern Client issues request to a Web Service Interface Interface is defined using a WSDL Client expects one of several results: Request is successfully processed and reply is returned in a timely manner Request is accepted but reply returns an application level error Request results in the return of a fault to the client No reply or fault is returned in a timely manner 29 Basic JMS Request/Reply Pattern Client sends a JMS Message to a Topic or Queue Reply may be synchronous or asynchronous The reply is optional Client expects one of several results: Request is successfully sent to a topic or queue and reply is returned in a timely manner Request is accepted but reply returns an application level error Attempt to send a Request to the topic or queue fails No reply is ever received 30
16 Event Listener Pattern A process listens for published events All subscribers to a topic will receive a copy of the message asynchronously JMS allows for durable subscriptions Event messages are send and consumed asynchronously 31 Custom Integration Patterns These would potentially include, but not be limited to patterns such as: Content-Based Router, where messages are routed based upon message content typically referenced using XPath expressions Smart Proxy, where messages may be redispatched to a specific destination service, where replies are accepted from the service and passed back to the client Claim Check, where a copy of an often very large file is maintained as a document for use by other processes, where the current status of the document is tracked, but the document is typically transported by means other than messaging Transformation, where transformations usually defined by XSL are used to reformat message contents Bridge, where a message published on a topic or queue may be forwarded to or received from another messaging infrastructure (this pattern can sometimes be implemented using third party products or simply through configuration) 32
17 Custom Integration Patterns Content-Based Router ESB Pattern using JMS allow Routing of Request Bus can make decisions related to the request handling 33 Custom Integration Patterns Smart Proxies Extends the Content-based router to permit a request to be initiated by a Web Service or a JMS Client Smart Proxies can dispatch the requests and correlate the responses 34
18 Custom Integration Patterns Service Integration Allows a service to expose its interface as a Web Service Adapter is in the ESB to convert the internal JMS message to the appropriate WS Request 35 Custom Integration Patterns Legacy Service Integration Have a Service that is not compliant to the standard Compliant Middleware Adapter is used in the ESB to provide a compliant interface 36
19 Message Flows All flows would typically use the ESB as an intermediary Events can be generated by servers or within the ESB Servers can also make client requests Some clients (and servers) will listen for events Transports used are web services and JMS 37 The Standards Based Integration Company Systems Integration Specialists Company, Inc : Web Services Implementation Profile CIM University San Francisco October 11, 2010 Margaret Goodrich, Manager, Systems Engineering SISCO, Inc ½ Mile Road Sterling Heights, MI USA Tel: Fax:
20 Introduction Scope/Purpose Message Exchange Patterns Integration Patterns Other Topics: Message Organization Interface Specifications ESB Considerations Security Considerations 39 Scope/Purpose Provides recommendations for Web Service implementation using Service Oriented Architecture (SOA) service patterns and Web Services Description Language (WSDL). The Goal is to provide sufficient information to enable implementations to be interoperable. Will be used as an integral part of the interoperability tests for distribution management systems in 2010 and beyond. 40
21 Message Exchange Patterns Three basic types: One Way Two Way Call Back 41 Message Exchange Pattern: One Way The sender sends its request out but does not expect a response message back. Since typically HTTP protocol is used, the sender can still get HTTP-level information such as a HTTP 404 error for a failed server communication. sd One-way Sender Receiver Request() 42
22 Message Exchange Pattern: Two Way Is a synchronous process with typically two messages involved, one for request and one for response. A sender sends a request to a receiver who returns a response message back to the sender. The request message is indicated as Request and the response message Response. sd Two-way Sender Receiver Request() Response() 43 Message Exchange Pattern: Call Back The callback is an asynchronous process for message exchange. It is made of two request/response (initial and final) synchronous calls. The two are correlated in a way that each party can unambiguously identify which callback goes with which initial request. The Sender sends an initial request to Receiver with a message called InitialRequest. The Receiver receives the message, returns a response message back and invokes the final request/response call with a request message called FinalRequest. The whole call-back process is completed after the Sender replies the final request. 44
23 Message Exchange Pattern: Call Back sd Call-back Sender Receiver InitialRequest() InitialResponse() FinalRequest() FinalResponse() 45 Integration Patterns There are two Patterns Basic Patterns: Service Level Patterns these include Send, Request, Reply, Retrieve, Receive, Execute or Show Operation Level Patterns these include Create, Change, Cancel, Close, Delete, Created, Changed, Canceled, Closed, Deleted The Common Service/Operation Patterns are: Direct and Indirect Send-Receive Service Interaction 46
24 Integration Patterns - Continued Additional Common Service/Operation Patterns: Request-Execute-Reply-Receive Services Interaction Pattern Request-Execute Services Interaction Pattern Request-Receive Services Interaction Pattern Show-Receive Services Interaction Pattern Retrieve-Execute-Show-Receive Services Interaction Pattern Retrieve-Execute Services Interaction Pattern Execute-Reply Services Interaction Pattern 47 Integration Pattern: Direct & Indirect Two methods to complete a data transaction from one system/application to another: with an intermediary (e.g. ESB) - Indirect without an intermediary Direct Direct is also known as point-to-point integration. That is, only one service needs to be provided by a service provider. Indirect requires two services. 48
25 Integration Pattern: Direct sd Direct Direct Application A Application B Request() Reply() 49 Integration Pattern: Indirect sd Indirect Indirect Direct Application A Intermediary Application B Request() Reply() Request() Reply() 50
26 Integration Pattern: Send-Receive Services Interaction Application A sends its data through a Send Web service to an intermediary, such as an Enterprise Service Bus (ESB) Application B provides a Receive service in order to receive the data. Hence there are two Web services are involved. This is an indirect interaction process since Application A does not send its data directly to B but through ESB. It is an asynchronous process since multiple invocation threads are involved. 51 Integration Pattern: Send and Receive Services Interaction sd SendReceive Pattern Application A Direct Intermediary Application B CreatedWorkOrder() Acknowlegement() CreatedWorkOrder() Acknowledgement() 52
27 Integration Pattern: Request-Execute-Reply- Receive Services Interaction Application B sends a request to create, change, or cancel to Application A using one Request Web service and one Execute service provided by the ESB and Application A, respectively. After it retrieves the data, Application A calls a Reply service at the ESB which then passes the request onto Application B using a Receive service. Process happens in an asynchronous fashion, although each service call in this case is a synchronous call (acknowledgement as a reply). This is an indirect interaction process since Application B does not send a request directly to Application A, but through the ESB. It is an asynchronous process since multiple invocation threads are involved. There are four Web services involved in this case. 53 Integration Pattern: Request-Execute-Reply- Receive Services Interaction sd RequestExecuteReplyReceive Pattern Application A CreateWorkOrder() Direct Intermediary Application B Acknowlegement() CreateWorkOrder() Acknowlegement() CreatedWorkOrder() CreatedWorkOrder() Acknowlegement() Acknowledgement() 54
28 Integration Pattern: Request-Execute Services Interaction Application B sends a request to create, change, or cancel to Application A using one Request and/or one Execute Web services provided by ESB and Application A, respectively. This is a synchronous interaction pattern. There is no need to have a Reply or Receive service at Application B side to receive a reply from Application A since the original Request thread is still open. A Reply is simply an acknowledgement return from Application A in this case. This interaction may or may not go through ESB. If an ESB is in the middle, one Request and one Execute service are needed. If it is a Direct interaction between B and A, only an Execute service is needed. 55 Integration Pattern: Request-Execute Services Interaction sd RequestExecute Pattern Indirect Application A Direct Intermediary Application B CreateWorkOrder() CreateWorkOrder() Acknowledgement() Acknowledgement() 56
29 Integration Pattern: Request-Receive Services Interaction Application B requests a data from Application A using a Request service provided by Application A. After the data is retrieved, Application A sends the work order to Application B using a Reply service. This is similar to Request-Execute-Reply-Receive pattern in a sense that both are asynchronous interactions. However it does not include an ESB in the middle. It is a direct call from B to A for a request, and another call from A to B for reply. 57 Integration Pattern: Request-Receive Services Interaction sd Request/Reply Indirect Application B Application A CreateWorkOrder() Acknowledgement() CreatedWorkOrder() Acknowledgement() 58
30 Other Topics of IEC Additional patterns are being documented Message Organization Provides an overview of the message organization as defined in the Part 9 standard. Interface Specifications Gives a description of the WSDL Structure, document style SOAP binding, and MTOM (Message Transmission Optimization Mechanism) ESB Considerations Describes common ESB characteristics and recommendations and refers the reader to Security Considerations Discusses XML Encrytion and XML Signatures. 59 Discussion!!!! zzzzz 60
31 Questions & Contacts Margaret Goodrich Home Office: Cell:
IEC : Implementation Profile
The Standards Based Integration Company Systems Integration Specialists Company, Inc. IEC 61968 100: Implementation Profile CIM University Prague, Czech Republic May 10, 2011 Margaret Goodrich, Manager,
More information: ESB Implementation Profile
The Standards Based Integration Company Systems Integration Specialists Company, Inc. 61968 1-1: ESB Implementation Profile CIM University CESI/TERNA Milan, Italy June 15, 2010 Margaret Goodrich, Manager,
More informationIEC Implementation Profiles for IEC 61968
IEC 61968-100 Implementation Profiles for IEC 61968 Overview CIM University UCAIug Summit New Orleans, LA 22 October 2012 Agenda Introduction A look at the purpose, scope and key terms and definitions.
More informationIEC Overview CIM University UCAIug Summit Austin, TX. 18 November 2011
IEC 61968-100 Overview CIM University UCAIug Summit Austin, TX 18 November 2011 Agenda Introduction A look at the purpose, scope and key terms and definitions. Use Cases and Messaging Patterns What are
More informationEnterprise Integration Using IEC
Enterprise Integration Using IEC 61968-100 Scott Neumann, UISOL Margaret Goodrich, SISCO Michael Johnson, Elster CIMug Meeting Introduction The purpose of this presentation is to describe enterprise integration
More informationImplementing a Ground Service- Oriented Architecture (SOA) March 28, 2006
Implementing a Ground Service- Oriented Architecture (SOA) March 28, 2006 John Hohwald Slide 1 Definitions and Terminology What is SOA? SOA is an architectural style whose goal is to achieve loose coupling
More informationBEAAquaLogic. Service Bus. JPD Transport User Guide
BEAAquaLogic Service Bus JPD Transport User Guide Version: 3.0 Revised: March 2008 Contents Using the JPD Transport WLI Business Process......................................................2 Key Features.............................................................2
More informationSoftware Architecture Patterns
Software Architecture Patterns *based on a tutorial of Michael Stal Harald Gall University of Zurich http://seal.ifi.uzh.ch/ase www.infosys.tuwien.ac.at Overview Goal Basic architectural understanding
More informationSimple Object Access Protocol (SOAP) Reference: 1. Web Services, Gustavo Alonso et. al., Springer
Simple Object Access Protocol (SOAP) Reference: 1. Web Services, Gustavo Alonso et. al., Springer Minimal List Common Syntax is provided by XML To allow remote sites to interact with each other: 1. A common
More informationRealisation of SOA using Web Services. Adomas Svirskas Vilnius University December 2005
Realisation of SOA using Web Services Adomas Svirskas Vilnius University December 2005 Agenda SOA Realisation Web Services Web Services Core Technologies SOA and Web Services [1] SOA is a way of organising
More informationLesson 5 Web Service Interface Definition (Part II)
Lesson 5 Web Service Interface Definition (Part II) Service Oriented Architectures Security Module 1 - Basic technologies Unit 3 WSDL Ernesto Damiani Università di Milano Controlling the style (1) The
More informationOracle SOA Suite 11g: Build Composite Applications
Oracle University Contact Us: 1.800.529.0165 Oracle SOA Suite 11g: Build Composite Applications Duration: 5 Days What you will learn This course covers designing and developing SOA composite applications
More informationDS 2009: middleware. David Evans
DS 2009: middleware David Evans de239@cl.cam.ac.uk What is middleware? distributed applications middleware remote calls, method invocations, messages,... OS comms. interface sockets, IP,... layer between
More informationOracle Exam 1z0-478 Oracle SOA Suite 11g Certified Implementation Specialist Version: 7.4 [ Total Questions: 75 ]
s@lm@n Oracle Exam 1z0-478 Oracle SOA Suite 11g Certified Implementation Specialist Version: 7.4 [ Total Questions: 75 ] Question No : 1 Identify the statement that describes an ESB. A. An ESB provides
More informationIntroduction to Web Services & SOA
References: Web Services, A Technical Introduction, Deitel & Deitel Building Scalable and High Performance Java Web Applications, Barish Web Service Definition The term "Web Services" can be confusing.
More informationJava EE 7: Back-End Server Application Development
Oracle University Contact Us: Local: 0845 777 7 711 Intl: +44 845 777 7 711 Java EE 7: Back-End Server Application Development Duration: 5 Days What you will learn The Java EE 7: Back-End Server Application
More informationService Interface Design RSVZ / INASTI 12 July 2006
Architectural Guidelines Service Interface Design RSVZ / INASTI 12 July 2006 Agenda > Mandatory standards > Web Service Styles and Usages > Service interface design > Service versioning > Securing Web
More informationLesson 3 SOAP message structure
Lesson 3 SOAP message structure Service Oriented Architectures Security Module 1 - Basic technologies Unit 2 SOAP Ernesto Damiani Università di Milano SOAP structure (1) SOAP message = SOAP envelope Envelope
More informationUsing CIMTool. The Standards Based Integration Company. Systems Integration Specialists Company, Inc.
The Standards Based Integration Company Systems Integration Specialists Company, Inc. Using CIMTool Margaret Goodrich, Manager, Systems Engineering SISCO, Inc. 6605 19½ Mile Road Sterling Heights, MI 48314
More informationC exam. IBM C IBM WebSphere Application Server Developer Tools V8.5 with Liberty Profile. Version: 1.
C9510-319.exam Number: C9510-319 Passing Score: 800 Time Limit: 120 min File Version: 1.0 IBM C9510-319 IBM WebSphere Application Server Developer Tools V8.5 with Liberty Profile Version: 1.0 Exam A QUESTION
More informationA Generic Approach for Compliance Assessment of Interoperability Artifacts
A Generic Approach for Compliance Assessment of Interoperability Artifacts Stipe Fustar Power Grid 360 11060 Parkwood Drive #2, Cupertino, CA 95014 sfustar@powergrid360.com Keywords: Semantic Model, IEC
More informationWeb Services & Axis2. Architecture & Tutorial. Ing. Buda Claudio 2nd Engineering Faculty University of Bologna
Web Services & Axis2 Architecture & Tutorial Ing. Buda Claudio claudio.buda@unibo.it 2nd Engineering Faculty University of Bologna June 2007 Axis from SOAP Apache Axis is an implementation of the SOAP
More informationdescribe the functions of Windows Communication Foundation describe the features of the Windows Workflow Foundation solution
1 of 9 10/9/2013 1:38 AM WCF and WF Learning Objectives After completing this topic, you should be able to describe the functions of Windows Communication Foundation describe the features of the Windows
More informationIntroduction to Web Services & SOA
References: Web Services, A Technical Introduction, Deitel & Deitel Building Scalable and High Performance Java Web Applications, Barish Service-Oriented Programming (SOP) SOP A programming paradigm that
More informationSun Java TM Composite Applications Platform Suite Implementing Selected EAI Patterns
Sun Java TM Composite Applications Platform Suite Implementing Selected EAI Patterns Michael Czapski, Enterprise Architect, Sun Microsystems Frank Kieviet, Senior Staff Engineer, Sun Microsystems TS-5301
More informationOracle Application Integration Architecture - Foundation Pack 2.5: Concepts and Technologies Guide
Oracle Application Integration Architecture - Foundation Pack 2.5: Concepts and Technologies Guide Release 2.5 Part No. E15762-01 October 2009 Oracle Application Integration Architecture - Foundation Pack
More informationGoal: Offer practical information to help the architecture evaluation of an SOA system. Evaluating a Service-Oriented Architecture
Evaluating a Service-Oriented Architecture Paulo Merson, SEI with Phil Bianco, SEI Rick Kotermanski, Summa Technologies May 2007 Goal: Offer practical information to help the architecture evaluation of
More informationOracle. Exam Questions 1z Java Enterprise Edition 5 Web Services Developer Certified Professional Upgrade Exam. Version:Demo
Oracle Exam Questions 1z0-863 Java Enterprise Edition 5 Web Services Developer Certified Professional Upgrade Exam Version:Demo 1.Which two statements are true about JAXR support for XML registries? (Choose
More informationWSDL versioning. Facts Basic scenario. WSDL -Web Services Description Language SAWSDL -Semantic Annotations for WSDL and XML Schema
Internet Engineering Tomasz Babaczyński ski, Zofia Kruczkiewicz Tomasz Kubik Information systems modelling UML and description languages WSDL -Web Services Description Language SAWSDL -Semantic Annotations
More informationSOAP Specification. 3 major parts. SOAP envelope specification. Data encoding rules. RPC conventions
SOAP, UDDI and WSDL SOAP SOAP Specification 3 major parts SOAP envelope specification Defines rules for encapsulating data Method name to invoke Method parameters Return values How to encode error messages
More informationEnterprise Messaging Infrastructure and use with SIB, MQ, DataPower and WMB
Enterprise Messaging Infrastructure and use with SIB, MQ, DataPower and WMB User Group Bedfont Lakes, 3 rd March 2009 Nigel Roper IBM s s ESB Portfolio Product Stacks Enterprise Service Bus Message Broker
More informationThis presentation is a primer on WSDL Bindings. It s part of our series to help prepare you for creating BPEL projects. We recommend you review this
This presentation is a primer on WSDL Bindings. It s part of our series to help prepare you for creating BPEL projects. We recommend you review this presentation before taking an ActiveVOS course or before
More informationWS-MessageDelivery Version 1.0
WS-MessageDelivery Version 1.0 WS-MessageDelivery Version 1.0 W3C Member Submission 26 April 2004 This version: http://www.w3.org/submission/2004/subm-ws-messagedelivery-20040426/ Latest version: http://www.w3.org/submission/ws-messagedelivery/
More informationIntegration Framework. Architecture
Integration Framework 2 Architecture Anyone involved in the implementation or day-to-day administration of the integration framework applications must be familiarized with the integration framework architecture.
More informationSUN. Java Platform Enterprise Edition 6 Web Services Developer Certified Professional
SUN 311-232 Java Platform Enterprise Edition 6 Web Services Developer Certified Professional Download Full Version : http://killexams.com/pass4sure/exam-detail/311-232 QUESTION: 109 What are three best
More informationSOAP. Jasmien De Ridder and Tania Van Denhouwe
SOAP Jasmien De Ridder and Tania Van Denhouwe Content Introduction Structure and semantics Processing model SOAP and HTTP Comparison (RPC vs. Message-based) SOAP and REST Error handling Conclusion Introduction
More informationJeppesen Solution Integrator Overview DOCUMENT VERSION 1.0
Jeppesen Solution Integrator Overview DOCUMENT VERSION 1.0 OCTOBER 1, 2014 Jeppesen Solution Integrator Overview DOCUMENT VERSION 1.0 Contents Figures Tables v vii Introduction 1 Getting Started........................................................
More information"Charting the Course... Mastering EJB 3.0 Applications. Course Summary
Course Summary Description Our training is technology centric. Although a specific application server product will be used throughout the course, the comprehensive labs and lessons geared towards teaching
More informationLesson 10 BPEL Introduction
Lesson 10 BPEL Introduction Service Oriented Architectures Module 1 - Basic technologies Unit 5 BPEL Ernesto Damiani Università di Milano Service-Oriented Architecture Orchestration Requirements Orchestration
More informationArchitectural patterns and models for implementing CSPA
Architectural patterns and models for implementing CSPA Marco Silipo THE CONTRACTOR IS ACTING UNDER A FRAMEWORK CONTRACT CONCLUDED WITH THE COMMISSION Application architecture Outline SOA concepts and
More informationJava Web Service Essentials (TT7300) Day(s): 3. Course Code: GK4232. Overview
Java Web Service Essentials (TT7300) Day(s): 3 Course Code: GK4232 Overview Geared for experienced developers, Java Web Service Essentials is a three day, lab-intensive web services training course that
More informationA Comparison of Service-oriented, Resource-oriented, and Object-oriented Architecture Styles
A Comparison of Service-oriented, Resource-oriented, and Object-oriented Architecture Styles Jørgen Thelin Chief Scientist Cape Clear Software Inc. Abstract The three common software architecture styles
More informationSERVICE-ORIENTED COMPUTING
THIRD EDITION (REVISED PRINTING) SERVICE-ORIENTED COMPUTING AND WEB SOFTWARE INTEGRATION FROM PRINCIPLES TO DEVELOPMENT YINONG CHEN AND WEI-TEK TSAI ii Table of Contents Preface (This Edition)...xii Preface
More informationActiveVOS JMS Transport options Technical Note
ActiveVOS JMS Transport options Technical Note 2009 Active Endpoints Inc. ActiveVOS is a trademark of Active Endpoints, Inc. All other company and product names are the property of their respective owners.
More informationWe recommend you review this before taking an ActiveVOS course or before you use ActiveVOS Designer.
This presentation is a primer on WSDL. It s part of our series to help prepare you for creating BPEL projects. We recommend you review this before taking an ActiveVOS course or before you use ActiveVOS
More informationA Perspective on the Transformation of zseries to Support New Workloads
A Perspective on the Transformation of zseries to Support New Workloads Carl Wohlers IBM Corporation carlw@us.ibm.com 1-877-535-6382 Mainframe and Distributed Server Integration In days of yore, the mainframe
More informationF O U N D A T I O N. OPC Unified Architecture. Specification. Part 1: Concepts. Version 1.00
F O U N D A T I O N Unified Architecture Specification Part 1: Concepts Version 1.00 July 28, 2006 Unified Architecture, Part 1 iii Release 1.00 CONTENTS Page FOREWORD... vi AGREEMENT OF USE... vi 1 Scope...
More informationMTAT Enterprise System Integration. Lecture 2: Middleware & Web Services
MTAT.03.229 Enterprise System Integration Lecture 2: Middleware & Web Services Luciano García-Bañuelos Slides by Prof. M. Dumas Overall view 2 Enterprise Java 2 Entity classes (Data layer) 3 Enterprise
More information2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.
T0/06-6 revision 2 Date: May 22, 2006 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular documentation
More informationModel Driven Integration Using CCAPI Technologies
Model Driven Integration Using CCAPI Technologies 2002 EMS Users Conference Ralph Mackiewicz, SISCO Inc. Agenda What is Model Driven Integration? Common Information Model Model Driven Messaging Model Aware
More informationOracle Fusion Middleware
Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1 (11.1.1.5.0) E17366-03 April 2011 Oracle Fusion
More information2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.
T0/04-023 revision 2 Date: September 06, 2005 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular
More informationIT6801-SERVICE ORIENTED ARCHITECTURE
ST.JOSEPH COLLEGE OF ENGINEERING DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING IT 6801-SERVICE ORIENTED ARCHITECTURE UNIT I 2 MARKS 1. Define XML. Extensible Markup Language(XML) is a markup language
More informationSERIES X: DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY OSI applications Generic applications of ASN.1
International Telecommunication Union ITU-T X.892 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2005) SERIES X: DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY OSI applications Generic applications
More informationSentinet for Microsoft Azure SENTINET
Sentinet for Microsoft Azure SENTINET Sentinet for Microsoft Azure 1 Contents Introduction... 2 Customer Benefits... 2 Deployment Topologies... 3 Cloud Deployment Model... 3 Hybrid Deployment Model...
More informationXML Web Service? A programmable component Provides a particular function for an application Can be published, located, and invoked across the Web
Web Services. XML Web Service? A programmable component Provides a particular function for an application Can be published, located, and invoked across the Web Platform: Windows COM Component Previously
More informationWHY WE NEED AN XML STANDARD FOR REPRESENTING BUSINESS RULES. Introduction. Production rules. Christian de Sainte Marie ILOG
WHY WE NEED AN XML STANDARD FOR REPRESENTING BUSINESS RULES Christian de Sainte Marie ILOG Introduction We are interested in the topic of communicating policy decisions to other parties, and, more generally,
More informationTowards a Telecommunication Service Oriented Architecture
Towards a Telecommunication Service Oriented Architecture Paolo Falcarin Jian Yu Politecnico di Torino, Italy paolo.falcarin@polito.it, jian.yu@polito.it Abstract Web Services are often used for providing
More informationJD Edwards EnterpriseOne Tools
JD Edwards EnterpriseOne Tools Business Services Development Guide Release 9.1.x E24218-02 September 2012 JD Edwards EnterpriseOne Tools Business Services Development Guide, Release 9.1.x E24218-02 Copyright
More informationEllipse Web Services Overview
Ellipse Web Services Overview Ellipse Web Services Overview Contents Ellipse Web Services Overview 2 Commercial In Confidence 3 Introduction 4 Purpose 4 Scope 4 References 4 Definitions 4 Background 5
More informationSHORT NOTES / INTEGRATION AND MESSAGING
SHORT NOTES / INTEGRATION AND MESSAGING 1. INTEGRATION and MESSAGING is related to HOW to SEND data to and receive from ANOTHER SYSTEM or APPLICATION 2. A WEB SERVICE is a piece of software designed to
More informationAppendix A - Glossary(of OO software term s)
Appendix A - Glossary(of OO software term s) Abstract Class A class that does not supply an implementation for its entire interface, and so consequently, cannot be instantiated. ActiveX Microsoft s component
More informationJAVA COURSES. Empowering Innovation. DN InfoTech Pvt. Ltd. H-151, Sector 63, Noida, UP
2013 Empowering Innovation DN InfoTech Pvt. Ltd. H-151, Sector 63, Noida, UP contact@dninfotech.com www.dninfotech.com 1 JAVA 500: Core JAVA Java Programming Overview Applications Compiler Class Libraries
More informationIntroduction to Web Services
Introduction to Web Services SWE 642, Spring 2008 Nick Duan April 9, 2008 1 Overview What are Web Services? A brief history of WS Basic components of WS Advantages of using WS in Web application development
More informationEnterprise SOA Experience Workshop. Module 8: Operating an enterprise SOA Landscape
Enterprise SOA Experience Workshop Module 8: Operating an enterprise SOA Landscape Agenda 1. Authentication and Authorization 2. Web Services and Security 3. Web Services and Change Management 4. Summary
More informationEuropean Component Oriented Architecture (ECOA ) Collaboration Programme: Architecture Specification Part 2: Definitions
European Component Oriented Architecture (ECOA ) Collaboration Programme: Part 2: Definitions BAE Ref No: IAWG-ECOA-TR-012 Dassault Ref No: DGT 144487-D Issue: 4 Prepared by BAE Systems (Operations) Limited
More informationCmpE 596: Service-Oriented Computing
CmpE 596: Service-Oriented Computing Pınar Yolum pinar.yolum@boun.edu.tr Department of Computer Engineering Boğaziçi University CmpE 596: Service-Oriented Computing p.1/53 Course Information Topics Work
More information1. Draw the fundamental software technology architecture layers. Software Program APIs Runtime Operating System 2. Give the architecture components of J2EE to SOA. i. Java Server Pages (JSPs) ii. Struts
More informationXML. Part II DTD (cont.) and XML Schema
XML Part II DTD (cont.) and XML Schema Attribute Declarations Declare a list of allowable attributes for each element These lists are called ATTLIST declarations Consists of 3 basic parts The ATTLIST keyword
More informationWSDL. Stop a while to read about me!
WSDL Stop a while to read about me! Part of the code shown in the following slides is taken from the book Java by D.A. Chappell and T. Jawell, O Reilly, ISBN 0-596-00269-6 What is WSDL? Description Language
More informationSEMI North America XML Messaging with E128
1 SEMI North America XML Messaging with E128 Bob Hodges BHodges ti.com July 18, 2003 1 XML Messaging Objective 2 Define a SEMI standard for XML asynchronous messaging using header elements in standard
More informationOverview SENTINET 3.1
Overview SENTINET 3.1 Overview 1 Contents Introduction... 2 Customer Benefits... 3 Development and Test... 3 Production and Operations... 4 Architecture... 5 Technology Stack... 7 Features Summary... 7
More informationONVIF Device IO Client Test Specification
ONVIF Device IO Client Test Specification Version 17.12 December 2017 www.onvif.org 2017 ONVIF, Inc. All rights reserved. Recipients of this document may copy, distribute, publish, or display this document
More informationProgramming Web Services in Java
Programming Web Services in Java Description Audience This course teaches students how to program Web Services in Java, including using SOAP, WSDL and UDDI. Developers and other people interested in learning
More information[MS-DPWSSN-Diff]: Devices Profile for Web Services (DPWS): Size Negotiation Extension
[MS-DPWSSN-Diff]: Devices Profile for Web Services (DPWS): Size Negotiation Extension Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes
More informationXEP-0357: Push Notifications
XEP-0357: Push Notifications Kevin Smith mailto:kevin@kismith.co.uk xmpp:kevin@doomsong.co.uk Lance Stout mailto:lance@andyet.com xmpp:lance@lance.im 2017-08-24 Version 0.3 Status Type Short Name Experimental
More informationGeneric Operations. Document number: DSP0223. Date: Version: Document type: Specification. Document status: DMTF Standard
1 2 3 4 Document number: Date: 2012-08-30 Version: 1.0.1 5 6 7 8 9 10 11 12 13 14 15 16 Document type: Specification Document status: DMTF Standard Document language: en-us 17 18 19 Copyright notice Copyright
More informationSOAP / WSDL INTRODUCTION TO SOAP, WSDL AND UDDI, THE COMBO FOR BIG WEB SERVICES SOAP - WSDL - UDDI. PETER R. EGLI peteregli.net. peteregli.
/ WSDL INTRODUCTION TO, WSDL AND UDDI, THE COMBO FOR BIG WEB SERVICES PETER R. EGLI 1/31 Contents 1. What is a web service? 2. Web service architecture 3. Web service versus conventional object middleware
More informationCOMMUNICATION PROTOCOLS
COMMUNICATION PROTOCOLS Index Chapter 1. Introduction Chapter 2. Software components message exchange JMS and Tibco Rendezvous Chapter 3. Communication over the Internet Simple Object Access Protocol (SOAP)
More informationIntroduction in Eventing in SOA Suite 11g
Introduction in Eventing in SOA Suite 11g Ronald van Luttikhuizen Vennster Utrecht, The Netherlands Keywords: Events, EDA, Oracle SOA Suite 11g, SOA, JMS, AQ, EDN Introduction Services and events are highly
More informationA Messaging-Based Integration Architecture for Print Production Workflow Systems
A Messaging-Based Integration Architecture for Print Production Workflow Systems Claes Buckwalter Digital Media, ITN, Linköping University, Sweden Abstract A print production workflow consists of a number
More informationUtility Operations & Best Practices The CIM: What it is and how it s being used
Utility Operations & Best Practices The CIM: What it is and how it s being used Ricardo Lopez Sr. Product Manager Itron Enterprise Edition Meter Data Management The CIM What It Is and How It s Being Used
More informationMOM MESSAGE ORIENTED MIDDLEWARE OVERVIEW OF MESSAGE ORIENTED MIDDLEWARE TECHNOLOGIES AND CONCEPTS. MOM Message Oriented Middleware
MOM MESSAGE ORIENTED MOM Message Oriented Middleware MIDDLEWARE OVERVIEW OF MESSAGE ORIENTED MIDDLEWARE TECHNOLOGIES AND CONCEPTS Peter R. Egli 1/25 Contents 1. Synchronous versus asynchronous interaction
More informationResearch on Publishing CIM Model Change Events through OPC UA
Research on Publishing CIM Model Change Events through OPC UA Zewu Peng 1, Churan Deng 1,*, Bojian Wen 1, and Qingping Xu 2 1 Information Centre of Guangdong Power Grid Corporation, 510600 Guangzhou, China.
More informationRESTful Network API for Notification Channel
RESTful Network API for Notification Channel Candidate Version 1.0 17 Jan 2012 Open Mobile Alliance OMA-TS-REST_NetAPI_NotificationChannel-V1_0-20120117-C OMA-TS-REST_NetAPI_NotificationChannel-V1_0-20120117-C
More informationJava EE 7: Back-end Server Application Development 4-2
Java EE 7: Back-end Server Application Development 4-2 XML describes data objects called XML documents that: Are composed of markup language for structuring the document data Support custom tags for data
More informationW3c Xml Schema 1.0 Data Type Datetime
W3c Xml Schema 1.0 Data Type Datetime The XML Schema recommendations define features, such as structures ((Schema Part 1)) and simple data types ((Schema Part 2)), that extend the XML Information Set with
More informationONVIF OSD Client Test Specification
ONVIF OSD Client Test Specification Version 18.06 June 2018 www.onvif.org 2018 ONVIF, Inc. All rights reserved. Recipients of this document may copy, distribute, publish, or display this document so long
More informationLesson 15 SOA with REST (Part II)
Lesson 15 SOA with REST (Part II) Service Oriented Architectures Security Module 3 - Resource-oriented services Unit 1 REST Ernesto Damiani Università di Milano REST Design Tips 1. Understanding GET vs.
More informationXml Schema Attribute Definition Language (xsd) 1.1 Part 1
Xml Schema Attribute Definition Language (xsd) 1.1 Part 1 According to the XSD 1.0 spec, XML Schema Part 1: Structures Second Edition: to the XSD 1.1 spec, W3C XML Schema Definition Language (XSD) 1.1
More informationDistributed Systems. Web Services (WS) and Service Oriented Architectures (SOA) László Böszörményi Distributed Systems Web Services - 1
Distributed Systems Web Services (WS) and Service Oriented Architectures (SOA) László Böszörményi Distributed Systems Web Services - 1 Service Oriented Architectures (SOA) A SOA defines, how services are
More informationNext-Generation SOA Infrastructure. An Oracle White Paper May 2007
Next-Generation SOA Infrastructure An Oracle White Paper May 2007 Next-Generation SOA Infrastructure INTRODUCTION Today, developers are faced with a bewildering array of technologies for developing Web
More informationD-Cinema Packaging Caption and Closed Subtitle
SMPTE STANDARD SMPTE 429-12-2008 D-Cinema Packaging Caption and Closed Subtitle Page 1 of 11 pages Table of Contents Page Foreword... 2 Intellectual Property... 2 1 Scope... 3 2 Conformance Notation...
More informationXML: Extensible Markup Language
XML: Extensible Markup Language CSC 375, Fall 2015 XML is a classic political compromise: it balances the needs of man and machine by being equally unreadable to both. Matthew Might Slides slightly modified
More information(9A05803) WEB SERVICES (ELECTIVE - III)
1 UNIT III (9A05803) WEB SERVICES (ELECTIVE - III) Web services Architecture: web services architecture and its characteristics, core building blocks of web services, standards and technologies available
More informationWeb Services Reliable Messaging TC WS-Reliability
1 2 3 4 Web Services Reliable Messaging TC WS-Reliability Working Draft 0.992, 10 March 2004 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Document identifier: wd-web services reliable
More informationOracle Fusion Middleware
Oracle Fusion Middleware Administering Web Services 12c (12.1.2) E28131-01 June 2013 Documentation for developers and administrators that describes how to administer Web services. Oracle Fusion Middleware
More informationONVIF Advanced Security Client Test Specification
ONVIF Advanced Security Client Test Specification Version 17.06 June 2017 www.onvif.org 2017 ONVIF, Inc. All rights reserved. Recipients of this document may copy, distribute, publish, or display this
More informationWeb Services Development for IBM WebSphere Application Server V7.0
000-371 Web Services Development for IBM WebSphere Application Server V7.0 Version 3.1 QUESTION NO: 1 Refer to the message in the exhibit. Replace the??? in the message with the appropriate namespace.
More informationConnecting ESRI to Anything: EAI Solutions
Connecting ESRI to Anything: EAI Solutions Frank Weiss P.E., ESRI User s Conference 2002 Agenda Introduction What is EAI? Industry trends Key integration issues Point-to-point interfaces vs. Middleware
More information