WebSphere Application Server 8.5

egyptiannorweiganInternet and Web Development

Oct 31, 2013 (3 years and 7 months ago)

147 views

© 2012 IBM Corporation

WebSphere Application Server 8.5


Ankur Goyal

IBM WebSphere

© 2012 IBM Corporation

2

WAS V8.5 Delivers

Unparalleled Application Development and Management Environment, Rich User
Experiences…Faster

Developer Experience


Operations and Control

Fast, flexible,

and simplified

application
development

Intelligent
Management
& Enhanced
Resiliency

Improved
Operations,
Security, Control
& Integration


Application Resiliency


New Liberty Profile


Enhanced WAS ND


Improved Operations

© 2012 IBM Corporation

3

3

Dynamic Server Profile

Not static like Web Profile


determines by app at a fine
-
grained level

Developer First Focus

Simplified, shareable server config (like a
dev. artifact). One XML file or several to
simplify sharing & reuse of config

Lightweight runtime

Small memory footprint:

(60MB for TradeLite)

Integration with ND Job Mgr

Optionally manage server
lifecycle through ND Job Mgr

Fidelity to full profile WAS

Same reliable containers & QOS
(easy migration from dev to ops)

Dynamic Runtime

Adding features & updating
configs does not require
server restart

A highly composable, dynamic Server profile

Popular Platforms

Adds MAC OS for
development

Incredibly fast:


start times: < 5 secs

Small Download
:

< 50MB


WAS v8.5

Liberty Profile

Unzip Install & Deploy

IM or unzip to install. Unzip
deploy of server + app + config

Integrated Tooling

Powerful tools. Simple
Eclipse feature

Lightweight “Liberty” Profile


For Web and Mobile Applications

© 2012 IBM Corporation

4

Highly Composable Runtime Based in ‘Features’

4

runtime services

config model


Java EE support


WAS Extensions


Traditional WAS
profile

Liberty profile

runtime (osgi) services

http transport

webcontainer

app manager

jsp

jsf

runtime (osgi) services

http transport

webcontainer

app manager

web app security

Servlet
-
3.0

JSF
-
2.0

webAppSecurity
-
1.0

Servlet
-
3.0


servlet
-
3.0

jsp
-
2.2

jsf
-
2.0

jpa
-
2.0

jdbc
-
4.0

ssl
-
1.0

jmx
-
1.0

jta
-
1.1

jax
-
rs 1.1 *

webappsecurity
-
1.0

wab
-
1.0

blueprint
-
1.0

ldap

beanvalidation 1.0

© 2012 IBM Corporation

5

Creating the Production Image

Install

add

WLP = WAS Liberty Profile

Installation Manager,

Or zip download

Manually,

Eclipse,

Or RAD

Manually,

Eclipse,

or RAD


Repackage everything,

or subset needed by server

WLP

SDK

server

app

WLP

SDK

WLP

SDK

server

app

server

app

WLP

SDK

server

app

WLP

SDK

server

app

WLP

SDK

server

app

WLP

SDK

server

app

WLP

SDK

server

app

WLP

SDK

server

app

© 2012 IBM Corporation

6

Non
-
destructive update of WLP and SDK

Server2

V1

WLPV1

SDKV1

App1V1

App2V1

Server1

V1

Server2

V1

WLPV1

SDKV1

App1V1

App2V1

Server1

V1

Server1

V2

SDKV2

WLPV2

update

Server1

V2

SDKV2

WLPV2

-

Deploy new configuration: Server1v2, SDKV2, WLPV2

-

Stop Server1V1 and start Server1V2

-

To roll back: stop Server1V2 and start Server1V1

© 2012 IBM Corporation

7

Non
-
destructive update of server and application

Server2

V1

WLPV1

SDKV1

App1V1

App2V1

Server1

V1

Server2

V1

WLPV1

SDKV1

App1V1

App2V1

Server1

V1

Server1

V2

update

Server1

V2

-

Deploy new server and application: Server1V2 and App1V2

-

Stop Server1V1 and start Server1V2

-

To roll back: stop Server1V2 and start Server1V1

App1V2

App1V2

© 2012 IBM Corporation

8

Liberty Profile


Startup & Footprint

8


The problem of a lightweight
development environment in
WebSphere has been solved!



Liberty Profile startup &
footprint are on par with
Tomcat.



Liberty Profile starts up in
less than half the time of
JBoss Web profile.




