JEPPIAAR ENGINEERING COLLEGE

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

QUESTION BANK

IT6801

SERVICE ORIENTED ARCHITECTURE

IV YEAR – VII SEM

2014 -2018 BATCH
Vision of Institution: To build Jeppiaar Engineering College as an Institution of Academic
Excellence in Technical education and Management education and to become a World Class
University.

Mission of Institution

M1 To excel in teaching and learning, research and innovation by promoting the

principles of scientific analysis and creative thinking

To participate in the production, development and dissemination of knowledge and

M2
interact with national and international communities

To equip students with values, ethics and life skills needed to enrich their lives and
M3
enable them to meaningfully contribute to the progress of society

To prepare students for higher studies and lifelong learning, enrich them with the
M4
practical and entrepreneurial skills necessary to excel as future professionals and
contribute to Nation’s economy

Vision of Department: To emerge as a globally prominent department, developing ethical

computer professionals, innovators and entrepreneurs with academic excellence through
quality education and research.

Mission of Department

To create computer professionals with an ability to identify and formulate the

M1
engineering problems and also to provide innovative solutions through effective
teaching learning process.

M2 To strengthen the core-competence in computer science and engineering and to create

an ability to interact effectively with industries.

M3 To produce engineers with good professional skills, ethical values and life skills for the
betterment of the society.

M4 To encourage students towards continuous and higher level learning on technological

advancements and provide a platform for employment and self-employment.
PROGRAM OUTCOMES (POs)

P405. Engineering Knowledge: Apply the knowledge of mathematics, science, engineering

1 fundamentals, and an engineering specialization to the solution of computer science
engineering problems.
P405. Problem analysis: Identify, formulate, review research literature, and analyze complex
2 engineering problems reaching substantiated conclusions using first principles of
mathematics, natural sciences, and engineering sciences.
Design/development of solutions: Design solutions for complex engineering problems and
P405. design system components or processes that meet the specified needs with appropriate
3 consideration for the public health and safety, and the cultural, societal, and environmental
considerations.
Conduct investigations of complex problems: Use research-based knowledge and research
PO4 methods including design of experiments, analysis and interpretation of data, and synthesis of
the information to provide valid conclusions.
Modern tool usage: Create, select, and apply appropriate techniques, resources, and modern
PO5 engineering and IT tools including prediction and modeling to complex engineering activities
with an understanding of the limitations.
The engineer and society: Apply reasoning informed by the contextual knowledge to assess
PO6 societal, health, safety, legal and cultural issues and the consequent responsibilities relevant
to the professional engineering practice.
Environment and sustainability: Understand the impact of the professional engineering
PO7 solutions in societal and environmental contexts, and demonstrate the knowledge of, and
need for sustainable development.
PO8 Ethics: Apply ethical principles and commit to professional ethics and responsibilities and
norms of the engineering practice.
PO9 Individual and team work: Function effectively as an individual, and as a member or
leader in diverse teams, and in multidisciplinary settings.
Communication: Communicate effectively on complex engineering activities with the
P405. engineering community and with society at large, such as, being able to comprehend and
10
write effective reports and design documentation, make effective presentations, and give and
receive clear instructions.
Project management and finance: Demonstrate knowledge and understanding of the
P405. engineering and management principles and apply these to one’s own work, as a member and
11 leader in a team, to manage projects and in multidisciplinary environments.

P405. Life-long learning: Recognize the need for, and have the preparation and ability to engage
12 in independent and life-long learning in the broadest context of technological change.
PROGRAMME EDUCATIONAL OBJECTIVES (PEOs)

PEO 01: To address the real time complex engineering problems using innovative approach
with strong core computing skills.

PEO 02: To apply core-analytical knowledge and appropriate techniques and provide solutions
to real time challenges of national and global society.

PEO 03: Apply ethical knowledge for professional excellence and leadership for the betterment
of the society.

PEO 04: Develop life-long learning skills needed for better employment and entrepreneurship.

PROGRAMME SPECIFIC OUTCOME (PSOs)

PS405.1 – An ability to understand the core concepts of computer science and engineering and to
enrich problem solving skills to analyze, design and implement software and hardware based
systems of varying complexity.

PS405.2 - To interpret real-time problems with analytical skills and to arrive at cost effective and
optimal solution using advanced tools and techniques.

PS405.3 - An understanding of social awareness and professional ethics with practical

proficiency in the broad area of programming concepts by lifelong learning to inculcate
employment and entrepreneurship skills.

COURSE OUTCOME (COs)

C405.1 Build XML Fundamentals

C405.2 Experiment with XML applications
C405.3 Understand the key principles behind SOA
C405.4 Develop web services using technology elements
C405.5 Apply SOA-based applications for intra-enterprise and inter-enterprise applications.
 SYLLABUS

UNIT I INTRODUCTION TO XML 9

XML document structure – Well formed and valid documents – Namespaces – DTD – XML Schema – X-
Files.

UNIT II BUILDING XML- BASED APPLICATIONS 9

Parsing XML – using DOM, SAX – XML Transformation and XSL – XSL Formatting – Modeling Databases in
XML.

UNIT III SERVICE ORIENTED ARCHITECTURE 9

Characteristics of SOA, Comparing SOA with Client-Server and Distributed architectures – Benefits of
SOA -- Principles of Service orientation – Service layers.

UNIT IV WEB SERVICES 9

Service descriptions – WSDL – Messaging with SOAP – Service discovery – UDDI – Message Exchange
Patterns – Orchestration – Choreography –WS Transactions.

UNIT V BUILDING SOA-BASED APPLICATIONS 9

Service Oriented Analysis and Design – Service Modeling – Design standards and guidelines --
Composition – WS-BPEL – WS-Coordination – WS-Policy – WS-Security – SOA support in J2EE
TOTAL : 45 PERIODS

TEXTBOOKS:
1. Ron Schmelzer et al. “XML and Web Services”, Pearson Education, 2002.
2. Thomas Erl, “Service Oriented Architecture: Concepts, Technology, and Design”, Pearson
Education, 2005.

REFERENCES:
1. Frank P.Coyle, “XML, Web Services and the Data Revolution”, Pearson Education, 2002
2. Eric Newcomer, Greg Lomow, “Understanding SOA with Web Services”, Pearson Education, 2005
3. Sandeep Chatterjee and James Webber, “Developing Enterprise Web Services: An Architect's Guide”,
Prentice Hall, 2004.
4. James McGovern, Sameer Tyagi, Michael E.Stevens, Sunil Mathew, “Java Web Services Architecture”,
Morgan Kaufmann Publishers, 2003.
 UNIT-I
INTRODUCTION TO XML 9

XML document structure – Well formed and valid documents – Namespaces – DTD – XML Schema – X-
Files.
PART A

Questions CO Bloom
Q.No ’s
Level
1 What are the major portions of XML document? C405.1 BTL1
The major portions of an XML document include the following:
• The XML declaration
• The Document Type Declaration
• The element data
• The attribute data
• The character data or XML content

2 What are the components of XML declaration? C405.1 BTL1

3 What are the XML delimiter characters? C405.1 BTL1

4 Define Document Type Declaration. C405.1 BTL1
The Document Type Declaration (DOCTYPE) gives a name to the XML content and provides a
means to guarantee
the document’s validity, either by including or specifying a link to a Document Type Definition
(DTD).

5 What are the components of Document Type Declaration? C405.1 BTL1

6 Define elements in XML document. C405.1 BTL1
XML elements can be defined as building blocks of an XML. Elements can behave as
containers to hold text, elements, attributes, media objects or all of these. Each XML
document contains one or more elements, the scope of which are either delimited by
start and end tags, or for empty elements, by an empty-element tag.

7 Define attributes in XML C405.1 BTL1

When you create XML Schemas, you define the individual elements and attributes and
assign valid types to them. Elements describe data, whereas attributes are like
properties of an element, in that they provide further definition about the element the
way that properties describe characteristics of objects and classes.

8 Define components in XML C405.1 BTL1

Comments are quite simple to include in a document. The character sequence <!--
begins a comment and --> ends the comment. Between these two delimiters, any text
at all can be written, including valid XML markup. The only restriction is that the
comment delimiters cannot be used; neither can the literal string --. Comments can be
placed anywhere in a document and are not considered to be part of the textual
content of an XML document.

9 Define DTD C405.1 BTL1

Document Type Definitions (DTDs) provide a means for defining what XML markup can
occur in an XML document. Basically, the DTD provides a mechanism to guarantee that
a given XML document complies with a well-defined set of rules for document
structure and content. These rules provide a framework for guaranteeing the “validity”
of a document. DTDs and the more recent XML Schema are the means for defining the
validity constraints on XML documents.

10 Define XML content C405.1 BTL1

The content between XML elements is where most of the value lies in an XML

document. In fact, that is almost exclusively where all the variable content lies. XML

elements are usually well defined and strict in their application

11 When the document will be considered as valid documents? BTL1
A well-formed XML document is considered valid only if it contains a proper Document
Type Declaration and if the document obeys the constraints of that declaration. In
most cases, the constraints of the declaration will be expressed as a DTD or an XML
Schema. Well-formed XML documents are designed for use without any constraints,
whereas valid XML documents explicitly require these constraint mechanisms. In
addition to constraining the possible elements and the ordering of those elements in a
document, valid XML documents can take advantage of certain advanced features of
XML that are not available to merely well-formed documents due to their lack of a DTD
or XML Schema.

12 Define well-formed documents. C405.1 BTL1

An XML document is well formed if it follows all the preceding syntax rules of XML. On
the other hand, if it includes inappropriate markup or characters that cannot be
processed by XML parsers, the document cannot be considered well formed. It goes
without saying that an XML document can’t be partially well formed.

13 Define Namespaces in XML. C405.1 BTL1

The xmlns attribute in the second <table> element gives the f: prefix a qualified
namespace. When a namespace is defined for an element, all child elements with the
same prefix are associated with the same namespace. Namespaces can also be declared
in the XML root element: <root. xmlns:h="http://www.w3.org/TR/html4/"

14 Define DTD Attributes C405.1 BTL1

XML attributes are name/value pairs that are used as metadata to describe XML
elements. XML attributes are very similar to HTML attributes. In HTML, src is an
attribute of the img tag, as shown in the following example:
<img src=”images/imagename.gif” width=”10” height=”20”>
In this example, width and height are also attributes of the img tag.

15 Define DTD Entities C405.1 BTL1

Entities in DTDs are storage units. They can also be considered placeholders. Entities
are special markups that contain content for insertion into the XML document. Usually
this will be some type of information that is bulky or repetitive. Entities make this type
of information more easily handled because the DTD author can use them to indicate
where the information should be inserted in the XML document.
16 What are the DTD Drawbacks and Alternatives? C405.1 BTL1
There are several drawbacks that limit the ability of DTDs to meet these growing and
changing validation needs.
First and foremost, DTDs are composed of non-XML syntax. Given that one of the
central tenets of XML is that it be totally extensible, it may not seem to make a lot of
sense that this is the case for DTDs.
Additionally, there can only be a single DTD per document. It is true that there can be
internal and external subsets of DTDs, but there can only be a single DTD referenced. In
the modern programming world, we are used to being able to draw the programming
constructs we use from different modules or classes.

17 How to create XML Schemas? C405.1 BTL1

Authoring an XML schema consists of declaring elements and attributes as well as the
“properties” of those elements and attributes. We will begin our look at authoring XML
schemas by working our way from the least-complex example to the most-complex
example. Because attributes may not contain other attributes or elements, we will
start there.

18 How to create XML Schemas? C405.1 BTL1

Authoring an XML schema consists of declaring elements and attributes as well as the
“properties” of those elements and attributes. We will begin our look at authoring XML
schemas by working our way from the least-complex example to the most-complex
example. Because attributes may not contain other attributes or elements, we will
start there.

19 Define XPath. C405.1 BTL1

The XML Path Language (XPath) is a standard for creating expressions that can be used
to find specific pieces of information within an XML document. XPath expressions are
used by both XSLT (for which XPath provides the core functionality) and XPointer to
locate a set of nodes. To understand how XPath works, it helps to imagine an XML
document as a tree of nodes consisting of both elements and attributes.

20 Define XPointer. C405.1 BTL1

The XML Pointer Language (XPointer), currently in the candidate recommendation
stage of the W3C approval process, builds on the XPath specification. An XPointer uses
location steps the same as XPath but with two major differences: Because an XPointer
describes a location within an external document, an XPointer can target a point within
that XML document or a range within the target XML document. You can find the
 complete specification at http://www.w3.org/TR/xptr.

21 Define XLink. C405.1 BTL1

The anchor element, <a>, within HTML indicates a link to another resource on an HTML
page. This could be a location within the same document or a document located
elsewhere. In HTML terms, the anchor element creates a hyperlink to another location.
The hyperlink can either appear as straight text, a clickable image, or a combination of
both. Although HTML anchor elements contain a lot of functionality, they are still
limiting— they require the use of the anchor element (<a>) itself, and they basically sit
there waiting for someone to click them before navigating to the specified location.

22 Describe targeting Namespaces. C405.1 BTL1

You can view an XML schema as a collection of type definitions and element
declarations targeted for a specific namespace. Namespaces allow us to distinguish
element declarations and type definitions of one schema from another. We can assign
an intended namespace for an XML schema by using the targetNamespace attribute on
the <schema> element. By assigning a target namespace for the schema, we indicate
that an XML document whose elements are declared as belonging to the schema’s
namespace should be validated against the XML schema.

23 How to model groups? C405.1 BTL1

A model group, at least in terms of a schema definition, is a logically grouped set of
elements. A model group within the XML Schema Definition Language consists of a
“compositor” and a list of “particles” or element declarations). A model group can be
constructed using one of the following XML Schema Definition elements:
• <all>
• <choice>
• <sequence>

24 What is anonymous type declaration? C405.1 BTL1

If you look closely, you’ll see the
declaration of a <Name> element that does not have a type attribute specified.
Instead, the <element> element, itself, contains a <simpleType> element without a
name attribute specified. This is known as an “anonymous” type definition.
25 How to declare simple types? C405.1 BTL1
Sometimes, it’s not necessary to declare a complex element type within an XML
schema. In these cases, you can use the <simpleType> element of the XML Schema
Definition Language.

26 Define the structure of a Document Type Definition? C405.1 BTL1

The structure of a DTD consists of a Document Type Declaration, elements, attributes,
entities, and several other minor keywords. We will take a look at each of these topics,
in that order. As we progress from topic to topic, we will follow a mini case study about
the use of XML to store employee records by the Human Resources department of a
fictitious company.

27 Define Ranges in XPointer. C405.1 BTL1

An XPointer range defines just that—a range consisting of a start point and an
endpoint. A range will contain the XML between the start point and endpoint but does
not necessarily have to consist of neat subtrees of an XML document. A range can
extend over multiple branches of an XML document. The only criterion is that the start
point and endpoint must be valid.

28 Define Simple Links. C405.1 BTL1

A simple link combines the functionality provided by the different pieces available
through an extended link together into a shorthand notation. A simple link consists of
an xlink:type attribute with a value of simple and, optionally, an xlink:href attribute
with a specified value. Simple links play multiple roles in linking documents. For
instance, the simple link, itself, acts as a resource XLink type for the local document. It
is the combination of this functionality that shortens the XLink definition for a simple
link.

29 Define Extended Links. C405.1 BTL1

Within the XML Linking Language, extended links give you the ability to specify
relationships between an unlimited number of resources, both local and remote. In
addition, these links can involve multiple paths between the linked resources. Local
resources are part of the actual extended link, whereas remote resources identify
external resources to the link. An out-of-line link is created when there are no local
resources at all for a link.

30 Define the rules for well formed documents in XML NOV/DEC 2016 C405.1 BTL1
An XML document is well formed if it follows all the preceding syntax rules of XML. On
the other hand, if it includes inappropriate markup or characters that cannot be
processed by XML parsers, the document cannot be considered well formed. It goes
without saying that an XML document can’t be partially well formed.
31 What is a XML namespace? NOV/DEC 2016 C405.1 BTL1
XML namespaces are used for providing uniquely named elements and attributes in
an XML document. They are defined in a W3C recommendation. An XML instance may
contain element or attribute names from more than one XML vocabulary.

32 What is XML? NOV/DEC 2017 C405.1 BTL1

In computing, Extensible Markup Language (XML) is a markup language that defines a
set of rules for encoding documents in a format that is both human-readable and
machine-readable through use of tags that can be created and defined by users.
33 What is XML document prolog? NOV/DEC 2017 C405.1 BTL1

The prolog refers to the information that appears before the start tag of the document
or root element. It includes information that applies to the document as a whole, such
as character encoding, document structure, and style sheets.

34 Define service Component.(MAY/JUNE 2018) C405.1 BTL1

Service-component architecture (SCA) Service-component architecture (SCA) is a group
of specifications intended for the development of applications based on service-
oriented architecture (SOA), which defines how computing entities interact to perform
work for each other.

PART-B

Q.No Questions CO Bloom’s

level
1 1. Explain XML document structure in detail (Ron Schmelzer Page 39- C405.1 BTL5
50)

2 2. Explain Namespaces in Detail. (Ron Schmelzer Page 58-61) (NOV/DEC C405.1 BTL5
2017)

3 3. Explain Document Type Definition in detail (Ron Schmelzer Page 67- C405.1 BTL5
103)

4 4. How to create XML Schemas? Explain in detail (Ron Schmelzer Page C405.1 BTL5
116-159) (NOV/DEC 2017)

5 5. Explain X-Files in detail (Ron Schmelzer Page 169-219) C405.1 BTL5

6 Create a document type definition that defines the structure for email C405.1 BTL6
message, further create a XML document that reference to the created
document type definitions
7 Explain with examples internal and external DTD (8) [NOV/DEC 2016] C405.1 BTL5
8 Explain in detail about XML schema and XML files. (16) [NOV/DEC C405.1 BTL5
2016]

9 Explain the Characteristics of SOA in Detail) [MAY/JUNE 2017] C405.1 BTL5

10 Discuss the Principles of service orientation in detail[MAY/JUNE 2017] C405.1 BTL6

 UNIT-2

BUILDING XML- BASED APPLICATIONS 9

Parsing XML – using DOM, SAX – XML Transformation and XSL – XSL Formatting – Modeling Databases
in XML.

PART-A
Questions CO Bloo
Q.No m’s
Level
1 What is DOM? C405.2 BTL1
The Document Object Model (DOM) is the model that describes how all elements
in an HTML age, like input fields, images, paragraphs etc., are related to the
topmost structure: the document itself. By calling the element by its proper DOM
name, we can influence it.

2 What are the disadvantages of Using DOM? C405.2 BTL1

One of the big issues is that DOM can be memory intensive. As mentioned earlier,
when an XML document is loaded, the entire document is read in at once. A large
document will require a large amount of memory to represent it. Other parsing
methods, such as SAX, don’t read in the entire document, so they are better in
terms of memory efficiency for some applications
3 1. Define DOM Levels C405.2 BTL1
The DOM working group works on phases (or levels) of the specification. At the
time of this writing, three levels are in the works. The DOM Level 1 and Level 2
specifications are W3C recommendations. This means that the specifications are
final and can be implemented without fear of things changing. Level 1 allows
traversal of an XML document as well as the manipulation of the content in that
document. Level 2 extends Level 1 with additional features such as namespace
support, events, ranges, and so on. Level 3 is currently a working draft.

4 Describe Java Bindings C405.2 BTL1

If you think about it, a class and a schema perform similar functions. Classes
describe Java objects, whereas schemas describe XML documents. An object is an
instance of a class, and a document follows a schema. The diagram in Figure 7.3
illustrates the relationships between schemas, classes, documents, and objects.
5 Describe SAX implementation. C405.2 BTL1
SAX implementations include all the underlying classes needed to parse
documents. The SAX API by itself does not include these underlying classes, so
you will need to obtain an implementation You can find a list of implementations
at http://www.megginson.com/SAX/applications. html. When looking for an
implementation, you might want to consider several factors, such as version
support, validating/nonvalidating, DTD/XML Schema support, and so on.

6 Define DOM Core C405.2 BTL1

The DOM core is available in DOM Level 1 and beyond. It permits you to create
and manipulate XML documents in memory. As mentioned earlier, DOM is a tree
structure that represents elements, attributes, and content.

7 Define DOM interface. NOV/DEC 17 C405.2 BTL1

A number of extended interfaces are not mandatory but may be available in some
implementations. These interfaces are beyond DOM Level 1 and are discussed
later in this chapter. You can determine whether these interfaces are supported
by calling the hasFeature() method of the DOMImplementation interface. You can
use the arguments “XML” and “2.0” for the feature and version parameters of the
hasFeature() method. For a detailed explanation, refer to the DOM specification
on the W3C Web site.

8 Define JAXB solutions. C405.2 BTL1

In the JAXB solution, we will model the rental property database as an XML
document. First we need to review the database schema. After reviewing the
schema, we will develop our desired XML document based on an XML schema.
After we have the XML schema developed, we can create the JAXB binding
schema. The JAXB binding schema contains instructions on how to bind the XML
 schema to a Java class. We’ll take the JAXB binding schema and generate the
appropriate Java classes.

9 Define DOM Traversal. C405.2 BTL1

Traversal is a convenient way to walk through a DOM tree and select specific
nodes. This is useful when you want to find certain elements and perform
operations on them.

10 Define DOM Range C405.2 BTL1

A range consists of two boundary points corresponding to the start and the end
of the range. A boundary point’s position in a Document or DocumentFragment
tree can be characterized by a node and an offset. The node is the container of
the boundary point and its position. The container and its ancestors are the
ancestor containers of the boundary point and its position. The offset within the
node is the offset of the boundary point and its position. If the container is an
Attr, Document, DocumentFragment, Element, or EntityReference node, the
offset is between its child nodes.

11 Describe JDOM. BTL1

JDOM was designed specifically for Java. In contrast, DOM is purely an interface
specification
independent of any language. For example, a Java parser can leverage standard
Java types and collections, such as the String class and the Collections API. The
goal of W3C DOM is to be language independent, which works but can add a lot
of unnecessary complications
12 2. Define Java Binding C405.2 BTL1
If you think about it, a class and a schema perform similar functions. Classes
describe Java objects, whereas schemas describe XML documents. An object is an
instance of a class, and a document follows a schema. The diagram in Figure 7.3
illustrates the relationships between schemas, classes, documents, and objects.

13 What is SAX? C405.2 BTL1

SAX by itself is just an API, and a number of implementations are available from
many of the familiar sources. The most commonly used parsers are Xerces from
the Apache XML project and Java API for XML Processing (JAXP) from Sun
Microsystems. A good list of parsers can be found at
http://www.xmlsoftware.com.
14 Define SAX packages C405.2 BTL1
The SAX 2.0 API is comprised of two standard packages and one extension
package. The standard packages are org.xml.sax and org.xml.helpers. The
org.xml.sax package contains the basic classes, interfaces, and exceptions needed
for parsing documents.

15 What is Entity references? C405.2 BTL1

SAX parsers will resolve entity references automatically. However, there are cases
when you might want to resolve an entity reference yourself. In the following
example, we will define an entity for hardcover books. It will be referenced as
&hc; and defined in our DTD. If we use an HTTP URL to define the entity, the SAX
parser will go out to the network to resolve it. What we want to do here is resolve
the entity using a local file. We can accomplish this using an EntityResolver

16 Define Lexical Events. C405.2 BTL1

LexicalHandler is part of the org.xml.sax.ext package, which is not necessarily
supported by all SAX implementations. Xerces, of course, provides support for the
extension package. Notice that we are explicitly implementing LexicalHandler.
This is necessary because DefaultHandler does not implement LexicalHandler. We
must fill in all methods of LexicalHandler whether we are interested in them or
not.

17 What are the Activities in the life cycle? C405.2 BTL1

• Requirements specification
• Architectural design
• Detailed design
• Coding and unit testing
• Integration and testing
Maintenance

18 Define Handling Errors. C405.2 BTL1

The Locator interface can give us the parse position within a ContentHandler
method. The position information includes line number and column number. It is
important to note that the Locator object should not be used in any other
methods, including ErrorHandler methods. Fortunately, ErrorHandler methods
 supply a SAXParseException object that can also give us position information.

19 Describe SAX implementation. C405.2 BTL1

SAX implementations include all the underlying classes needed to parse
documents. The SAX API by itself does not include these underlying classes, so
you will need to obtain an implementation. You can find a list of implementations
at http://www.megginson.com/SAX/applications html. When looking for an
implementation, you might want to consider several factors, such as version
support, validating/nonvalidating, DTD/XML Schema support, and so on

20 Describe Basic document structure in XSL formatting objects. C405.2 BTL1

An XML-FO document follows the syntax rules of XML; as a result, it is well
formed. XSL-FO elements use the following namespace:
http://www.w3.org/1999/XSL/Format
The following code snippet shows the basic document setup for XSL-FO:
<?xml version=”1.0” encoding=”utf-8”?>
<fo:root xmlns:fo=”http://www.w3.org/1999/XSL/Format”>
<!-- layout master set -->
<!-- page masters: size and layout -->
<!-- page sequences and content -->
</fo:root>

21 How to generate a PDF document? C405.2 BTL1

Follow these steps to generate a PDF document from simple.fo:
1. Open an MS-DOS window.
2. Move to the directory <install_dir>\ch9_xsl\xsl_fo\.
3. Set up the Java classpath by typing setpaths.
4. Execute Apache-FOP by typing fop simple.fo simple.pdf.
The Apache-FOP formatter now reads the input file simple.fo and generates the
output file simple.pdf.
5. View the simple.pdf file in Adobe Acrobat Reader. Your screen should
resemble
22 Describe XML Database Mapping? C405.2 BTL1
The first type of XML database solution provides a mapping between the XML
document and the database fields. The system dynamically converts SQL result
sets to XML documents. Depending on the sophistication of the product, it may
provide a graphical tool to map the database fields to the desired XML elements.
Other tools support a configuration file that defines the mapping. These tools
continue to store the information in relational database management system
(RDBMS) format. They simply provide an XML conversion process that is normally
implemented as a server-side Web application.

23 How to create JAXB binding schema? C405.2 BTL1

