C01

IBM’s Web 2.0 Strategy:Products And Themes

Raymond Josef Edward A. LaraRegional Technical Team, ASEAN SW Lab Services

© 2008 IBM CorporationPage 1

WebSphere Technical Conference 2008

Gain new insights, knowledge and skills | 19-22 August 2008 Suntec Singapore

What Is Web 2.0

� Term coined by Tim O’Reilly for the next generation of web applications and software in general

� Shows a paradigm shift where applications are not dependent on technology but by the socialfactor…the “American Idol” phenomenon

� Web applications, since their inception, has been one big proof-of-concept showing that the technology works, Web 2.0 is about what the technology is used for: to serve content and incite participation




Concepts Behind Web 2.0

� Embrace the “long tail”�Current web applications just expose the “head”

�Web 2.0 apps reaches back as far as needed to get content

� Content focus�Web 2.0 hinges on content, lots of it

�Critical mass needs to be achieved to bring out the worthy 20% but the other still 80% needs to be there

� Power to the users�Web 2.0 is what the Internet is all about: choice

�Users must be given freedom to determine what “clicks” and this will lead others to follow

�How many times have you heard: “Did you see that new video in YouTube?”

� Webmasters demoted to administrators�Webmasters are delegated to just managing the infrastructure and for technical support

�Content control and even presentation is entirely up to the users

� The inmates have taken over the asylum

�The more freedom users have the more they can enrich the application

�Some rights may have to be given up to the user

� Constant refinement�There is no such thing as a “final version” in Web 2.0 web apps

�As long as users keep coming back the web application is in “perpetual beta”

� Cooperate, don’t control�Work with the users, build a framework for them to operate with but don’t restrict

�See “On The Lot” and “Google Gadgets”

� Multi-channel�The browser is not the only platform to present Web 2.0

�Mobile Phones, PDAs, Web Kiosk Terminals, and even desktop applications




IBM’s Web 2.0 Strategy

� Technology�AJAX

�REST

�JSON

�RSS

�ATOM

� Techniques/Services�Mashups

�Composite Applications

�Tagging

�Folksonomy

�Blogging

�Wikis




AJAX

� Stands for Asynchronous JavaScript and XML� AJAX is not a new technology or programming language, but a new

way to use existing standards and mechanisms� With AJAX you can create better, more dynamic, and more user-

friendly web applications that incorporates features that were previously only seen in desktop applications (e.g. drag and drop)

� Dojo Toolkit – Widely supported AJAX framework




Traditional Web Applications

Client

Application Server

User interaction with pagetriggers HTTP request…

Request processed and HTML page generated

Time

Client refreshes whole pagebased on new HTML

HTTP request HTTP response

User interaction…




AJAX Web Applications

Client

Application Server

User interaction with pagetriggers AJAX action…

Request processed and XML data or HTML page fragment generated

Time

Client refreshes part of a pagebased on new XML data or HTML

JavaScript

JavaScript invoked tohandle request

HTTP request HTTP response

User interaction…




REST

� Stands for Representational State Transfer� Conceptualized by Roy Fielding in his doctoral dissertation which

became the architectural model for HTTP (and therefore the World-Wide Web)

� Characteristics:� Client-Server – Uses a request-response type of interaction

� Stateless – The request must hold all information necessary to accomplish the interaction and should not rely on any server context

� Uniform Interface – The request makes use of set methods to determine the type of access (GET, PUT, POST, DELETE)

� Named Resources – The request must name the resource to be accessed from the server

� Works well with AJAX




More On REST

� REST is not a standard� W3C will not put out a specification for REST

� Vendors will not sell a toolkit for REST

� REST is a design pattern� It is not packaged, it is implemented

� REST uses standards� HTTP

� URI/URL

� XML, HTML, GIF, JPEG (resource representations)

� text/xml, text/html, image/gif, image/jpeg (MIME types)




REST In Action

� This is an example of how REST can be used in an application such as a customer relationship management system

AtomGET../crm/customer/cust1225/itemRetrieve a customer’s purchases

