Web Services

1
(No Transcript)
2
McKean
Kevin

• CEO Editorial Director
• InfoWorld Media Group

3

• Platinum Sponsors

Gold Sponsors
4
(No Transcript)
5
Bosworth
Adam

• Chief Architect and Senior VP of Advanced
  Development
• BEA Systems, Inc.

6
A Framework for the Future
7
Agenda

• Integration and TCO
• Learn from History Waves of Change
• This Wave, SOA and Why
• Challenges and Solutions
• Solutions Today
• Solutions Tomorrow
• The Day After

8
Integration and TCO

• Integrate your user interface
• Portals, Customization, Personalization
• Understand your site flows
• Access to information and process, not just
  content
• Integrate your information
• Integrating information across applications
• Integrate your business processes
• Treat every application as a service
• TCO
• Make it more and more cost-effective to design,
  develop, deploy and manage applications and
  easier to monitor their efficiency

9
History Waves
Cycle of Innovation Disruptive Technology lt 5
of developers Standard Platform/APIs lt 20 of
developers Framework / Tools Rest of developers
S O A
Web Platform

• Technology
• Integration
• Web Services
• XML
• BPM, IM

Client/Server

• Technology
• Access
• Web Browser - HTTP/HTML, Java,,Servlets
• Ecmascript
• J2EE/.Net AppServers, Text indexing, images,..
• Ease of Use
• FrontPage, WebLogic Workshop

PC, GUI

• Technology
• Data
• RDBMS, SQL PCs, LANs, TCP/IP, Relational
  Database
• Ease of Use
• PowerBuilder, Visual Basic,

Mainframe

• Technology
• Productivity
• Bios, Windows, Mac
• Ease of Use
• dBASE, Turbo Pascal, VB 1.0,,

• Technology
• Transactions
• Batch, OLTP, DBMS, Messaging, CICS
• Ease of Use
• COBOL

10
The Wave SOA and Why

• The economics are huge Integrate across the
  enterprise
• Your information (Data models across
  Applications)
• Your user interface (Portals)
• Integrate your business processes (EAI)
• Who remembers Cullinet?
• What changes the economics is the Web
• Any application anywhere
• This drives standards It always has
• How does one accomplish Integration
• Recognize the realities and design for them
• Sufficient tools and technologies to make this
  productive
• Sufficient information to make this manageable

11
The Realities of Integration

• Apps are built by different groups of people in
  different places and at different times
• They are deployed and altered on different
  schedules
• Often they are legacy apps that either have
  scheduled downtime or constraints on throughput
• Applications frequently require people and
  process to execute requests and cannot respond
  quickly to a request
• Applications run on many disparate platforms

12
What are Web Services?
User Interface
Logic
Apps Talking to Apps
Data
13
Why Web Services?

• Web Services is the Architecture required for
  Application to Application Integration in the
  real world
• Coarse Grained Communication
• Loose Coupling
• Asynchrony

14
Cross Platform

• Cant mandate the operating system
• Cant ignore mainframes
• Cant ignore Unix
• Cant ignore Linux
• In short, .NET does not equal all applications
• Solution Formal model for sharing documents
  whose format is agreed upon by all platforms,
  e.g. XML

15
Coarse Grained Communications

• Cant overload the network
• Cant overall the applications and servers
• Cant mandate the object model
• Cant expect to hang onto references
• Cant expect to mandate a platform
• In short, apps are not objects
• Solution A formal model for requesting and
  delivering coarse grained sets of data using XML

16
Loose Coupling

• Cant understand the other applications
  implementation
• Cant break if it changes
• Cant know its underlying data model
  implementation
• Cant assume its platform or language
• Cant know how to query it
• In short, apps are not databases or interfaces
• Solution A formal model describing the XML
  messages being sent/requested and, if stateful,
  the legal sequences in which this may occur

17
Asynchrony

• Cant assume that the other application is
  running
• Cant assume that it can execute the service or
  deliver the information instantly
• Load constraints
• People and process constraints
• Cant assume that connections are reliable
• In short, apps are not functions or methods
• Solution Enable asynchronous communication and
  coordinated conversations

18
The Solution
19
The Technologies
20
Apps Talking to Apps
Integration
BPM
Data Integration
XML Queues/Stores
Command Control
Message Broker
XML Query
WEB SERVICES
21
Apps Talking to Apps
Web Services
Adapters
Enterprise-server Application Server
Message/Integration Workflow
DB
Queue
ERP
J2EE
Legacy
W/S enabled app
22
Programming Model for SOA Apps

• Integration Broker Message Driven
• Choreographed with Business Process Model
  (BPEL4WS), but extended with Java (JPD)
• Specific Order Processing
• Message oriented Error handling and recovery
• Long-Running Transactions and Undo logic
• Maintains State/Context across messages
• RAS Volumes 1000s / second

23
Loose Coupling in the Large, CMR

• Message Broker
• Massively scalable and potentially very fast
• In Order Delivery within a conversation
• Filters all loosely coupled requests in and out
• Decides and controls who needs to know
• Fully XML and Web Service aware
• Supports Reliable Message Service Store/Forward
• Extensible pipeline that integrates logging,
  monitoring, authentication, authorization,
  subscription, and custom transformations
• Unifies all destination and all topics as URLs

24
Where Are We Today

• Enabled for EAI
• Standards are almost sufficient
• Envelope (SOAP), Package (XML), Contract (WSDL)
• Asynch - WS_ADDRESSING
• Reliable WS_RELIABLEMESSAGING
• Secure WS_SECURITY
• BEPL4WS (Almost OK, Visual Basic w/out the Basic)
• Technology
• XMLBeans, EcmaScript 4X, XML Query, JWS, JPD,
  Controls