Note: Tomcat , JBoss, and GlassFish were
measured with the HotSpot JDK, while Liberty
was measured with the IBM JDK.

System Info:

Lenovo T60p
-

2 x 2.16 GHz Intel Core Duo T2600



2GB RAM, Windows XP 32
-
bit

Apache Tomcat 7.0.12

JBoss Community Edition 7.0 Web Profile server

GlassFish Server 3.1 Open Source Edition Web Profile

WAS V8.5 Liberty Profile

(All servers had the TradeLite benchmark application installed)

© 2012 IBM Corporation

9

Liberty Profile
-

Throughput

9


A lightweight server that can
service requests with the
speed of a full production
server!



Liberty Profile provides up to
20% better runtime
performance than JBoss and
25% better than Tomcat.






Note: Tomcat , JBoss, and GlassFish were
measured with the HotSpot JDK, while Liberty
was measured with the IBM JDK.

System Info:

IBM x3550


4 x 1.86 GHz Intel Xeon E5320, 8 GB RAM



RedHat Linux 5.3 32
-
bit

Apache Tomcat 7.0.12

JBoss Community Edition 7.0 Web Profile server

GlassFish Server 3.1 Open Source Edition Web Profile

WAS V8.5 Liberty Profile

(All servers had the TradeLite benchmark application installed)

© 2012 IBM Corporation

10

Intelligent Routing

Intelligent Management

Extending QoS through autonomic computing

Dynamic
Clustering

Self
-
Optimizing

StockTrading 1.0

StockTrading 3.0

Finance 3.0

Application
Edition
Management

Self
-
Managing

StockTrading 2.0

Finance 4.0

Health
Management

Self
-
Protecting

Self
-
Healing

© 2012 IBM Corporation

11

11


Automatically detect and handle application health problems


Without requiring administrator time, expertise, or intervention


Intelligently handle health issues in a way that will maintain
continuous availability


Each health policy consists of a condition, one or more actions, and a
target set of processes


Includes health policies for common application problems


Customizable health conditions and health actions

Health Management

Sense and respond to problems before end users suffer an outage


Comprehensive
Health Policies


Customizable
Health
Actions


Customizable
Health
Conditions


© 2012 IBM Corporation

12

Health Management


Health Policies


Health policies can be defined for
common server health conditions


When a health policy's condition is
true, corrective action execute
automatically or require approval


Notify administrator (send email or
SNMP trap)


Capture diagnostics (generate
heap dump, java core)


Restart server


Excessive response time means you
are monitoring what matters most:
your customer's experience!


Application server restarts are done in
a way that prevent outages and
service policy violations


Each health policy can be in
supervise or automatic mode.
Supervise mode is like training wheels
to allow you to verify that a health
policy does what you want before
making it automatic.

Helps mitigate common health problems before outages occur

Health Conditions



Excessive request timeouts:

% of timed out requests



Excessive response time:

average response time



Excessive garbage collection:
% of time spent in GCs



Excessive memory:
% of maximum

JVM heap size



Age
-
based:

amount of time server has been running



Memory leak:

JVM heap size after garbage collection



Storm drain:

significant drop in response time



Workload:

total number of requests

© 2012 IBM Corporation

13

Health Management


Custom Health Actions

Provides flexibility by allowing the definition of custom actions
allowing administrators to define an action plan to be carried out
when the unhealthy situation detected.

© 2012 IBM Corporation

14

14


Upgrade Applications without interruption to end users


Concurrently run multiple editions of an applications


Automatically route users to a specific application


Multiple editions can be activated for extended periods of time


Rollout policies to switch from one edition to another without service loss


Easily update OS or WebSphere without incurring down time


Easy
-
to
-
use edition control center in admin console, plus full scripting
support

Application Edition Management

Applications can be upgraded without incurring outages

Validation

Mode

Rollout

Policies

Concurrent

Activation

© 2012 IBM Corporation

15

Application Edition Management

Operational Scenario


Concurrent Activation

© 2012 IBM Corporation

16

16


Associate service policies with your applications


Let WebSphere manage to the service goals


Programmatically respond to spikes in demand


Add or reduce application server instances as appropriate


Automatically recover from infrastructure problems


Includes automatic start and stop of cluster members based on load
for MQ
-
driven applications



Decrease administrative overhead required to monitor and diagnose
performance issues

Dynamic Clustering

Proactively provision and start or stop application servers based
on workload demands to meet Service Level Agreements

© 2012 IBM Corporation

