javapandit.net
  • Home
  • Quick Java
    • Exception Handling
    • Collections Framework
  • Java Best Practices
  • Web Services
    • Web Service Basics
    • Ten Basic webservice concepts
    • XML
    • Apache Axis
    • Restful Web Services
  • JMS Concepts
    • JMS- MySQL
  • Hadoop
    • NoSQL DATABASEs
    • Apache Sqoop
    • Hadoop Interview Questions
  • Java 5
  • Java 8
    • Java 8 : Lambda Expressions
  • JDBC
  • Java Architect
    • Enterprise application re-platforming strategies
    • Java Memory Management
  • Java Programs
  • Technical Tips
    • How to set JAVA_HOME environment variable
    • How to create an auto increment field in Oracle?
    • Linux Commands
  • Best Java Interview Questions
    • Java Interview Questions- YouTube
  • Interview Questions
    • Java Tech interview Questions
    • Core Java Interview Questions >
      • core tech questions1
      • Java Collection interview questions
      • Java Concurrency
    • Servlets Interview Questions
    • JSP Interview Questions
    • Java Web Services Interview Questions
    • EJB Interview Questions
    • XML Interview Questions
    • JMS Interview Questions
  • Struts Interview Questions
    • Struts 2 Interview Questions
  • Java EE Architects Interview Questions
    • Java Architect Interview Questions
    • Top 10 reasons for Java Enterprise Application Performance Problems
    • Web Application Scalability Questions for IT Architect
  • JavaPandit's Blog
  • Web Services Interview Questions
  • Servlets And JSP
  • Oracle SOA Interview Questions
    • Open ESB /JBI
    • BPEL Language
  • Log4J
  • Ant
  • Maven
  • JMeter
  • JUnit
  • Apache POI Framework
  • ORCALE SERVICE BUS (OSB) Interview Questions
  • J2EE Patterns
    • Model-View-Controller (MVC)
    • Front Controller
    • DAO
    • Business Delegate
    • Session Facade
    • Service Locator
    • Transfer Object
    • Design Patterns >
      • Creational Patterns >
        • Singleton
      • Behavioural Patterns
      • Structural Patterns
    • Intercepting Filter
  • SQL Interview Questions/Lab
  • Best Wall Papers
    • Devotional Songs
  • Java Community
  • HIBERNATE
  • ORACLE CC&B
    • Oracle CC&B Interview Questions
  • Docker
  • Little Princess
    • Sai Tanvi Naming Ceremony Celebrations
    • Rice Feeding Ceremony
    • Sai Tanvi Gallery
  • APPSC Career Guidance
    • AP History
    • Indian Polity
    • Indian Economy
    • Science & Technology
    • Mental Ability and Reasoning
    • Disaster Management
    • Current Affairs and Events
    • General Sciences >
      • Biology
      • Physics
      • Chemistry
    • Previous Question Papers
  • About Us
  • Contact US

WebServices

Picture
key functional components:

Service Implementation:
Build from scratch, provide a wrapper, or create a new service interface for an existing Web Service.

Publication:
Author the WSDL document, publish the WSDL on a Web Server, and publish the existence of your WSDL in a Web Services registry using a standard specification (UDDI).

Discovery:
Search the registry, get the URL, and download the WSDL file. –Invocation: •Author a client (SOAP) using the WSDL and make the request (SOAP message) and get the response (SOAP message).

Overview

Picture
1. Client queries registry to locate service.
2. Registry refers client to WSDL document.
3. Client accesses WSDL document.
4. WSDL provides data to interact with Web service.
5. Client sends SOAP-message request.
6. Web service returns SOAP-message response.

Stages of Web services Development and Deployment:


Creation – Design, development, documentation, testing, and distribution.

Publication – Web service hosting and maintenance.


Promotion – Directory services, value-added services and accreditation.

Structure:

Picture






A program sends a request  to a remote Web service containing an XML message and (optionally) receives a response.
  
A minimal web service has three components:

The Service: a software component which is capable of processing an XML document. –Transport, programming language etc is not important

The Document: the XML document that –contains all of the application-specific information.

The Address:  describes the protocol binding (e.g. TCP or HTTP) & network address that can be used to access the service. –also called a port-reference.

Features:

Support Document Exchange:
XML containing document-oriented or procedural-oriented information.

Standardization:
Based on standardized XML and supported globally by most major technology firms.

Interoperability:
XML is at the data transport level.

Loosely Coupled:
The abstraction web server interface (WSDL) from its implementation decouples the logic of the client and the server.   
   –makes it much easier to change back-end implementation without the client needing to update their code.

Course-grained:
Course-grained model e.g. fine grained = Java method but Web Service typically combine several fine-grained operation to expose collective.

Supports RPC:
Support remote procedure calls (built into SOAP) via and XML-based protocol.

Web Service Development:

Green field:
Developer starts from scratch, creating not only the Web service but also the application functionality being exposed as a Web service.

Bottom up:
Functionality being exposed as a Web service (i.e. the back-end application) already exists.

Top down: 
Start with an existing Web service interface and then create the application functionality capable of implementing that interface.

Meet in the middle:
Combination – the Web services interface (abstract WSDL) and existing application code exists already –need to integrate them by creating a bridge.


Powered by Create your own unique website with customizable templates.