A Techno Blog, mainly about Java

On Demand

New Page 1

Service Oriented Enterprise
Patterns for SOA

Sam says

SOA Services Oriented Architectures – encapsulates software into service interfaces
are invoked by message passing. The preferred method of building
SOA is web services.

  • Architecture that leverages standards to represent software assets as services

  • Provides a standard way of representing and intercating with software assets
  • Used externally to integrate with apps outside of the enterprise
  • Service exposes only its interfaces to the rest of the system

Component Based Development (CBDI)

Main components in a SOA world are service providers and service requestors.

  • provider has some piece of code that performs a function that can be invoked
    across a network
  • requestor needs a piece of code that performs that function and has access
    to the provider’s network

Some implementations use a registry of services to help requestors find

  • Find: The requestor searches the known/trusted providers, or a registry, for a service description.
  • Bind: The requestor uses the service description to acess the provider and its
  • Publish: Providers publish their services to the registry so requestors can find

e-biz on demand operating environment

  • business processes: enable for web services
  • integrated end-to-end: use web services to integrate your data with your partnets, suppliers,
    customers, and so forth
  • respond with speed: use high level tools and languages to model and change your business processes quickly

Web services are functional elements deployed on a node on a network and
accessed over the Internet. A  Web service could be a piece of data
(such as the weather), a document (such as a credit report), or a file
of transactions (such as orders placed via an online marketplace), among
other things. 

Web services let companies bridge communications
gaps?between software written in different programming languages,
developed by different vendors or running on different operating

What make some functionality a web service is the "how" not the "what". 

IBM’s definition of web services: anything described by WSDL, services
are discoverable, and communicate using XML messages across industry standard

Web services are based on a set of standards:

SOAP (Simple Object
Access Protocol
): is an XML document format used to send information between endpoints.
A SOAP envelope can include a header (which contains metadata), and must
include a body (which contains the data). [1] [2] [3]







WSDL (Web Services Descripton
): A WSDL document describes the interface to a web service – the "how"

and "where" of a web service. It makes it possible for a requestor
to invoke a service after it has been discovered. The requestor uses WSDL
to learn what arguments are required for invoking the Web service. The
developers of the functional component use WSDL to define the metadata
describing the web service.   

UDDI  (Universal Description, Discovery and
): Used for service discovery and service publication. Clients of Web services
used UDDI to discover where the web services reside. Web services providers
use UDDI to publish their Web services.  

SOAP, WSDL, and UDDI are all based on


Services Primer

Services Guide



WebServices Zone

News on Web Services


August 9, 2004 - Posted by | SOA

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: