Why WebSphere Provides a Superior Foundation - … 06_Why... · Multiple development environments ... Message Broker Integration Server Branch System Human ... Java runtime platform

CTS8-Why IBM is Better 1

Why WebSphere Provides a Superior Foundation

D1 - 06 Why WebSphere Provides a Superior Foundation.ppt 2

Service Combining Frameworks

WebSphere Application Infrastructure

Enterprise Service Bus

PeopleIntegration

Process Integration Information Integration

Partner ServicesApplication Services Data ServicesPeople with Clients

WSDLWSDL WSDL WSDL WSDLWSDL WSDL WSDL



Why WebSphere Is The Right Choice

� We have already seen that WebSphere leads the competition in SOA capabilities…


Typical Enterprise SOA Business Solution

SOAToolingand Run-time

CICS

SAPHigh Speed

Message Broker

Integration Server

Branch System

Information Integration

HumanWorkflow

Models/Simulation

Enterprise Service BusBranch

Headquarters

� IBM WebSphere has a complete solution set

� One development environment (Eclipse)

� Automatic SOA programming tools for business and IT

� Web application server which supports human workflow

� Adapters and tooling for legacy systems

� Portal for customizing user interfaces

� Support for voice and wireless devices

� Information integration

� Enterprise Service Bus to flexibly and reliably connect services

� Microsoft, SAP, BEA, and TIBCO can’t do this

Wireless




Branch Data

Microsoft Can’t Do This SOA Solution

CICS

SAPHigh Speed

Message Broker

Integration Server

Branch System

HumanWorkflow

Models/Simulation


Headquarters

Wireless

� Microsoft .NET missing capabilities

� Multiple development environments

� No automatic SOA programming

� No process simulation and analysis of process models

� Additional development work for human workflow

� Few adapters

� No information integration

� No enterprise service bus

� No high-speed message broker

Source: IBM Software Group Competitive Project Office, 2005


SAP NetWeaver XI Can’t Do This SOA Solution� SAP NetWeaver XI missing

capabilities

� Multiple development environments



� Separate server needed for human workflow

� No adapters for non-SAP applications




� NetWeaver products are primarily implemented in 25 year-old ABAP technology


Branch Data

CICS

SAPHigh Speed

Message Broker

Integration Server

Branch System

HumanWorkflow

Models/Simulation


Headquarters

Wireless




BEA WebLogic Can’t Do This SOA Solution� BEA WebLogic missing capabilities



� No support for disconnected wireless devices

� Few adapters

� Information integration cannot perform SQL queries or update information sources




Branch Data

CICS

SAPHigh Speed

Message Broker

Integration Server

Branch System

HumanWorkflow

Models/Simulation


Headquarters

Wireless



TIBCO Can’t Do This SOA Solution� BEA WebLogic missing capabilities

� Multiple development tools


� No web application server

� No support for disconnected wireless devices





Branch Data

CICS

SAPHigh Speed

Message Broker

Integration Server

Branch System

HumanWorkflow

Models/Simulation


Headquarters

Wireless




Why WebSphere Is The Right Choice

� We have already seen that WebSphere leads the competition in SOA capabilities…

� Now let’s look at some other important considerations for the application infrastructure� Flexible deployment� Build web solutions fast and easy

� Superior performance and scale

� Strong security� Lower cost

� Reliable enterprise operation


On Demand-Style Application RequirementsPortability� Flexible deployment

� Build web solutions fast and easy


� Strong security

� Lower cost




WindowsWindows

WebSphere Application

Server

LinuxLinux


Server

UNIXUNIX(AIX, HP(AIX, HP--UX, Solaris)UX, Solaris)


Server

OS/400OS/400


Server

zOSzOS


Server

J2EE Application

RationalApplicationDeveloper

Open standards Open standards make it possible to make it possible to develop application develop application

once, deploy on once, deploy on multiple platforms multiple platforms

Portability:WebSphere Enables Platform Portability


Product implementation of J2EE available on a wide variety of server platforms

WebSphere Application Server

Defines containers and a profile of standards for the Java runtime platform

J2EE Standards

Runs same Java code on any hardware/operating system Java Virtual Machine

.NET applications only run on Windows.NET applications only run on WindowsABAP applications only run on SAPABAP applications only run on SAP