PUT

GET

POST

GET

GET

Method

../crm/customer/cust1225/item

../crm/customer/cust1225/item/it301

../crm/customer/cust1225

../crm/customer/cust1225

../crm/customer

URI

Enter a customer’s new purchase

Retrieve a customer’s purchase

Update a customer’s information

Retrieve a customer

Retrieve all customers

Action

JSON

XML

JSON

XML

Atom

Representation




REST vs. RPC

The URI is the methodThe URI calls the method

Designed for HTTPProtocol neutral

Unique URI per resourceAll resources use the same URI

Document orientedData oriented

RESTRPC




What About Web Services?

� Web services is an excellent technology� For systems integration and business processes

� Generally, for computer-to-computer solutions

� Web services is not appropriate for all situations� Not easily consumable (can’t code “by hand”)

� Generally, it is not good for user-to-computer solutions

We only need this…

…so what’s all this!!!




JSON

� Stands for JavaScript Object Notation� A specification for the simple and lightweight representation of data� JSON is text-based and easy to parse (compared to XML)� JSON is not tied to a particular programming language� Works well with REST services

{"accountNo": "12250301","name": "Jack B. Nimble","acctType": "CA","balance": 1000

}




RSS

� Stands for Rich Site Summary (or Really Simple Syndication)� A protocol used for subscription and delivery of content, called

syndication� Returns an XML document summarizing the updated content




Atom

� A syndication protocol similar to RSS but with a richer and morestrictly defined message format (works well with REST)

RequestGET /reilly/ HTTP/1.1Host: example.orgContent-Type: application/atom+xml

ResponseHTTP/1.1 200 OkContent-Type: application/atom+xmlContent-Length: nnnn

<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom ">

<title>My Submitted Expenses</title><link href="http://example.org/reilly/"/><entry>

<title>Lotusphere 2006</title><link rel=“alternate” href="http://example.org/reilly/3.html"/><link rel=“edit” href=“http://example.org/reilly/3.html”/><updated>2006-12-05T12:29:29</updated> <content type="XHTML" xml:lang="en-us">

<p xmlns="...">I am a speaker and am staffing a stand in the innovation lab</p> </content>

</entry></feed>




Mashups And Composite Applications

� A mashup is…� A collection of two or more components bound

together through content

� An application derived by seamlessly combining content from more than one data source

� A composite application is…� A rapidly created application to address an

immediate need

� A typically (but not necessarily) short-lived solution

� Informal, “good enough” (lacks product quality)




Tagging

� Tagging is the collaborative effort to organize information in which users are encouraged to assign freely chosen keywords to identify web sites (i.e. bookmarks) in ways that are meaningful to themselves

� Tagging results in a new way of classifying data known as a folksonomy

� Gives rise to tag clouds

It’s not what you know…it’s not who you know…it’s who knows what you need to know!




Blogs And Wikis




What Does Web 2.0 Mean For My Company?

� Syndication can be used to disseminate information quickly both internally (e.g. meeting recordings/podcast) and externally (e.g. product updates)

� Companies can allow mashups and composite applications for specialized functions (e.g. CRM, proposal generation) to increase user productivity

� Search engines can offer searching based on folksonomies as an alternative to standard taxonomy-based searches

� Companies can derive ideas for new products by deploying a blog for it’s customer community

� Product documentation can be refined and made more complete through wikis, errors in documentation can be corrected quickly




What Happened To SOA?

WEB 2.0Componentized Interoperable

Modular Scaleable




Where Is The Web 2.0 In WebSphere?

� WebSphere sMash� Based on the Project Zero public incubator

� REST services platform

� Supports JSON and ATOM

� Supports PHP and Groovy scripting

� WAS 6.1 Feature Pack for Web 2.0� AJAX proxy with support for REST connection

� JSON messaging capability (JSON-RPC)

� ATOM support

� Dojo toolkit + IBM extensions

Thank you…

[email protected]

Date post:	19-Oct-2014
Category:	Documents
View:	359 times
Download:	5 times

C01

Documents