TechnoBuzz

A Techno Blog, mainly about Java

web 2.0 conference

In Raleigh, I got a chance to attend IBM’s technical briefing on web 2.0 .

For now, will just list various bits of info that I will organize later.

QEDWiki (Quick and easy design) . Assembly : “QEDWiki is a unique Wiki framework in that it provides both Web users and developers with a single Web application framework for hosting and developing a broad range of Web 2.0 applications.”

Damia . Feeds: “provides easy-to-use tools that developers and IT users alike can use to quickly assemble data feeds from the Internet and a variety of enterprise data sources. The benefits of this service include the ability to aggregate and transform a wide variety of data or content feeds, which can be used in enterprise mashups.”

Mashup Hub. Tag : “Mashup Hub provides two broad areas of support: feed generation for enterprise data sources and a catalog of feeds and user interface (UI) widgets.”

Info 2.0

Many eyes

Baby name wizard

gather.com

second life

strike iron

gold corp

zoho

zoot

Advertisements

September 14, 2007 Posted by | AJAX, Blogging, J2EE, NC, Open Source, SOA, Web/Tech | Leave a comment

AXIS

Web Services with AXIS

June 29, 2005 Posted by | SOA | Leave a comment

SOA Talk

Service Oriented Architecture and Enterprise Service Bus

April 27, 2005 Posted by | SOA | Leave a comment

grid services

ogsa

December 9, 2004 Posted by | SOA | Leave a comment

Web Services learning

tutorial on web services

ws by apache

prez by ibm

September 22, 2004 Posted by | SOA | Leave a comment

On Demand

New Page 1

Service Oriented Enterprise
Patterns for SOA

Sam says

SOA Services Oriented Architectures – encapsulates software into service interfaces
which
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
services.



  • 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
    service.
  • Publish: Providers publish their services to the registry so requestors can find
    them.


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
systems.



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
protocols.





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]




<soapenv:Envelope>

<soapenv:Header>

</soapenv:Header>

<soapenv:Body>



</soapenv:Body>



</soapenv:Envelope>







WSDL (Web Services Descripton
Language
): 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
Integration
): 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
XML.



WEB SERVICES INTEROPERABILITY (ws-i.org)



Web
Services Primer



Web
Services Guide



SearchWebServices



GotDotNet


WebServices Zone



News on Web Services

August 9, 2004 Posted by | SOA | Leave a comment

Enterprise Sevice Bus in news

ESB – one messaging fabric choice for underlying an SOA.

August 3, 2004 Posted by | SOA | Leave a comment

Enterprise service bus

An article about ESB in regards to IBM (the code name of the product is Jetstream) : “ESB is built around industry standards and tools, including Java and Web services protocols”.

July 12, 2004 Posted by | SOA | Leave a comment