Websphere Overview

1
Websphere Overview
dan wolfson senior technical staff member IBM
Data Management
2
Outline

• WebSphere Overview
• Industry Trends Implications
• Standards
• Changing Value Chain
• Access from everywhere
• Access to everywhere
• Service Oriented Architectures
• Flow-oriented architectures
• Discussion Areas

3

• Web and Business Component Serving

4
WebSphere Application Server Editions

• EJB Container

5

• J2EE 1.2 Required APIs/Function
• Delivered in WebSphere R4.0

• EJB 1.1
• Servlet 2.2
• JSP 1.1
• JDBC Core (J2SE 1.2)
• JDBC 2.0 Extensions
• JMS 1.0 (just the framework APIs)
• JNDI 1.2
• JTA 1.0
• JavaMail 1.1
• JAF 1.0
• RMI-IIOP 1.0
• JavaIDL (J2SE 1.2)
• Roles-based authorization

6

• EJB 2.0 Highlights

• Message Driven Beans
• Container Managed Relationships
• Portable-Finder Query Expressions (EQL)
• Lazy Activation and Dirty Detection
• Local Bean and Home Interfaces
• Select Methods
• Custom Home Methods
• Re-introduced Run-As
• Interoperability based on IIOP

7

• WebSphere Brand (and related) Products

B2C
B2E
Process Automation
e-Markets
B2B
Lotus Domino
WebSphere B2B Integrator
WebSphere Commerce Suite
MQSeries Workflow
WebSphere Transcoding Publisher
WebSphere Everyplace Suite
WebSphere Studio
WebSphere Homepage Builder
WebSphere Site Analyzer
Tivoli Policy Director
WebSphere Business Components
WebSphere Voice Server
VisualAgefor Java
WebSphere Edge Server
WebSphere Personalization
WebSphere Host Integration
VisualAge Application Rules
MQSeries Integrator
VisualAge Generator
WebSphere Portal Server
WebSphere Application Servers
MQSeries
8
Service Oriented Architectures Web Services

• Business functions that are
• Invoke-able over the Internet/Intranet
• Using transports such as HTTP and SMTP, and
  others
• Note Locally optimized transports are
  interesting too
• That typically use XML for information
  interchange
• Building blocks for more complex Web applications
• Success in the Internet requires loose coupling
• Low technology barrier to entry -- HTTP and XML
• Few temporal constraints -- no long locks, allow
  think time and latency
• High version attenuation -- enable independent
  development cycles for interface changes
• Interoperability must be preserved
• Open Source provides reference implementations
• J2EE and other standards relavent to implementing
  business services

9
Service-Oriented Architectures
Service Registry
Service Requester
Service Provider
10

• Leveraging Simple Beginnings

• Short Term
• Web services are a way of gaining access to
  business function over the internet through
  programmatic interfaces enabled by HTTP and SOAP
• Longer Term
• Web services are a way of describing business
  function that can be accessed over a variety of
  communication protocols
• Focus is on WSDL
• Different binding protocols offer different
  qualities of service -- loose vs. tight coupling
• SOAP/HTTP -- un-reliable, but ubiquitous,
  internet enabled
• SOAP/HTTP-R -- reliable, but less ubiquitous,
  internet enabled
• SOAP/SMTP -- mail-oriented, high latency,
  store-forward
• SOAP/JMS or XML/JMS -- asynchronous, high
  latency, leverages existing providers
• RMI/IIOP -- synchronous, low latency,
  standardized service contexts
• Choose the binding protocol that meets the needs
  of the business situation
• Resolve the programming model issues of protocol
  transparency

11
Multiple Protocol Endpoints Inbound Messages

• EJB
• SessionBean

12
WebSphere ApplicationServer

• DB2

Stored Procedure "A"
Private UDDI
Stored Procedure "B"
Generic Query Invoker
SOAP Router
XMLExtender
XMLExtender
Public UDDIs
Dept Table
SOAP Requests/Replies
EmployeeTable
Virtual WebData
ServiceProviders
SOAP Clients
DB2 Clients
13

• Intra-Enterprise Integration

Work Assignment (people, organization, role,
level)
Business model
Workflow activities
- manual - program

Application integration
Applications - interactive - automatic
client/ server apps
MQSeries TXSeries CICS IMS
other app's
ActiveX OLE DCOM
Java Corba
Lotus Notes
front-end back-end
14

• Inter-Enterprise Computing

15
Discussion Topics

• What is the role of XML?
• A data representation for information exchange or
  more?
• How does XML fit into the J2EE model?
• How do you map persistence to XML stores?
• Synchrony vs. Asynchrony
• Do the messaging models and application server
  models converge?
• What do we tell customers?