Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

SOE > GA 2 > Flashcards

GA 2 Flashcards

(18 cards)

Start Studying
1
Q

Foundation for Web Servies

A 
Compose and Combine Services: BPEL
Publish, Find, Use Services: UDDI
Formal Service Descriptions: WSDL
Service Interactions: SOAP
Universal Data Format: XML
Ubiquitous Communications: Internet
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

XML Document Structure

A

XML document (aka XML document instance or instance)

A specific data set for a given markup language

Base for fundamental Web services technologies (SOAP, WSDL, UDDI and BPEL)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

XML Structure

A

Well-formedness (syntactically correct)

  • XML documents must have a root element
  • XML elements must have a closing tag
  • XML tags are case sensitive
  • XML elements must be properly nested
  • XML attribute values must be quoted

Validity (grammatically correct)

  • Well-formed and:
  • referring to correct document type declaration
  • Document obeys declaration constrains
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

XML Schema Definition Language

A

XSD: description of content and structure of XML documents in XML

  • Declaration of elements and attributes and how they are arranged inside a document
  • Reuse of elements rom other schemas
  • Definition of complex elements
  • Definition of restrictions (data types, values etc.)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

XSD document structure

A
  • Root element: schema
  • Element & Attribute declarations (instantiations)
  • (New) type definitions
    • Simple/complex
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

XML element vs. attribute

A

Both are used to store data

but:

  • attribute can be seen as a characteristic or property while nested element as embedded hierarchical child element of the parent element
  • attribute has no cardinalities
  • attribute has no internal structure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is SOAP?

A

SOAP is a lightweight protocol intended for exchanging structured information in a decentralised, distributed environment

SOAP is a way for a program running in one operating system to communicate with a program running in either the s are or a different operating system, using HTTP (or any other transport protocol) and XML

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

SOAP Messaging Framework

A

= XML-based messaging framework that is:

  • Extensible
  • Interoperable
  • Independent
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

SOAP Extensible

A
  • Simplicity remains one of SOAP’s primary design goals
  • SOAP defines a communication framework that allows for features such as security, routing, and reliability to be added later as layered extensions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

SOAP Independent

A
  • SOAP allows for any programming model
  • SOAP defines a model for processing individual, one-way messages
  • SOAP also allows for any number of message exchange patterns (MEPs)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

SOAP Message Format

A

SOAP message consists of three parts:

  • SOAP Envelope
  • SOAP Header (optional)
  • SOAP Body
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

SOAP Envelope

A

The SOAP Envelope construct defines an overall framework for expressing what is in a message and who should deal with it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

SOAP Header

A
  • The Header element is a generic container for
    control information
  • It may contain any number of elements from
    any namespace
  • Header blocks should contain information that
    influences payload processing
  • Header is optional
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

SOAP Body

A

The body element represents the message payload

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Web Services Description Language

A

Why?

  • Description in consistent manner for providers, clients, developers etc.
  • Precise XML interface along with misc. messages defined a priori
  • XML Schema not enough

What?

  • Machine understandable XML specification describing:
    • Structure
    • Operational characteristics
    • Wire format & transport protocol
    • Payload data via type system (based on XML Schema complex types)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is WSDL for?

Study These Flashcards
A

WSDL describes:

  • What a service’s interface looks like
  • How a service is accessed
  • Where a service is located

WSDL does NOT describe:
- computations and semantics

Essentially: a contract between Provider and Consumer of service

17
Q

WSDL Characteristics

Study These Flashcards
A
  • Platform- and language- independence
  • Schema validated
  • Division of interface description and technical details
    • Service interface definition
      • Operations, parameters and abstract data types
    • Service implementation definition
      • Binding to network address, protocol and data formats
18
Q

WSDL Implementation definition

Study These Flashcards
A

Binding
 Defines message exchange
 Binds the port type to a service implementation (but not specific address)
 Information about protocol, message style and formatting, and data types
 Correspondence with PortType
 Several bindings may represent various impl. of the same PortType (e.g. different protocols)
 Port
 Single endpoint(s): combination of binding and network address
 Service
 Uniquely named collection of related port elements
 May be exposed via multiple ports of different bindings

SOE (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions