The document discusses key concepts related to web services including SOAP, WSDL, and UDDI. It defines web services as software that makes itself available over the internet using XML messaging. It describes SOAP as the messaging protocol that uses XML and HTTP for communication. WSDL provides an XML format to describe web services, including what functions they provide and how to access them. UDDI is a platform-independent registry where businesses can publish their web services to allow for discovery.
Introduction to SOAP/WSDL Web Services and RESTful Web Servicesecosio GmbH
In this talk, held as part of the Web Engineering lecture series 2015 at Vienna University of Technology, we give an overview of the current state of the art in the domain of Web Services.
In the first part we dwell on the main principles of Service Oriented Architectures (SOA), followed by an introduction of the three core standards SOAP, WSDL, as well as UDDI. Furthermore, we briefly cover the Java API for XML Web Services (JAX-WS).
In the second part we focus on principles of RESTful Web Services and the Java API for RESTful Web Services. The lecture is accompanied by practical examples, which are also available on GitHub.
Introduction to Service Oriented Architectures, SOAP/WSDL Web Services and RE...ecosio GmbH
In this guest talk, held as part of the Web Engineering lecture series at Vienna University of Technology, we give an overview of the current state of the art in the domain of Web Services.
In the first part we dwell on the main principles of Service Oriented Architectures (SOA), followed by an introduction of the three core standards SOAP, WSDL, as well as UDDI. Furthermore, we briefly cover the Java API for XML Web Services (JAX-WS).
In the second part we focus on principles of RESTful Web Services and the Java API for RESTful Web Services. The lecture is accompanied by practical examples, which are also available on GitHub.
JAX-WS is the replacement and next generation to JAX-RPC and makes web services development much easier using annotations and much less configuration. JAX-WS is useful for people building webservices/SOA based infrastructure as JAX-WS makes the web service development much easier and is a big gain for developer productivity.
The session uses a web service for temperature conversion example to build both the client side and Server side artifacts. Also on the server side both Servlet based and EJB3.0 based web service development will be demonstrated. JAXB concepts will be used to demonstrate the examples.
The session uses Eclipse Ganymede and Jboss 5.0. However JAX-WS being the standard, the code will smoothly work on any JavaEE based compliant servers.
Here i am attaching the document for creating the web services
i hope this can be helpful for Freshers.
http://skillgun.com/csharp/interview-questions-and-answers
Introduction to SOAP/WSDL Web Services and RESTful Web Servicesecosio GmbH
In this talk, held as part of the Web Engineering lecture series 2015 at Vienna University of Technology, we give an overview of the current state of the art in the domain of Web Services.
In the first part we dwell on the main principles of Service Oriented Architectures (SOA), followed by an introduction of the three core standards SOAP, WSDL, as well as UDDI. Furthermore, we briefly cover the Java API for XML Web Services (JAX-WS).
In the second part we focus on principles of RESTful Web Services and the Java API for RESTful Web Services. The lecture is accompanied by practical examples, which are also available on GitHub.
Introduction to Service Oriented Architectures, SOAP/WSDL Web Services and RE...ecosio GmbH
In this guest talk, held as part of the Web Engineering lecture series at Vienna University of Technology, we give an overview of the current state of the art in the domain of Web Services.
In the first part we dwell on the main principles of Service Oriented Architectures (SOA), followed by an introduction of the three core standards SOAP, WSDL, as well as UDDI. Furthermore, we briefly cover the Java API for XML Web Services (JAX-WS).
In the second part we focus on principles of RESTful Web Services and the Java API for RESTful Web Services. The lecture is accompanied by practical examples, which are also available on GitHub.
JAX-WS is the replacement and next generation to JAX-RPC and makes web services development much easier using annotations and much less configuration. JAX-WS is useful for people building webservices/SOA based infrastructure as JAX-WS makes the web service development much easier and is a big gain for developer productivity.
The session uses a web service for temperature conversion example to build both the client side and Server side artifacts. Also on the server side both Servlet based and EJB3.0 based web service development will be demonstrated. JAXB concepts will be used to demonstrate the examples.
The session uses Eclipse Ganymede and Jboss 5.0. However JAX-WS being the standard, the code will smoothly work on any JavaEE based compliant servers.
Here i am attaching the document for creating the web services
i hope this can be helpful for Freshers.
http://skillgun.com/csharp/interview-questions-and-answers
Overview of web services, SOAP, WSDL and UDDI.
A web service provides a defined set of functionality on a machine-processable interface.
The web service interface is described in a formal language like WSDL that allows creating code to access the service thus simplifying web service consumer (client) and provider (server) development.
In big web services, the interface is typically described in WSDL while the access to the service makes use of the SOAP message protocol.
SOAP has its roots in remote object access but is now a general message based and asynchronous transport mechanism.
SOAP is typically carried in HTTP (HyperText Transmission Protocol), but other message based protocols like SMTP (Email) or plain TCP could be used as well.
WSDL provides a formalized description of an interface that is coarsely separated in an abstract service interface definition containing operations and data types, a transport binding that describes how the web service is accessed and finally a description of the location (address) under which a web service is accessible.
UDDI (Universal Description and Discovery Protocol) was meant to become the standard protocol for some kind of a public yellow pages where publicly accessible web services would be listed. Lack of industry interest, however, prevented UDDI to gain widespread use.
2024.06.01 Introducing a competency framework for languag learning materials ...Sandy Millin
http://sandymillin.wordpress.com/iateflwebinar2024
Published classroom materials form the basis of syllabuses, drive teacher professional development, and have a potentially huge influence on learners, teachers and education systems. All teachers also create their own materials, whether a few sentences on a blackboard, a highly-structured fully-realised online course, or anything in between. Despite this, the knowledge and skills needed to create effective language learning materials are rarely part of teacher training, and are mostly learnt by trial and error.
Knowledge and skills frameworks, generally called competency frameworks, for ELT teachers, trainers and managers have existed for a few years now. However, until I created one for my MA dissertation, there wasn’t one drawing together what we need to know and do to be able to effectively produce language learning materials.
This webinar will introduce you to my framework, highlighting the key competencies I identified from my research. It will also show how anybody involved in language teaching (any language, not just English!), teacher training, managing schools or developing language learning materials can benefit from using the framework.
Read| The latest issue of The Challenger is here! We are thrilled to announce that our school paper has qualified for the NATIONAL SCHOOLS PRESS CONFERENCE (NSPC) 2024. Thank you for your unwavering support and trust. Dive into the stories that made us stand out!
Model Attribute Check Company Auto PropertyCeline George
In Odoo, the multi-company feature allows you to manage multiple companies within a single Odoo database instance. Each company can have its own configurations while still sharing common resources such as products, customers, and suppliers.
Welcome to TechSoup New Member Orientation and Q&A (May 2024).pdfTechSoup
In this webinar you will learn how your organization can access TechSoup's wide variety of product discount and donation programs. From hardware to software, we'll give you a tour of the tools available to help your nonprofit with productivity, collaboration, financial management, donor tracking, security, and more.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
Acetabularia Information For Class 9 .docxvaibhavrinwa19
Acetabularia acetabulum is a single-celled green alga that in its vegetative state is morphologically differentiated into a basal rhizoid and an axially elongated stalk, which bears whorls of branching hairs. The single diploid nucleus resides in the rhizoid.
3. Web Services?
Any piece of s/w that makes itself
available over the internet and uses
XML messaging system.
Due to XML communication, WS is
OS or pgming language independent.
Eg:- Java can talk with Perl; Windows
app can talk with Unix app.
4. Web Services
Services available on web
Examples:
1. Social media web service:
communicate with your friends
2. E-commerce webservice :
online purchasing
5. Web Site vs Web Services
Web site human consumption
WS application consumption
6. Why Web Services?
App Server1 App Server2
m/c1 m/c2
X
(jar)
getProducts()
MVC
Client calls getProducts()
getProducts()
7. Why Web Services?
getProducts() in Appserver2 can’t
call getProducts() in AppServer1.
Solution:
Make the getProducts() as jar file
& put it in AppServer2.
8. Why Web Services?
Problems:
Db difference in AppServer2
Modifications in getProducts()
in AppServer1 can’t reflect in
AppServer2. (so repack another
jar for modified getProductsI())
9. Why Web Services?
App Server1 App Server2
m/c1 m/c2
direct call using
WS
getProducts()
MVC
Client calls getProducts()
getProducts()
10. Why Web Services?
+ve: interoperable
Language independent
java ws can invoke .Net WS
H/W independent
Ws running in Windows can call
Unix WS
11. Why Web Services?
+ve: interoperable
Eg:-
Google Maps In Chrome under
windows
Google Maps in IE under
Redhat Linux
13. Web services Building Blocks
SOAP (Simple Object Access Protocol)
XML based transport protocol
WSDL (Web Services Description Language)
XML based
To describe WS
UDDI(Universal Description, Discovery,
and Integration)
.NET based
To discover WS
14. SOAP (Simple Object Access Protocol)
SOAP = XML + HTTP
XML to encode & decode data
HTTP to transport data
Def:-
XML based communication protocol which is
language & platform independent.
15. Why SOAP?
DCOM & CORBA objects communicate
using RPC.
-ve of RPC:
Blocked by firewalls & proxy servers.
+ve of SOAP:-
No such blocking, moreover by using SOAP,
applications running on different OS, different
technologies, different PL can communicate
with each other.
16. SOAP Elements
1. Envelope Element (required)
2. Header Element (opt)
3.Body Element (required)
4.Fault Element (opt)
17. SOAP Elements
1. Envelope element identities the XML
as a SOAP message.
2. Header element contains WS std
info like authentication, pay load.
3. Body element contains the actual
information, call & response
information.
4. Fault element provides error
information occurred while
processing the msg.
20. SOAP HTTP Binding
After establishing a connection, the client
can send an HTTP request message to
the server:
POST /item HTTP/1.1
Host: 189.123.255.239
Content-Type: text/plain
Content-Length: 200
21. SOAP HTTP Binding
The server then processes the request
and sends an HTTP response back to the
client.
The response contains a status code that
indicates the status of the request:
200 OK status code
Content-Type: text/plain
Content-Length: 200
22. Why HTTP for SOAP?
HTTP is already a widely implemented, and well
understood, protocol.
SOAP messages are one-way, instead of two-way.
one from the "client" to the "server“ and one from the
"server" back to the "client”. But SOAP specification
also says that when a request/response protocol, such
as HTTP, is used, these two messages can be
combined in the request/response of the protocol.
Most firewalls are already configured to work with
HTTP.
HTTP makes it easy to build in security, with Secure
Sockets Layer (SSL)
24. WSDL (Web Services Description Language)
• WSDL is an XML document to describe
web services and how to access web
services
A client program connecting to a web
service can read the WSDL to determine
what functions are available on the
server.
The client can then use SOAP to actually
call one of the functions listed in the
WSDL.
27. Definition Element
root element of all WSDL documents
Associates WS with its namespaces.
Defines one or more WS.
contains all the service elements described
here.
• Types to define datatypes used by
WS using XSD.
• Message piece of information
exchanged between C/S.
28. WSDL (Web Services Description Language)
• Operation actions which are
supported by WS.
• PortType collection of operations
• Binding links abstract section with
actual section or concrete section.
• Port endpoint defined in terms of URL
• Service how to consume WS?
Collection of related end pts.
30. Definition Element
targetNamespace unique logical namespace
for WS.
xmlns default WSDL namespace which
contains <definition>, <message> …
xmlns:tns optional attribute contains same
value as targetNamespace.
Xmlns:soap & xmlns:xsd std namespace for
SOAP information and data types.
31. Types Element
To define datatypes used by WS using XSD.
<types>
<schema targetNamespace
="http://www.mysite.com/myservice.wsdl"
xmlns="http://www.w3.org/2000/10/XMLSchema">
<element name=“MyRequest">
</element>
</schema>
</types>
User defined schema
Std schema
32. Message Element
Definition element contains one or more message
elements.
<message name="getMyInput">
<part name="term" type="xs:string"/>
</message>
<message name="getMyOutput">
<part name="value" type="xs:string"/>
</message>
Each msg element can contain any no of part
child elements.
2 message elements (1- request, 2-
response)
33. PortType Element
PortType element contains one or more operation
elements.
portType class or I/f
Operation method
<portType name=“MyServicePortType">
<operation name=“MyMethod">
<input message=“tns:getMyInput"/>
<output message=" tns:getMyOutput"/>
</operation>
</portType>
35. Service Element
• Web service clients can learn the following from
the service element:
– where to access the service,
– through which port to access the web service, and
– how the communication messages are defined.
• documentation element to provide human-
readable documentation.
36. Service Element
<service name=“MyService">
<documentation>WSDL File for MyService</documentation>
<port name=“MyServicePort” binding="tns:MyServiceBinding“>
<soap:address
location="http://www.mysite.com/MyService/">
</port>
</service>
Example pgm: combine all elements code
38. UDDI (Universal Description, Discovery, and Integration)
• UDDI is platform independent registry in
which business can publish their services &
also it provides mechanism to locate web
services
By OASIS (Advancing Open Standard for
Information Society)
UDDI provides publication & discovery of WS
which are key components of SOA.
39. UDDI Basics
Public UDDI registries are hosted by
companies such as IBM, Microsoft.
DNS Vs UDDI
DNS (nameIP address) is a static DB.
Where as UDDI provides information on how
to find & invoke WS.
GUID (Globally Unique Identifiers)
to uniquely identify the resources in each
registry.
40. 3 Levels of Information in UDDI
White Pages Companies general information
such as Name, Address, Contact Number.
Yellow Pages Looking up companies by their
kind of services.
Green Pages Provides information about how
to interact with companies web services.
41. UDDI Structure
UDDI provides 4 types of information.
1. Business Information
2. Service Information
3. Binding Information
4. Service Specification
42. UDDI Structure
Business Entity
Business Service
Business Service
Binding Template
Binding Template
Binding Template
Binding Template
tModel
tModel
tModel
tModel
43. UDDI Structure
1.Business Information (abt org,
Group of ppl who register their
services in registry)
Provided by BusinessEntity
Element.
Supports white pages & yellow
pages.
This element is top level
information manager.
44. UDDI Structure
2. Service Information (Resources
provided by business)
Provided by BusinessService
Element.
Supports green pages.
This element is top level
information manager.
45. UDDI Structure
3. Binding Information (info abt how to
bind & invoke WS)
Provided by BindingTemplate
Element.
BindingTemplate element is within
BindingService element.
46. UDDI Structure
4. Service Specification
Enclosed within each
BIndingTemplate Element.
tModel elements (Technical
Models)
tModel pointer to WDSL file.