Portability:Finally Achieved via Standards and Cross-Platform Products




Why Do Customers Want Application Portability?

� Flexibility to choose server platform� Re-use old servers� Scale up to more powerful server� Improve reliability by moving to IBM zSeries Servers

� Consolidate workloads to fewer servers

� Integrate systems from business acquisitions

� Software vendors can sell their solutions into more customer environments

� Avoid vendor lock-in

Make it a strategic decision in your enterprise Never develop a non-portable application again!


On Demand-Style Application Requirements

Basic programming model

� Flexible deployment



� Strong security

� Lower cost




Fundamental Programming Models

IBM

J2EE

Microsoft

.NET+

COM

SAP NetWeaver

J2EE+

ABAP

Which is best for on demand style applications?


Consequences of Building Solutions Using Two Different Programming Models

� Different development and debugging tools

� Different deployment techniques

� Different security models increases risk of security exposures

� Performance degradation due to switching between programming models at runtime

� Multiple development skills

� Multiple system administration skills

� It’s harder and more complicated!



.NET Execution Engine based on Microsoft Intermediate Language (MSIL)

Data Access, XML, and Internet access

Support for server or desktop applications

Programming languagesVB.NET,C#,C++,JScript.NET

Web Services

Windows User InterfaceASP.NET

Base Classes

Common Language Runtime

MSMQ MTS/COM+ IIS WMI

Win32

ADO.NET

WebForms

XML Network

Server Application Desktop Application

Microsoft .NET Framework

.NET applications execute here



.NET Capabilities Trail Java by 5 Years

.NET WebSphere/J2EE

CLR JVM

MSIL Byte Code

JIT JIT

Yes Yes

Yes Yes

Yes Yes

Yes Yes

CLR - Common Language Runtime, MSIL - Microsoft Intermediate Language, JVM - Java Virtual Machine

* Product comparison: .NET 1.1 vs. WebSphere V5.0

Server Side Programming Model

Abstracted Runtime Environment

Abstract Instruction Set

Native Compilation

Object Introspection

Garbage Collection

Exception Handling

Type Safety



What’s Missing in the .NET Programming Model?

Transaction Processing!

� .NET Common Language Runtime does not support distributed transaction management!

� Older COM+ programming model must be used� Serviced Components are the name for .NET objects that

inherit a class which provides access to COM+ transaction services

� Call outside of CLR to execute COM+ transaction services� COM is a legacy programming model, different than .NET

objects


Both updatedUpdateDatabase 2

UpdateDatabase 1

Start Transaction

UpdateDatabase 2

UpdateDatabase 1

FailureStart

Transaction

Rollback TransactionRestore database 1

CommitTransaction

X

On Demand Style Applications Need Transactions

Neither updated



J2EE Features Missing from the .NET Programming Model

� WebSphere/J2EE formalized container concept� .NET CLR does not provide many container services

� WebSphere /J2EE Connection Architecture (J2EE/CA)� .NET does not have a formalized architecture for connecting

to other environments (other than web services)

� WebSphere/J2EE JNDI� .NET has no standardized architecture or services for locating

and accessing remote objects


� Containers provide an environment in which to run application components

� WebSphere/J2EE container simplifies the job of creating server-side applications

� CICS was the industry’s first commercially successful container

Database

Web Container

JSP Page Servlet Enterprise JavaBean

RMI-IIOP EJB Container

J2SE J2SE

JTA

JMS

JAA

S

JavaMail

JAF

Connectors

JAX

PJD

BC

JavaMail

JAF

JTA

JMS

JAA

S

Connectors

JAX

PJD

BC

WebSphere Containers

Container Concept Makes Server-Side Programming Easier



ContainerContainer

1000Clients

1000 Connections1000 Connections++

1000 Processes1000 Processes++

50 MBytes of RAM50 MBytes of RAM++

10,000 Open Files10,000 Open Files

A) No ContainersA) No Containers

10001000ClientsClients

B) With a ContainerB) With a Container

Operating System Operating System is fineis fine

50 Shared Connections50 Shared Connections++

50 Processes50 Processes++

25 MBytes of RAM25 MBytes of RAM++

500 Open Files500 Open Files

50

Operating Operating System diesSystem dies

How Containers Help the Underlying OS


1. Transaction management� .NET must rely on legacy COM+

2. Provide a single-level store programming model so that programmers are free from issues of when and how to load data� .NET programmers must write code

3. Automatically manage pools of EJBs to improve overall performance� .NET programmers must write code

4. Automatically hydrate/dehydrate user components to share system resources and support more clients� .NET programmers must write code

5. Automatically manage pools of DB connections to improve performance and support more clients� .NET data providers are not required to pool DB connections (but

some do)

WebSphere/J2EE Container Function Not Provided by .NET Framework



6. Provide J2EE/CA connection services, including pooling, security, and management� .NET has no standardized architecture for accessing legacy systems

7. Supports the distribution, addressing, and communication required for distributed components� .NET must rely on legacy COM+ and DCOM

8. Reads runtime requirements from deployment descriptions to facilitate simultaneous component reuse by different applications� .NET security policies must be in the code� COM+ transaction declarations must be in the code

9. Provide asynchronous Message-Driven Bean (MDB) initiation� .NET programmers must write MSMQ 3.0 triggers

10. Provide platform transparency� .NET only runs on windows

WebSphere/J2EE Container Function Not Provided by .NET Framework


It’s Smart To Use a Container

These are advantages over .NET

� Easier to write good code� Application programmers do not have to repetitively write

difficult code for each application

� Fewer bugs� Resource management in multi-user environment is complex, is

more likely to have bugs than business code, and those bugs are more difficult to correct

� More flexible administration� Declarative configuration means that administrators can change

policy without waiting for a programmer to make code changes




Benchmarks




� Strong security

� Lower cost



Edison Group Study on Application Server Performance“WebSphere emerged as the winner, with a higher supported transaction rate

than demonstrated by the other platforms."

Source: Edison Group, Inc., Middleware Performance Comparison 12/2004

21368692Multi-tier architecture silk transactions per second:

41495270Flat architecture silk transactions per second:

.NetJBossWebLogicWebSphere

Performance Comparison – Transactions per Second

Transactions per Second

Multi-tier architecture silk transactions per second:Flat architecture silk transactions per second:

DatabaseServer

MiddlewareServer

HTML/HTTPServer

Multi-Tier Architecture

.Net

JBoss

WebLogic

WebSphere

MiddlewareServer

HTML/HTTPServer

Flat Architecture



Real World Experience:Office Depot

� Office Depot replaced Microsoft Web solution with WebSphere

� Needed to scale their e-commerce infrastructure to meet projected growth

� Performance improved by 50% over previous Microsoft solution

� Requires 75% fewer servers than Microsoft solution (160 > 40)

� Solution� WebSphere Application Server V4.0� WebSphere Studio Application Developer� IBM iSeries hardware servers



Track Record

Security Model

Security Operations




� Strong security

� Lower cost




� One bulletin every 3 working days!

� In 1H04 the number of Windows viruses and worms rose by 350% YTY – Symantec Corp

� Gartner estimates that it costs $300,000 per year to manually deploy patches to 1,000 servers.CAGR: Compound Annual Growth Rate

0

100

200

300

400

500

Qua

ntity

Company Reports

Microsoft Security BulletinsAll Products - Cumulative

1998 1999 2000 2001 2002 2003 2004

Microsoft Security Bulletins

Source: ??


Developers create application components

E.g. Build a method to delete accounts

Declare what Role is required to access each resource.E.g. Supervisors can delete Accounts

Application Provider

Application Assembler

Security Administrator

Assign Roles to Users

E.g. Assign Supervisor Role to Kate

use LDAP server as the user directory

Declarative, Roles-Based Access Control

JSPs, servlets, EJBs, etc. are all protected with the same model

WebSphere/J2EE: A Consistent Model for Security



Microsoft – Mixed Security Models

� COM+ role-based access control model is declarative

� .NET role-based access control is specified in source code� [PrincipalPermission(SecurityAction.Demand,Role=“Teller”)]

public void CreateAccount(){….}

� The two models have different class hierarchies and define roles differently

� This means that serviced components (COM+) have a different security model than pure .NET components

� Inconsistent models tend to provide looser security� Increased chance of mistakes, oversight, conflicts