17


Dynamic Clustering


A Dynamic Cluster is a virtual cluster of
servers (JVMs) hosting the application
that lives on group of nodes


What is dynamic about a dynamic
cluster?


App server definitions are dynamically
created or deleted based upon the
node membership policy (e.g. Servers
are created/deleted if a node is added
to /removed from a node group)


App server definitions are automatically
updated when the server template
associated with the dynamic cluster is
updated


App servers are started / stopped
based upon current application
demand & service policies

© 2012 IBM Corporation

18

18


Service policies are used to
define application service
level goals


Allow workloads to be
classified, prioritized and
intelligently routed


Enables application
performance monitoring


Resource adjustments are
made if needed to consistently
achieve service policies

Service Policies define the relative importance
and response time goals of application services;
defined in terms the end user result the
customer wishes to achieve

What is a Service Policy?


Easily allows an administrator to specify the relative importance of
applications and optionally a response time goal. WebSphere then
manages your applications according to this policy.

© 2012 IBM Corporation

19


Requests are prioritized and routed based upon administrator defined
rules


Flexible policy
-
based routing and control


On Demand Router (ODR) is the focal point for Intelligent Routing


A routing tier that’s aware of what’s happening on the application
server tier


Application server utilization, request performance, etc…


Route work to the application server that can do it best


Provide preference for higher priority requests


Integrates with Health Management and Dynamic Clustering






Intelligent Routing

Improves business results by ensuring priority is given to
business critical applications

© 2012 IBM Corporation

20

Intelligent Management Scenario

The On Demand Router applies sophisticated classification and flow control
algorithms to intelligently manage workload

WebSphere On Demand Router
(ODR)

Classification

Prioritization and
Flow Control

Routing and Load
Balancing

Placement
Executions

Node 2

Node 3

Node 4

Node 5

Placement

Decisions

WebSphere Decision
Makers

Application Demand

Resource State

Routing, Health and
Service Policies

Node 1

© 2012 IBM Corporation

21

Intelligent Management Data Logging


WebSphere Application Server ND contains comprehensive data
logging of applications, users and resources; content in logs is
configurable and aggregated for easily hooking into accounting and
charge
-
back products


Comprehensive logging

of application,
resource and workload information
across autonomic systems


Historical trend analysis

using either
pre
-
packaged or customized reports
with innovative visualization
techniques


Easily hookup to accounting and
chargeback systems such as Tivoli
Usage and Accounting Manager

© 2012 IBM Corporation

22

Memory leak detection & Protection in WAS

WebSphere Application Server V8.5
:


Ability to mitigate memory leak when stopping apps


Ability to prevent leaks, receive leak warnings and get heap/system dumps


MBean to list stopped apps that have memory leaks

22

Reduce possibilities

of memory leak in

your applications

Get enough info.

if leak is detected

to help fix my app

List stopped

apps that have

memory leaks

© 2012 IBM Corporation

23

IBM J9 JVM competitive advantages

IBM J9

Hot Spot,

OpenJDK

Fast garbage collection for large heap sizes (>4GB)
-

-
Xgcpolicy:balanced

Yes

No

System class data sharing for reduced memory footprint and faster startup

Yes

Client only

Application class data sharing for smaller memory footprint and faster startup

Yes

No

Avoid JVM restarts due to the PermGen filling up

Yes

No

Compressed 64
-
bit references (for faster runtime and smaller memory)

Yes

Recent

Dump analyzer
-

hang, crash, memory management

Better

Good

Garbage Collection and Memory Visualizer
-

memory usage and performance

Better

No

Memory Analyzer


troubleshoot memory leaks and excessive heap
consumption

Yes

Yes

Health Center


real time monitoring of running virtual machines

Yes

No

Faster performance per core

Yes

No*

© 2012 IBM Corporation

24

IBM WebSphere 11 years of performance leadership

IBM track record


Held the
most

records in ECPerf


FIRST

to publish SPECj2001


FIRST

to publish SPECj2002


FIRST

and ONLY company to publish SPECj2002
Distributed


FIRST

to publish SPECj2004


Was the only vendor to publish for over

13 months


Held #1 spot for most of the time


FIRST

to publish SPECjEnterprise2010


LOWEST

cost per transaction


BEST
performance per core




WAS is
16%

faster per core on same hardware as
WebLogic
1

EjOPS per second per processor core

JBoss
:

0
(never published)

IBM: 524

SPECjEnterprise2010