Now that the DTD is defined for our document, we need to define the JAXB
binding schema. The JAXB binding schema is an XML document that contains
instructions on how to bind a DTD to a Java class. Using the JAXB binding schema,
we can define the names of the generated Java classes, map element names to
specific properties in the Java class, and provide the mapping rules for attributes.
The following code example informs the JAXB system that the element
<rental_property_list> should be mapped to a Java class and that it is the root
element for the XML document:
<element name=”rental_property_list” type=”class” root=”true”/>

24 How to generate the JAXB classes based on schema? C405.2 BTL1

Now we are ready to generate the Java source files based on our schemas. JAXB
provides a schema compiler for generating the Java source files. The schema
compiler takes as input the DTD and the JAXB binding schema. Figure 10.6
illustrates the process.

25 How to represent the XML Document? C405.2 BTL1

In any markup language, the first element to appear is called the "root element",
which defines what kind of document the file will be. In an HTML file, the <html>
tag is the root element. An HTML file will always have the HTML element as the
root element, while in an XML file, it can be anything.
 Eg:
<phonebook>
<number>
</number>
<name>
</name>
</phonebook>

26 3. Mention any 3 XML Parsers C405.2 BTL1

SAX (Simple API for XML) Parser
DOM (Document Object Model) Parser and
XSLT (XML Style Sheet) Parsers.

27 What is the purpose of the XML DTD C405.2 BTL1