TCO

Five Years of Misery

Frequent Changes




� Strong security

� Lower cost




Application Server Express Pricing

2 Processors0

10

20

30

40

50

60

70

80

90

100

110

120

130

140

150

Thou

sand

s

DB AS OS OS CAL

WA

P Ex

p Li

nux

WA

P Ex

p W

indo

ws

Win

dow

s ST

D

Included in OS

40004000AS

9998(4999 x 2)

9748(4874 x 2)

9748(4874 x 2)

DB

999999349OS

20000(500 x 40)

20000(500 x 40)

--OS CAL

30,99734,74714,097Total

WindowsSTD

WAS EXPWindows

WAS EXP Linux

2 Processors

500 Users

1 Processor0

10

20

30

40

50

60

70

80

90

100

110

120

130

140

150

Thou

sand

s

DB AS OS OS CAL

WAP

Exp

Lin

ux

WAP

Exp

Win

dow

s

Win

dow

s ST

D

Included in OS

20002000AS

499948744874DB

999999349OS

10000(250 x 40)

10000(250 x 40)

--OS CAL

15,99817,8737,223Total

WindowsSTD

WAS EXPWindows

WAS EXP Linux

1 Processor

250 Users


� IBM middleware is delivered as an integrated set of solution components, all running on the J2EE model� Portal, messaging, collaboration, business integration,

commerce, etc.

� Microsoft middleware is still implemented in legacy COM code� Only exception is BizTalk 2004 which is implemented in .NET

� SAP applications are still implemented in ABAP� So is most of NetWeaver

Platform Maturity

Microsoft and NetWeaver customers will face significant migrations




Native COM Native .NET Native Longhorn

Visual Studio

BizTalk

SharePoint Portal

Exchange Server

SQL Server

Windows Server

Office Suite

Windows Client

20072006200520042003200220012000

VS“Orcas”

VS “Whidbey”

VS .NET 2003VS .NETVS 6.0

BizTalk 2004

BizTalk 2002

BizTalk 2000

SPPS 2003SPPS 2001

Exchange2003

Exchange 2000

SQL Server 2005

(Yukon)SQL 2000

LonghornServerWS2003W2k

Office 2003 +VS ToolsOffice XP

LonghornClientWin XP

Biggest Hidden Cost! Five Years of .NET Migration MiseryThree Major Technology Transitions




Customer References!




� Strong security

� Lower cost




� 6000 IBM xSeries servers� 3000 run WebSphere

� 1 Billion page views per day� 20,000 pages per second at peak� 500 Million with WebSphere

� 3.5 Million items listed per day� 240,000 per hour at peak� 17 Million items for sale every day� 295 Million items for sale in 4Q ’03

� 3 Million concurrent users at peak

� 20 Million Service API calls per day� 1 Million for listing new items

Web Site LoadWeb Site LoadRegistered Users Registered Users (Millions)(Millions)

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1

1997 1998 1999 2000 2001 2002 2003 2004

100M Registered Users100M Registered Users1 new user every 1 second 100 Million

ebay Is a WebSphere Site.NET and NetWeaver can’t do this!


� Barista II proof of concept project� Separate tier for EJB business logic� Heavyweight account pages

� 350 pps with 67% CPU utilization on servlet nodes and 73% on EJB nodes

� Demonstrated capability to meet production requirements of 16.5 Milliontransactions per day (Peak/average ratio is 8.7)

accountoverview page

servlet44 nodes

EJB15 nodes

data15 nodes

RS/6000 Winterhawk II

Schwab Brokerage/Trading Applications



On Demand-Style Application Requirements – The Winner Is . . .

�

�

�

�

�

�

IBM Microsoft NetWeaver




� Strong security

� Lower cost



ODI CEO

WebSphere Solved Each Problem

1. All new policy applications are processed quickly and accurately.2. Claims processing is much more efficient.3. We are now attracting new customers and growing again.

…and because a service oriented architecture approach was used to solve these problems, On Demand Insurance now has the flexibility to quickly change to respond to changing business conditions



Are You Portable?

prodigy90.mpg

Documents

Why WebSphere Provides a Superior Foundation - … 06_Why... · Multiple development environments ... Message Broker Integration Server Branch System Human ... Java runtime platform