Oracle: 452

Both benchmark ran on the same model of Intel

Westmere
-
EP processors

(1) SPEC and
SPECjEnterprise2010
are registered trademarks of the Standard Performance Evaluation Corporation
. Results
from www.spec.org as of 04/29/2012 Oracle SUN
Blade Server X6270 M2 452.285 EjOPS/core SPECjEnterprise2010, Oracle Sun Fire X4170 M3


519.386 SPECjEnterprise2010 EjOPS (Orac
le's best SPECjEnterprise2010
EjOPS/core result so far). IBM HS 22 Blade 524.621 EjOPS/core (World Record SPECjEnterprise2010 EJOPS/core result)

© 2012 IBM Corporation

25

Performance


Cost per transaction

© 2012 IBM Corporation

26

Oracle Charges More ... And Provides Less



Oracle requires licenses for backup servers1, IBM doesn't requires licenses for backup
servers, Standby servers, Failover servers

when failover is 10+ days, Remote mirroring
servers


Oracle charges for all CPUs on a server even if "soft
-
partitioned"4

(e.g. with VMware), IBM
charges only for CPUs utilized by WebSphere Application Server Network Deployment


Additional costs for features that are included in WebSphere Application Server Network
Deployment but not in WebLogic Server Enterprise Edition such as Web cache5, Session
initiation Protocol (SIP)6

and the SCA programming model7


Oracle has announced plans to stop support for Itanium platforms but WebSphere still
continues to support Itanium.


http://www
-
01.ibm.com/software/web
servers/appserv/whypay
more/


© 2012 IBM Corporation

27

IBM WebSphere Application Server vs. JBoss:
TCO over 5 years

Hands
-
on analysis of capabilities
revealed that JBoss is 49% more
expensive than WebSphere

Source: Based on the study by Summa Technologies, December 2010

WAS v7 vs. JBoss EAP v5.1

© 2012 IBM Corporation

28


Liberty Profile


Expanded Tooling and WAS
Tooling Bundles


OSGI programming model
enhancements


EJB support in OSGi apps


JDK7 Support


Migration toolkit


Web 2.0 & Mobile Toolkit; IBM
Worklight Integration


SCA OASIS programming
model

WAS V8.5 Delivers

Unparalleled Application Development and Management Environment, Rich
User Experiences…Faster

Developer Experience


Operations and Control

Fast, flexible,

and simplified

application
development


Application Edition
Management


Application Server Health
Management


Dynamic Clustering


New Intelligent Routing
capabilities


Messaging infrastructure
resiliency


Memory leak detection &
protection in WAS

Intelligent
Management
& Enhanced
Resiliency

Improved
Operations,
Security, Control
& Integration


Selectable JDK


WebSphere Batch
enhancements


Admin Security Audit


OSGi Blueprint security
improvements


Cross Component Trace
(XCT)


Enhanced IBM Support
Assistant


Better log and trace filtering


Application Resiliency

© 2012 IBM Corporation

29

© 2012 IBM Corporation

30

TCO for the IBM WebSphere
Infrastructure

vs. Oracle


Software acquisition costs:
IBM up to 80% savings over Oracle


Oracle list price license cost is higher than IBM for comparable products


Oracle charges full license cost for "Warm" backup and DR servers
-

IBM does not


Oracle charges full license cost for "Cold" backup servers when failover is longer than 10 days


Oracle does not allow soft partitioning using VMware or other virtual machines


Oracle does not provide fixes to those who do not have current support
-

IBM does


IBM offers more complete features, thus less 3rd party products needed


IBM offers more flexible packaging (don’t need full license of a “big” suite for all CPUs)


Software support costs:
IBM up to 80% savings over Oracle


Oracle charges 22% for the support
-

IBM charges 20%


Oracle charges for the first year of support
-

IBM includes it for free


Oracle support cost quickly goes back to the % of the list price
-

IBM keeps it at PPA level


Management, administration, upgrade costs:
IBM up to 50% savings over Oracle


IBM provides better virtualization capabilities via WVE plus zSeries platform support


IBM provides faster server provisioning via WebSphere Cloudburst Appliance


Hardware, power, cooling costs:
IBM up to 50% savings over Oracle


IBM requires less hardware (and software) to run the same workload


Downtime and SLA costs:
IBM up to 98% savings over Oracle


Oracle does not always provide transaction integrity under failures


Oracle does not offer self correcting health monitoring capabilities of WVE