• Frameworks and Tools have shipped
• Hide plumbing! Focus on app/business logic

25
The Realities of Development

• Making Applications Services means much more
  uptime and volume
• Service Integration and competition means more
  rapid need to alter the application
• The tough financial realities mean fewer and
  farther developers (even when they are still
  employed, they are now often 5,000 miles away)

26
The Solution
27
Users
Magic Triangle
End Users
Corporate Developers
System Programmers
Power Users
?
?
?
?
Abstraction
?
?
?
?
Code
?
?
?
?
Complexity
28
Framework for Application Developers
29
Ideal Architecture Develop
WLW Code Metadata Controls Bus Components
Logging and Monitoring
Message Brokering Control, Monitoring, Routing
Meta-Data Policy Repository
BPM, User Interface Data Integration Layers
EJB Components (Code Dist) Transactions, Metadata
Caching
30
Ideal Architecture Deploy
Admin Console Script, Log, Map Resources
Logging and Monitoring
Message Brokering Control, Monitoring, Routing
Meta-Data Policy Repository
BPM, User Interface Data Integration Layers
EJB Components (Code Dist) Transactions, Metadata
Caching
31
Ideal Architecture Manage
Management Console Monitor, Alter, Control
Logging and Monitoring
Message Brokering Control, Monitoring, Routing
Meta-Data Policy Repository
BPM, User Interface Data Integration Layers
EJB Components (Code Dist) Transactions, Metadata
Caching
32
Ideal Architecture Run
Users, Applications, Partners
Logging and Monitoring
Message Brokering Control, Monitoring, Routing
Meta-Data Policy Repository
BPM, User Interface Data Integration Layers
EJB Components (Code Dist) Transactions, Metadata
Caching
33
Hot off the PressXML Query, Ecma 4X

• XML Query
• 1ms times per XML message / processor
• XML-gtXML, XML-gtJava, XMLSQL-gtXML
• Can teach 5MM people this, not 50,000
• Can build great Visual tools to author
• EcmaScript 4X
• XML is a native type
• Seamless integration with predicates and queries
• Procedurally extensible
• Dynamically redeployable
• Easy to learn/teach

34
Looking Out a Little Bit Further

• Compiled Languages extend to comprehend XML as a
  type and messaging as a metaphor
• Storages that are optimized for massively
  scalable fast routing of XML messages emerge
• Surprise. Basic standards (SOAP) freeze! Turn
  into the TCP/IP of this era
• Next Generation User Interface optimized for
  wireless, mobile, and Instant Messaging

35
XML Distributed Store

• Extremely fast
• Must save and retrieve up entire messages, pieces
  of messages, and persisted state at a rate of
  1000s/second
• Intelligent XPATH and pattern recognition
• A great deal of single-user transient data
• Should have optimized retrieval for known filters
• This isnt the Relational DB as XML solution
• This is true storage/retrieval of XML messages

36
Mobile, OCC and IM

• Will drive huge rise in asynchronous Web services
• Poor and unreliable bandwidth mandate background
  push
• Requires a standard model on back-end that is
  front-end neutral
• Information must come to you because too
  expensive to go to it
• IM makes it easy to push information to clients
  and to know who has what status
• User Interface is going to learn to listen

37
BEA WebLogic Platform

• BEA Web Logic Platform 8.1 Productivity,
  Integration
• Single unified model for business process (JWS,
  JPD)
• Single unified view of your information (Liquid
  Data)
• Single unified view of your information (Portal)
• Single unified place to develop (WLW)
• Single unified view of your pages and page flow
  (JPF)
• Extensible (.jcx) - Controls
• Message Driven Model (JWS, JWF, XML Beans)
• One architecture (Controls, Meta-data,
  Components)
• Fast transform (XML Query, Transform Controls)

38
BEA WebLogic Workshop 8.1IDE For the Rest of Us

• Built by a crack totally experienced team
• Business Views and Source Views, all updatable
• Integrated 1-stop debugging and deployment
• Fully extensible, but with SWING
• Integrated Test Harness is part of it
• Visual editing of everything
• Standard use of property sheet for methods, not
  just controls

39
Benefits

• Dramatic improvements in productivity
• 2002/2003 Within the Enterprise, EAI becomes
  standards based just as Client Server changed
  databases. Information will truly be integrated
  within organizations.
• 2003/2004 Between Enterprises, integration of
  information and processes becomes routine using
  secure reliable web services and intelligent
  extensible Web service brokers
• 2003 2005 The need for disconnected
  information, online/offline, and push drives the
  next-generation browser, an asynchronous browser,
  and leads to much more timely information
  flowing to your customers, partners and employees

40
Final Thoughts

• The Web Wave has really only just begun
• Like all waves, it takes 10 years to come to
  fruition and will increase usage by an order of
  magnitude
• Web Services will standardize both how
  applications and businesses talk to each other
  and the very concept of messaging and information
  delivery
• We will look back in wonder and ask how we ever
  survived in the current anarchy where information
  didnt flow as seamlessly and in as metered and
  managed a manner between programs as electricity
  flows between devices today
• BEAs current products are designed for this
  world and we continue to innovate toward it

41
Thank you
42
(No Transcript)
43
Mark JonesExecutive News Editor, InfoWorld

• Next Generation Web Services

Moderator
Adam CohenChief Developer, JetBlue Airways Ameet
PatelCTO, LabMorgan Kevin PollariPartner
Global Lead for Architecture Strategy Assets,
Accenture Gene RogersChief Technologist, Boeing
Advanced Space Launch Systems
44
(No Transcript)
45

• Sponsored Case Studies

46
(No Transcript)
47
(No Transcript)
48
(No Transcript)