The purpose of a DTD is to define the structure of an XML document. It defines
the structure with a list of legal elements:
<!DOCTYPE note [ <!ELEMENT note (to,from,heading,body)> <!ELEMENT to
(#PCDATA)>
<!ELEMENT from (#PCDATA)> <!ELEMENT heading (#PCDATA)> <!ELEMENT body
(#PCDATA)> ]>

28 What is XML Prolog C405.2 BTL1

XML file always starts with a Prolog. The minimal prolog contains a declaration
that identifies the document as an XML document, like this:
<?xml version="1.0"?>
The declaration may also contain additional information, like this:
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
.

29 What is XSL Programming? C405.2 BTL1

XSL (XML Stylesheet) Programming is the Next Generation of the CSS (Cascading
Style Sheet Programming). In CSS, users can use certain style tags which the
browsers can understand and are predefined by W3 consortium. XSL takes ths to
one step ahead and users can define any tags in the XML file. XML sheets can help
in showing the same data in different formats.
<?xml-stylesheet href="doc.xsl" type="text/xsl"?>
30 What is XSLT? C405.2 BTL1
XSLT stands for XSL Transformations
XSLT is the most important part of XSL
XSLT transforms an XML document into another XML document
XSLT uses XPath to navigate in XML documents
XSLT is a W3C Recommendation

31 Define XML parser [NOV/DEC 2016] C405.2 BTL1

An XML Parser is a parser that is designed to readXML and create a way for
programs to use XML. There are different types, and each has its advantages.
Unless a program simply and blindly copies the whole XML file as a unit,
every program must implement or call on anXML parser

32 Outline a simple style sheet using XSL [NOV/DEC 2016] C405.2 BTL2
XSL is a language for expressing style sheets. An XSL style sheet is, like
with CSS, a file that describes how to display an XML document of a given
type. XSL shares the functionality and is compatible with CSS2 (although it
uses a different syntax). It also adds

Example Style Sheet:

<xsl:template match="FX">
<fo:block font-weight="bold">
<xsl:apply-templates/>
</fo:block>
</xsl:template>

33 List the disadvantage of SAX [NOV/DEC 17] C405.2 BTL1

• SAX is similar to a one-pass compiler. After it reads part of the document, it

cannot navigate backward to reread the data it has processed, unless you start all
over again.

• Because SAX does not store the data that it has processed, you cannot modify
this data and store it back in the original document.

• Because SAX does not create an in-memory document structure, you cannot
build an XML document by using a SAX parser.

34 Define the characteristics of Orchestration service layer. (MAY/JUNE 2018) C405.2 BTL1
The orchestration service layer introduces a parent level of abstraction that alleviates the
need for other services to manage interaction details required to ensure that service
operations are executed in a specific sequence. Within the orchestration service layer,
process services compose other services that provide specific sets of functions,
independent of the business rules and scenario-specific logic required to execute a
process instance.
32 Define soap message. .(MAY/JUNE 2018) C405.2 BTL1

A SOAP message is an ordinary XML document containing the following

elements −

• Envelope − Defines the start and the end of the message. It is a mandatory
element.
• Header − Contains any optional attributes of the message used in
processing the message, either at an intermediary point or at the ultimate
end-point. It is an optional element.
• Body − Contains the XML data comprising the message being sent. It is a
mandatory element.
• Fault − An optional Fault element that provides information about errors
that occur while processing the message.

PART-B

Q.No Questions CO Bloom’s

level
1 What is DOM? Explain Parsing XML using DOM (Ron Schmelzer C405.2 BTL5
Page 267-296)

2 Explain Parsing using SAX (Ron Schmelzer Page 309-331) C405.2 BTL5

3 Explain XML transformation with XSL (Ron Schmelzer Page 345-376) C405.2 BTL5

4 Explain modelling databases in XML in detail (Ron Schmelzer Page 409- C405.2 BTL5
437)

5 Explain XSL formatting objects in detail (Ron Schmelzer Page 377-391) C405.2 BTL6

6 Compare DOM and SAX based XML parsing. (6) [NOV/DEC 2016] C405.2 BTL5

7 Explain SAX based parsing with example. (10) [NOV/DEC 2016] C405.2 BTL5

8 Give a brief note on Modeling database in XML (8) [NOV/DEC 2016] C405.2 BTL5
9 With example formulate how XSLT can transform an XML C405.2 BTL6
document into HTML.(8) [NOV/DEC 2016]

10 Discuss on the protocol of Atomoic Transaction in detail. .(MAY/JUNE C405.2 BTL6

2018)

11 Explain the elements of Web services platform in detail. .(MAY/JUNE C405.2 BTL5
2018)
 UNIT-3

SERVICE ORIENTED ARCHITECTURE 9

Characteristics of SOA, Comparing SOA with Client-Server and Distributed architectures – Benefits of
SOA -- Principles of Service orientation – Service layers.

PART-A

Questions CO Bloo
Q.No m’s
Level
1 What is architecture? C405.3 BTL1
Application architecture is to an application development team what a
blueprint is to a team of construction workers. Different organizations document
different levels of application architecture.

2 Define Service-oriented architecture C405.3 BTL1

An SOA can refer to application architecture or the approach used to standardize

technical architecture across the enterprise

3 Define Client / Server architecture C405.3 BTL1

Mainframe back-ends served thin clients, are considered an
implementation of the single-tier client-server architecture Mainframe systems
natively supported both synchronous and asynchronous communication. The
latter approach was used primarily to allow the server to continuously receive
characters from the terminal in response to individual key-strokes. Only upon
certain conditions would the server actually respond.

4 Define Distributed Internet architecture C405.3 BTL1

Distributing application logic among multiple components (some residing
on the client, others on the server) reduced deployment headaches by centralizing
a greater amount of the logic on servers. Server-side components, now located on
dedicated application servers, would then share and manage pools of database
connections, alleviating the burden of concurrent usage on the database server A
single connection could easily facilitate multiple users.
5 Define SOA Characteristics [NOV/DEC 17] C405.3 BTL1

• Services are discoverable and dynamically bound.

• Services are self-contained and modular.
• Services stress interoperability.
• Services are loosely coupled.
• Services have a network-addressable interface.
• Services have coarse-grained interfaces.
• Services are location-transparent.
• Services are composable.
• Service-oriented architecture supports self-healing.

6 Define Coarse-Grained Services C405.3 BTL1

A service-based system controls the network access to the objects within the service
through a set of coarse-grained interfaces. A service may still be implemented as a set of
fine-grained objects, but the objects themselves are not accessible over a network
connection. A service implemented as objects has one or more coarse-grained objects that
act as distributed façades. These objects are accessible over the network and provide
access to the internal object state from external consumers of the service. However,
objects internal to the service communicate directly with each other within a single
machine, not across a network connection
7 Define Service Component C405.3 BTL1
This is the true heart of the SOA. The Service Component is that logical
unit of code which implements the functionality to support the Service. The
Service Component exposes one or more Services. A Service Component is also
usually associated with a data store of some kind. This can contain data about a
fundamental data type, control data, process, data, etc depending on the nature of
the particular service component.

8 Define Service-component-level Testing C405.3 BTL1

Service-component-level testing or Unit testing, is normally performed by
the developers to test that the code not only successfully compiles, but the basic
functionality of the components and functions within a service are working as
specified. The primary goal of Component testing is to take the smallest piece of
testable software in the application, isolate it from the remainder of the code, and
determine whether it behaves exactly as you expect. Each Component is tested
separately before integrating it into a service or services.
9 Define Process/Orchestration-level Testing C405.3 BTL1
Process/Orchestration testing ensures services are operating collectively as
specified. This phase of testing would cover business logic, sequencing, exception
handling and process decomposition (including service and process reuse).

10 Define Security Testing C405.3 BTL1

As SOA evolves and grows within your organization, the profile and
necessity of Security testing will increase. Today, many organizations perform an
inadequate amount of penetration testing at the very end of a project. SOA
combined with Government and Regulatory compliance, will require Security
testing activities to be incorporated into the entire project life cycle.

11 Explain Legacy System Adapter C405.3 BTL2

It is my personal opinion that any time a Service Component needs to
interface to a legacy system, that an Adapter Pattern should be used. This Adapter
performs a number of tasks. Its primary function is to convert to/from data
formats spoken by the legacy system and the common data formats used by the
Foundational Service Components. In order to perform the conversions, it may be
necessary for an adapter to interface with many Service Components in order to
perform data enrichment or break data apart into its fundamental data types.

12 Define Composite Service Component C405.3 BTL1

A Composite Service Component is a component which combines the
functionality of one or more other Foundational or Composite Service
Components. It may also encapsulate additional functional and data enrichment,
business process, etc. In some cases, a Composite Service Component may be
purpose built to support one and only one business process or application, where
it makes sense to encapsulate a piece of reusable functionality on the server side
instead of in the application.

13 Define WSDL? C405.3 BTL1

SOA services have self-describing interfaces in platform-independent
XML documents. Web Services Description Language (WSDL) is the standard
used to describe the services.

14 Define XSD? C405.3 BTL1

SOA services communicate with messages formally defined via XML
Schema (also called XSD). Communication among consumers and providers or
services typically happens in heterogeneous environments, with little or no
knowledge about the provider. Messages between services can be viewed as key
business documents processed in an enterprise.
15 Define UDDI? C405.3 BTL1
SOA services are maintained in the enterprise by a registry that acts as a
directory listing. Applications can look up the services in the registry and invoke
the service. Universal Description, Definition, and Integration (UDDI) is the
standard used for service registry.

16 Explain about QOS? C405.3 BTL2

Each SOA service has a quality of service (QoS) associated with it. Some
of the key QoS elements are security requirements, such as authentication and
authorization, reliable messaging, and policies regarding who can invoke services.

17 Define Service Proxy? C405.3 BTL1

The service provider supplies a service proxy to the service consumer. The
service consumer executes the request by calling an API function on the proxy. It
then formats the request message and executes the request on behalf of the
consumer. The service proxy is a convenience entity for the service consumer. It
is not required; the service consumer developer could write the necessary
software for accessing the service directly.

18 Define Service-Orientation and Interoperability C405.3 BTL1

Service-oriented computing, stating that services must be interoperable is
just about as evident as stating that services must exist. Each of the eight
principles supports or contributes to interoperability in some manner.

19 Define service Loose coupling C405.3 BTL1

The principle of Service Loose Coupling promotes the independent design
and evolution of a service’s logic and implementation while still guaranteeing
baseline interoperability with consumers that have come to rely on the service’s
capabilities.

20 What is CCT C405.3 BTL1

CCT as an engineering tool giving one a rough measure of learnability and
difficulty combined with a detailed description of user behavior. This can then be
used by analysts employing their professional expertise
21 Define Business layer C405.3 BTL1
Business layer is responsible for supporting business process life cycle.
Business process lifecycle consists of five stages: design, model, simulate,
monitor, manage, and optimize business processes. Business layer users are either
business analysts, or business managers. Business analysts create the initial drafts
of the business processes, and business managers will manage and monitor those
business processes.

22 Define Business services layer C405.3 BTL1

Business services layer holds orchestration and choreography engines under governance
mechanisms to map business processes to composing Web services. Orchestration and
choreography engines are the mapping enablers of business processes into executable
services. Web services are stateless services that can not maintain business logic,
operation flow, or user state; so, the need of an orchestration layer to include business
logic is addressed. Orchestration and choreography engines maintain business process
workflow logic, performance requirements, and system/user state. Business services layer
has access to business rules repository
23 What is Session ID? A session ID is a unique identification C405.3 BTL1

string usually a long, random and alpha-numeric string, that is

transmitted between the client and the server. Session IDs are usually stored in
the cookies, URLs (in case url rewriting) and hidden fields of Web pages.

24 Define Composite Service Component C405.3 BTL1

A Composite Service Component is a component which combines the
functionality of one or more other Foundational or Composite Service
Components. It may also encapsulate additional functional and data enrichment,
business process, etc. In some cases, a Composite Service Component may be
purpose built to support one and only one business process or application, where
it makes sense to encapsulate a piece of reusable functionality on the server side
instead of in the application.

25 List out some characteristics of contemporary SOA. [NOV/DEC 2016] C405.3 BTL1
It is at the core of the service-oriented computing platform.
It increases quality of service.
It is fundamentally autonomous and based on open standards.
It supports vendor diversity and fosters intrinsic interoperability.
It promotes discovery and It promotes federation.
It promotes architectural composability.
It supports a service-oriented business modeling paradigm.
 It implements layers of abstraction.
It is a building block.
It is an evolution.
It is still maturing.

26 How loose coupling achieved in SOA? [NOV/DEC 2016] C405.3 BTL1

The principle of Service Loose Coupling promotes the independent design and
evolution of a service’s logic and implementation while still guaranteeing
baseline interoperability with consumers that have come to rely on the service’s
capabilities.
In order to ensure that the service contract is not tightly coupled to the service
consumers and to the underlying service logic and implementation. This results in
service contracts that could be freely evolved without affecting either the service
consumers or the service implementation.

27 What is Text based communication & types? APR/MAY2017 C405.3 BTL1

Text-based communication is familiar to most people, in that they will have
written and received letters. However, the style of letter writing and that of face-to
face communication are very different. The text-based communication in
groupware systems is acting as a speech substitute, and, thus, there are some
problems adapting
between the two media.
There are four types of textual communication in current groupware:
discrete – directed message as in email. There is no explicit connection between
different
messages, except in so far as the text of the message refers to a previous one.
linear – participants’ messages are added in (usually temporal) order to the end of
a
single transcript.
non-linear – when messages are linked to one another in a hypertext fashion.
spatial – where messages are arranged on a two-dimensional surface.

28 Define XSD? C405.3 BTL1

SOA services communicate with messages formally defined via XML
Schema (also called XSD). Communication among consumers and providers or
services typically happens in heterogeneous environments, with little or no
knowledge about the provider. Messages between services can be viewed as key
business documents processed in an enterprise.
29 What are the fundamental parts of SOA framework?[ NOV/DEC 2017] C405.3 BTL1

• Enterprise service bus (ESB)

• Service registry
• Business processes
• MDM hub
• Data management

30 What is the responsibility of service(MAY/JUNE 2018) C405.3 BTL1

These components are responsible for realizing the functionality of services. The middle
layer is the Service Layer, which is where exposed services (both individual and
composite services) carrying out business functions reside.
 PART-B

Q.No Questions CO Bloom’s

level
1 Explain how SOA can be compared to Client server architecture C405.3 BTL5

2 Describe the principles of service orientation C405.3 BTL5

3 Explain in detail about SOA components and how are they C405.3 BTL5
interrelate.
4 Decide how the ‘golden rules’ and heuristic help interface designers C405.3 BTL5
take account of cognitive psychology? Illustrate your answer with the
design of Microsoft office word. Page no: 282 NOV/DEC2017

5 Explain about Hypertext and its characteristics. C405.3 BTL5

6 What is distributed internet architecture? Compare it with SOA C405.3 BTL4

7 Explain the anatomy of service oriented architecture C405.3 BTL4

8 Describe how SOA can be compared to distributed internet C405.3 BTL5

architectures
9 Explain briefly about web services as component wrappers C405.3 BTL6

10 Compare SOA with client server and distributed internet C405.3 BTL5
architectures. (MAY/JUNE 2018)

11 Propose the various principles of service orientation in detail. C405.3 BTL6

(MAY/JUNE 2018)
 UNIT IV
Part – A

Blooms
S. Course
Taxano
N Question Outco
my
o. me
Level
1 What is Web Services?
Web Services can convert your applications into Web-
applications. Web Services are published, found, and used through the C405.4
Web.

BTLI

2 What are Web Services?

• Web services are application components
C405.4 BTLI
• Web services communicate using open protocols
• Web services are self-contained and self-describing
• Web services can be discovered using UDDI
 • Web services can be used by other applications
• XML is the basis for Web services
• 3. List the Web services platform elements:
• SOAP (Simple Object Access Protocol)
• UDDI (Universal Description, Discovery and Integration)
• WSDL (Web Services Description Language)

3 Define Web API

Web API is a development in Web services (in a movement
called Web 2.0) where emphasis has been moving away from SOAP
based services towards Representational State Transfer (REST) based
C405.4 BTLI
communications.REST services do not require XML, SOAP, or
WSDL service-API definitions.
Web APIs allow the combination of multiple Web services into new
applications known as mashups.

4 Define Agents and Services

A Web service is an abstract notion that must be implemented
by a concrete agent. The agent is the concrete piece of software or
hardware that sends and receives messages, while the service is the
resource characterized by the abstract set of functionality that is C405.4 BTLI
provided. To illustrate this distinction, you might implement a
particular Web service using one agent one day, and a different agent
the next day with the same functionality. Although the agent may
have changed, the Web service remains the same.

5 Define Soap message.

A SOAP message is specified as an XML Information Set . While all SOAP C405.4 BTLI
message examples in this document are shown using XML 1.0 syntax, other
representations MAY be used to transmit SOAP messages between nodes
6 Define Request-Response
Request-Response is a pattern in which the service consumer
uses configured client software to issue an invocation request to a C405.4 BTLI
service provided by the service provider. The request results in an
optional response

7 Define Subscribe-Push
A third pattern for interaction is called Subscribe-Push, shown
in Figure 4-3. In this pattern, one or more clients register
subscriptions with a service to receive messages based on some
C405.4 BTLI
criteria. Regardless of the criteria, the externally visible pattern
remains the same. Subscriptions may remain in effect over long
periods before being canceled or revoked. A subscription may, in
some cases, also register another service endpoint to receive
notifications.
8 Data paging
Some services automatically facilitate the paging of large data
C405.4 BTLI
sets, enabling developers to focus on core application business logic
instead of worrying about basic data management infrastructure.

9 Define Coordination Model

The Coordination model provides integrated service to each
C405.4 BTLI
key customer group. The integration results from sharing key data
across the business units to present a common fact to the customer.

10 Define Atomic Service Transaction

Atomic Service Transaction is the name of a design pattern
authored by Thomas Erl and published as part of the SOA Design
C405.4 BTLI
Patterns catalog. Within the catalog this pattern is further categorized
as one of the Composition Implementation Patterns. The icon used to
identify Atomic Service Transaction

11 List the Atomic Transaction Protocols

A Completion protocol which is typically used to initiate the
commit or abort states of the transaction. The Durable 2PC protocol
C405.4 BTLI
for which services representing permanent data repositories should
register. The Volatile 2PC protocol to be used by services managing
non-persistent (temporary) data.

12 Define atomic transaction coordinator

The atomic transaction coordinator plays a key role in managing the C405.4 BTLI
participants of the transaction process, and in deciding the transaction’s
ultimate outcome
13 Define Business activity
Business activities consist of long-running, complex
transactions involving numerous services. Hours, days, or even weeks
C405.4 BTLI
can pass before a business activity is able to complete. During this
period, the activity can perform numerous tasks that involve many
participants.

14 Define Orchestration
Refers to an executable business process that may interact
with both internal and external Web services. Orchestration describes
how Web services can interact at the message level, including the
C405.4 BTLI
business logic and execution order of the interactions. These
interactions may span applications and/or organizations, and result in
a long-lived, transactional process. With orchestration, the process is
always controlled from the perspective of one of the business parties.

15 Define Choreography C405.4 BTLI

 More collaborative in nature, where each party involved in the
process describes the part they play in the interaction. Choreography
tracks the sequence of messages that may involve multiple parties and
multiple sources. It is associated with the public message exchanges
that occur between multiple Web services.

16 Define Service Layers

When building various types of services, it becomes evident
that they can be categorized depending on: - the type of logic they
encapsulate - the extent of reuse potential this logic has - how this
C405.4 BTLI
logic relates to existing domains within the enterprise As a result,
there are three common service classifications that represent the
primary service models used in SOA projects: - Entity Services - Task
Services - Utility Services

17 Define Application Services layer.

Application services layer holds applications exposed as services, newly
added services, and legacy applications wrapped by standard Web services
interface. Services at Application Services layer are set of stateless Web
services that perform certain task(s). Business process is the summation of C405.4 BTLI
tasks performed by one or more services of application services layer at the
sequence maintained by orchestration and choreography engines. Services
of Application Services layer are reusable among different business
processes, can be integrated in new applications, and can be extended
address new business processes
18 Service Orchestration
Service Orchestration is nothing more than a fancy title for a
program that calls web services during its execution. There’s nothing
magical or omnipotent about a ―service orchestration‖. In fact we’ll
learn later that any service orchestration implemented using BPEL is
C405.4 BTLI
also just a standard, WSDL-defined web service in its own right. In
the context of Java, a service orchestration might be a Java class that
not only constructs and calls methods on other classes but which also
invokes web services using special Java classes and interfaces
designed specifically for that purpose.

19 Define the Reply activity.

A Reply is responsible for extracting data from a process
variable and placing it into a WSDL message that is then sent back in
response to the one accepted by the preceding Receive. In fact C405.4 BTLI
syntactically, a Reply activity requires that the process have a Receive
(or equivalent) somewhere earlier in the flow of the process. Here’s
the XML syntax our BPEL Process uses to reply to the loan approval

20 ACID transactions
C405.4 BTLI
They preserve the atomicity, consistency, isolation, and
durability of the operation(s) encompassed by the transaction. This
 helps preserve the integrity of our programs’ logic execution as well
as the integrity of the data managed by those programs. Java
transaction managers are specifically designed to provide this
functionality.

21 List the types of Choreography. APR/MAY 2018

• Abstract Choreography
C405.4 BTLI
• "portable" choreography
• Concrete Choreography

22 Define Abstract Choreography.

The types of information that is exchanged, for example an
C405.4 BTLI
order sent between a buyer and a seller The sequence and conditions
under which the information is sent.

23 Define Portable Choreography.

Detailed definitions of the physical structure of the
information that is exchanged including the WSDL port types and
operations Details of the technology to be used, for example, how to
C405.4 BTLI
secure the messages and send them reliably Rules that express, as far
as possible, the conditions that are used to control the sequence of
exchange of information, in terms of, for example XPath expressions
that reference data in the messages.

24 Define Concrete Choreography.

Choreography, where all the details are specified that are
required to send a message. This extends the definition in a Portable
Choreography to include information about the "endpoints". This can C405.4 BTLI
include information such as:
The URLs that are the destinations of the messages that are sent, and
Other "endpoint" specific rules such as digital certificates to be used for
securing messages
25 Define Orchestration service
Orchestration services encapsulate the entire business
process. For example, a service containing the entire flow of the
Employer Registration" business process is an orchestration service. C405.4 BTLI
The complete registration process identifying the employer type,
determining liability and registering the employer in the database
and various other steps.
26 Define SOAP
SOAP is a method of accessing remote objects by sending
XML messages, which provides platform and language independence. C405.4 BTLI
It works over various low-level communications protocols, but the
most common is HTTP.

27 Explain about the operations in entity-centric?

GetSomething
UpdateSomething C405.4 BTLI
AddSomething
DeleteSomething

28 What are Java Servlets?

Servlets are Java technology's answer to CGI programming. They are
C405.4 BTLI
programs that run
on a Web server and build Web pages.

29 Define the term JSP EL

EL means the expression language , it is a simple language for
accessing data, it makes it
possible to easily access application data stored in JavaBeans C405.4 BTLI
components. The jsp expression
language allows a page author to access a bean using simple syntax
such as $(name).

30 Sketch the anatomy of a SOAP message. [NOV/DEC 2016]

A SOAP message is an ordinary XML document containing the

C405.4 BTLI
following elements −
Envelope − Defines the start and the end of the message. It is a
mandatory element.
 Header − Contains any optional attributes of the message used in
processing the message, either at an intermediary point or at the
ultimate end-point. It is an optional element.
Body − Contains the XML data comprising the message being sent. It
is a mandatory element.
Fault − An optional Fault element that provides information about
errors that occur while processing the message.
All these elements are declared in the default namespace for the
SOAP envelope

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://www.w3.org/2001/12/soap-envelope" SOAP-
ENV:encodingStyle="http://www.w3.org/2001/12/soap-encoding">

<SOAP-ENV:Header>
...
...
</SOAP-ENV:Header>

<SOAP-ENV:Body>
...
...
<SOAP-ENV:Fault>
...
...
</SOAP-ENV:Fault>
...
</SOAP-ENV:Body>

</SOAP_ENV:Envelope>

31 List out some primitive MEPs. [NOV/DEC 2016]

A common set of primitive MEPs are listed below C405.4 BTLI

i. Request-response
ii. Fire-and-forget
 iii. Complex MEPs

32 List Down The Basic platform blocks APR/May 2018

1.services

2.Business processes

3.Human actors

4. Events C405.4 BTLI

5.Service Descriptions, Contracts, and Policies

6.Service Compositions

7.Programs

8.Information Items, Data Items, and Data Stores

33 Define ASP.NET Web Forms APR/May 2018

ASP.NET Web Forms is a part of the ASP.NET web application framework

and is included with Visual Studio. ... Web Forms are pages that your users C405.4 BTLI
request using their browser. These pages can be written using a
combination of HTML, client-script, server controls, and server code

34 What is UDDI NOV/DEC 2017

UDDI is an XML-based standard for describing, publishing, and finding web C405.4 BTLI
services. UDDI stands for Universal Description, Discovery, and Integration.
UDDI is a specification for a distributed registry of web services

35 List any four pitfalls of SOA NOV/DEC 2017

Implementation pitfalls
• Not Invented Here Syndrome
• Versioning
• Security
Architectural/design pitfalls C405.4 BTLI
• Incorrect Granularity of Services
• SOA does not solve complexity automatically
• Big Design Upfront
• Incorrectly applied Canonical Data Model
• - Missing skills
Organizational pitfalls:
 • -Unclear ownership/Project based funding
• Ignoring culture when introducing SOA

PART B
1 Write short notes on
BTL5
a.Service descriptions. (6) b.Atomic transaction .(5) C405.4
c.Choreography.(5)

2 Discuss about different service layer in detail(16) C405.4 BTL5

3 Discuss about three service layers in detail.(16) C405.4 BTL5

4 Describe in detail about messaging with SOAP.(16) C405.4 BTL5

5 a.Write short notes on orchestration andchoreography.(10)

C405.4 BTL 5
b.Briefly discuss on application service layer.(6)

6 Explain briefly about technical requirements for orchestration and

choreography.(16) BTL6
C405.4
Discuss in detail about Orchestration and Choreography [NOV/DEC
2016]

7 Briefly explain about: BTL 6

C405.4
a.Service layer abstraction .(8) b.Application service layer.(8)

8 Describe the process of messaging with SOAP and Atomic

transaction.(16)
Explain in detail about Atomic Transaction Process with suitable C405.4 BTL5

diagrams. [NOV/DEC 2016]

9 Explain about service layer configuration

C405.4
scenarios.(16) BTL6
10 Explain about service layer abstraction and
C405.4 BTL6
orchestration service layer
11 Discuss on how SOA is related to the layers of the
C405.4
J2EE platform APR/MAY 2018 BTL5

12 Mention the benefits of JAX-RPC in detail APR/MAY

C405.4
2018 BTL5

13
C405.4 BTL5
NOV/DEC 2017
14
C405.4 BTL5
NOV/DEC 2017

UNIT V
PART A

S. Course Blooms
No Question Outcom Taxanom
. e y Level
1 What is Service-oriented analysis?
Service-oriented analysis establishes a formal analysis
process completed jointly by business analysts and technology
architects. Service modeling, a sub-process of service-oriented
C405.5
analysis, produces conceptual service definitions called service
candidates. Iterations through the service-oriented analysis and BTL1
service modeling processes result in the gradual creation of a
service inventory blueprint.
2 Write the business-centric entry points?
These business-centric entry points are:
People—Productivity though people collaboration
Process—Business process management for continuous C405.5 BTL1
innovation
Information—Delivering information as a service.

3 Write the IT-centric entry points?

These IT-centric entry points are: Reuse—Creating
C405.5 BTL1
reusable functionality Connectivity—Underlying connectivity to
support business-centric SOA

4 Define entity-centric business service.

The entity-centric business service is agnostic to any one
business process, they achieve "process logic independence" and
therefore become highly reusable. And, because they represent a
well-defined set of logic and data, they establish a level of C405.5 BTL1
abstraction and governance over a distinct business domain. This
can significantly increase the agility with which business processes
that rely on the composition of services can be altered in response
to change.”

5 List out the component specification in Service modeling

Data
Rules C405.5 BTL1
Services
Configurable profile
Variations

6 Define SOMA - Service Oriented Modeling and Architecture

Service Oriented Modeling and Architecture refers to the
general domain of service modeling that is necessary for the
creation and design of Service Oriented Architecture. Service
Oriented Modeling and Architecture covers a much larger scope C405.5 BTL1
and implements service oriented analysis and design via a
specification, designation, and actualization of services, as well as
the components that help realize those services and the flows that
can aid in the process of building such services.

7 Define Resource and services

The XML Web services architecture defines a standard
C405.5 BTL1
mechanism for making resources available via XML messaging.
Being able to access a resource by simply transmitting XML
messages over standard protocols like TCP, HTTP, or SMTP
 greatly lowers the bar for potential consumers. The term "Web
service" (or simply "service") typically refers to the piece of code
implementing the XML interface to a resource, which may
otherwise be difficult to access

8 Define Messages and operations

A message exchange is also referred to as an operation.
C405.5 BTL1
Operations are what consumers care about most since they're the
focal point of interacting with the service.

9 Define WSDL
The Web Services Description Language (WSDL) provides
an XML grammar for describing these details. WSDL picks up
where XML Schema left off by providing a way to group
messages into operations and operations into interfaces. It also
provides a way to define bindings for each interface and protocol
combination along with the endpoint address for each one. WSDL
plays an important role in the overall Web services architecture
since it describes the complete contract for application
communication Although other techniques exist for describing
Web services, the WS-I Basic Profile Version 1.0 mandates the
use of WSDL and XML Schema for describing Web services. This
helps ensure interoperability at the service description layer.
C405.5 BTL1

10 What is the responsibility of the service?

This provides the basic description of WHY the service
should exist. Services are expensive. If you cannot stand in front
C405.5 BTL1
of an executive and make a purely business-oriented case for the
existence of a service, you need to rethink it. You are doing
something wrong.
11 What rules does the service own?
This provides the basic scope of the service. In a well
devised, Enterprise SOA, you will have a rule implemented in a
C405.5 BTL1
relatively small number of services (hopefully in one service)
which makes it easier to change that rule. This means that you
need to describe the collection of rules owned by a service.

12 What style of EAI are you implementing?

The alternative is the "RPC (Remote Procedure Call)" style. If
you are passing a block of self-describing and complete data to a service,
and all that returns is "thanks... got it," then you are using the messaging
C405.5 BTL1
style. If you are passing a command (with or without parameters) and are
expecting either a set of data in response or an "OK... operation
complete" message back, then you are using the RPC style. Note that
RPC style services are more typical but, IMHO, less powerful because
they assume a real-time binding between the interacting systems
13 Is the service itempotent?
In other words, if a call to the service is duplicated, and
instead of being called once, the service is called twice with
identical parameters/payload, will the service detect the
duplication and prevent any effects on the underlying systems? C405.5 BTL1
This is very important in messaging style services, but it turns up
in RPC services as well. A service that provides idempotency is
more loosely coupled than one that does not, but it also adds to the
complexity of the service implementation.

14 What preconditions and postconditions apply to this service?

Just as in use case development, you must be able to
describe the factors that must be in place for this service to be
used. Unlike typical use case development, however, you must
describe the behavior of the service when these preconditions are C405.5 BTL1
not met. You also must describe the limitations and constraints of
the service. For example, if a service is designed to be used only
during a specific business process, then this must be described and
included in the service design.

15 What actors may use this service and how will they be
authenticated?
This is an optimistic statement, because you (a) may not
know, and (b) may not want to limit your implementation.
However, you need to consider all of the actors who can use the
C405.5 BTL1
business rule that you are encapsulating. If one of those actors
cannot use your service, you need to either find a suitable
interaction where that actor can use the rule, or create another
service that meets that actors needs. Even within the firewalls of
the data center, it is imperative that the communications between
systems be understood to be secure from mal-intentioned people.
 If your answer is "pray," then you may want to consider a new line
of work

16 List the stages of WS-Coordination

Instantiation (or activation) of a new coordinator for the
specific coordination protocol, for a particular application instance
Registration of participants with the coordinator, such that they
C405.5 BTL1
will receive that coordinator's protocol messages during (some part
of) the application's lifetime. Propagation of contextual
information between Web services that comprise the application.
An entity to drive the coordination protocol through to completion

17 Define WS-Coordination context

A coordination identifier with guaranteed global
uniqueness for an individual coordinator in the form of a URI An
address of a registration service endpoint where parties receiving a
C405.5 BTL1
context can register participants into the protocol A TTL value
which indicates for how long the context should be considered
valid Extensible protocol-specific information particular to the
actual coordination protocol supported by the coordinator

18 What data elements will be required in order to call the

service? C405.5 BTL1
Do not define the format of the calling sequence. Define the semantics of
the data element itself
19 What data elements will be returned by the service in its
acknowledgement / receipt / return?
Think of these questions as the services "data dictionary"
C405.5 BTL1
but with more constraints. Data dictionaries describe data a rest.
These points describe data in process.

20 Define task service

A task service is a form of business service with a
functional context based on a specific business process. As a C405.5 BTL1
result, task services are not generally considered agnostic and
therefore have less reuse potential than other service models.

21 List out the stages to develop applications in WS-BPEL

Denial - don't need it

Coercion - management says we have to use it C405.5 BTL1
Elation - realization that it will solve all our enterprise application
problems
Depression - realization that it will not solve all our enterprise
application problems yet
 Enlightenment - understanding how - and when - to leverage the
advantages of SOA, via BPEL (in this case, using your Java skills
as a guide)

22 Define WS-Policy APR/MAY2018

The Web Services Policy Framework (WS-Policy)
provides a general purpose model and corresponding syntax to
describe the policies of a Web Service. WS-Policy defines a base C405.5 BTL1
set of constructs that can be used and extended by other Web
services specifications to describe a broad range of service
requirements and capabilities.

23 Define Composable Architecture

The Web service specifications (WS*) are designed to be
composed with each other to provide a rich set of tools for secure,
reliable, and/or transacted Web services. WS-Policy by itself does
C405.5 BTL1
not provide a negotiation solution for Web services. WS-Policy is
a building block that is used in conjunction with other Web service
and application-specific protocols to accommodate a wide variety
of policy exchange models.

24 Define Compact Policy Expression

To express a policy in a more compact form while still using the XML
C405.5 BTL1
Infoset, this specification defines three constructs: an attribute to
decorate an assertion, semantics for recursively nested policy operators,
and a policy reference/inclusion mechanism
25 Define Policy Expression

To convey policy in an interoperable form, a policy expression is an C405.5 BTL1

XML Infoset representation of a policy. The normal form policy
expression is the most straightforward Infoset; equivalent, alternative
Infosets allow compactly expressing a policy through a number of
constructs
26 List the Security Threads APR/MAY 2018

• Confidentiality
• Man-in-the-middle C405.5 BTL1
• Spoofing
• Denial of Service
• Replay Attacks

27 List the Web Services Security Requirements APR/MAY 2018

C405.5 BTL1
• Authorization
• Data Integrity and Data Confidentiality
• Integrity of Transactions and Communications
 • Non-Repudiation
• End-to-End Integrity and Confidentiality of Messages
• Audit Trails
• Distributed Enforcement of Security Policies

28 Define Secure Messaging

Secure Messaging ensures privacy, confidentiality and
integrity of interactions. Digital signatures techniques can be used
to help ensure non-repudiation. Techniques that ensure channel
security can be used for securing messages. However, such
techniques are applicable in a few limited cases. Examples include C405.5 BTL1
a static direct connection between a requester agent and a provider
agent. For some applications, such mechanisms can be
appropriate. However, in the general case, message security
techniques such as encryption and signing of the message payload
can be used in routing and reliable messaging.

29 List the layers of the J2EE platform as they relate to SOA.

C405.5 BTL1

30 List the layers of the J2EE platform as they relate to SOA.

J2EE solutions inherently are distributed and therefore

componentized. The following types of components can be used to
build J2EE Web applications:
Java Server Pages (JSPs) Dynamically generated Web pages
hosted by the Web server. JSPs exist as text files comprised of C405.5 BTL1
code interspersed with HTML.
Struts An extension to J2EE that allows for the development of
Web applications with sophisticated user -interfaces and
navigation.
Java Servlets These components also reside on the Web server and
are used to process HTTP request and response exchanges. Unlike
JSPs, servlets are compiled programs.
 Enterprise JavaBeans (EJBs) The business components that
perform the bulk of the processing within enterprise solution
environments. They are deployed on dedicated application servers
and can therefore leverage middleware features, such as
transaction support.
While the first two components are of more relevance to establishing the
presentation layer of a service-oriented solution, the latter two
commonly are used to realize Web services
31 Give the step by step process in the service oriented analysis.
[NOV/DEC 2016]

– Define a preliminary set of service operation

candidates.
– Group service operation candidates into logical
contexts. These contexts represent service
candidates.
C405.5 BTL1
– Define preliminary service boundaries so that they
do not overlap with any existing or planned
services.
– Identify encapsulated logic with reuse potential.
– Ensure that the context of encapsulated logic is
appropriate for its intended use.
– Define any known preliminary composition models.

32 Write the syntax for getVariableData function in WS BPEL.

[NOV/DEC 2016]
C405.5 BTL1
getVariableData(variable name, part name, location
path)

33 What is service modeling process NOV/DEC 2017

SOMF is a service-oriented development life cycle methodology, a
discipline-specific modeling process. It offers a number C405.5 BTL1
of modeling practices and disciplines that contribute to a
successful service-oriented life cycle development
andmodeling during a project
34 Write any four attributes of invoke elements of BPEL
NOV/DEC 2017 C405.5 BTL1

1 Briefly explain about WSDL & SOAP basics in service oriented C405.5 BTL6
design.(16)
2 Describe in detail about entity-centric business service design in a C405.5 BTL5
step by step process.(16)
3 Explain the steps involved in service oriented design in detail .(16) C405.5 BTL6

4 Explain the basics of web services description language in C405.5 BTL6

detail.(16)
5 Explain briefly about business-centric SOA C405.5 BTL6

6 Explain in detail about service modeling guidelines.(16) C405.5 BTL6

7 Describe application service design in a step by step process.(16) C405.5 BTL1

8 .a.List out the objectives of service oriented design.(6)

BTL1
b.Explain about service oriented design process.(10) C405.5
BTL6

9 Explain entity-cenric and task-centric business

C405.5 BTL6
service design in detail.(16)
10 a.Discuss about entity-centric business service design .(8)
b.List out the steps for composing SOA.(8) C405.5 BTL5

11 Identify the various steps involved in service oriented modeling

elaborate them in detail. (16) [NOV/DEC 2016] C405.5 BTL5

12 Illustrate in detail about the WS-BPEL with code snippets (16)

[NOV/DEC 2016] C405.5 BTL5

13 Describe the Web Services Security Requirements in detail.

C405.5 BTL5
APR/MAY 2018
14 List out the security Threads in detail APR/MAY 2018 C405.5 BTL5

15
C405.5 BTL5
NOV/DEC 2017
16
C405.5 BTL5
NOV/DEC 2017
 Question Paper code 80602

B.E./B.Tech DEGREE EXAMINATIONS NOVEMBER /DECEMBER 2016

Seventh Semester

IT6801 service oriented architecture

(Regulation 2013)

Answer All Questions

PART A ---(10 *2 = 20 )

1. Give the rules for well formed documents in XML

2. What is a XML namespace?

3. Define XML parser.

4. Write a simple style sheet using XSL

5. List out some characteristics of contemporary SOA.

6. How loose coupling achieved in SOA?

7. Sketch the anatomy of a SOAP message.

8. List out some primitive MEPs.

9. Give the step by step process in the service oriented analysis.

10.Write the syntax for getVariableData function in WS BPEL.

Part B ---- (5 * 16 = 80)

11. (a) (i) Create a document type definition that defines the structure for email
message,further create a XML docum,ent that reference to the created document type
definitions. (8)
 (ii) With examples explain internal and external DTD. (8)

OR

(b) Explain in detail about XML schema and XML files. (16)

12. (a) (i) Differentiate DOM and SAX based XML parsing. (6)

(ii) Explain SAX based parsing with example. (10)

OR

(b) (i) Give a brief note on Modeling database in XML (8)

{ii) With example show how XSLT can transform an XML document into HTML.(8)

13. (a) Compare SOA with client server and distributed internet architectures. (16)

OR

(b) Summarize the various principles of service orientation in detail. (16)

14. (a) Discuss in detail about Orchestration and Choreography (16)

OR

(b) Explain in detail about Atomic Transaction Process with suitable diagrams. (16)

15.(a) Identify the various steps involved in service oriented modeling elaborate them in
detail. (16)

OR

(b) Illustrate in detail about the WS-BPEL with code snippets (16)
 Question Paper code 41302

B.E./B.Tech DEGREE EXAMINATIONS APRIL /MAY 2018

Seventh Semester

IT6801 service oriented architecture

(Regulation 2013)

Answer All Questions

PART A ---(10 *2 = 20 )

1. Define Service-oriented architecture

2. State service component

3. State the characteristics of Orchestration service layer?

4. Define Soap message

5. Write the IT centric entry points

6. What is the responsibility of the service?

7. List down the basic platform blocks.

8. Define ASP.NET Web Forms.

9. Mention the three types of choreography.

10.define WS-Policy..

Part B ---- (5 * 16 = 80)

11. (a)Explain the characteristics of SOA in detail.

OR

(b) Mention the principles of service orientation standardization in detail.

12. (a) Discuss on the protocols of Atomic Transaction in detail.

OR

(b) Describe the elements of Web services platform in detail.

13. (a) Explain about the operations in entity centric.

OR

(b) Compare SOA with distributed client-server architecture. Discuss the anatomy of
service oriental architecture.

14. (a) Discuss how SOA is related to the layers of the layers of the J2EE platform.

OR

(b) Mention the benefits of JAX_RPC in detail.

15.(a) Describe the web services Security Requirements in detail

OR

(b) List the Security threads in detail.