AAI-2075 Evolving an IBM WebSphere Topology to Manage a Changing Workloa

© 2015 IBM Corporation

Evolving an IBM WebSphereTopology to Manage aChanging Workload

Tom Alcott STSM

Michael Cheng WebSphere Release Architect

Tom Seelbach WebSphere Development

AAI-2075

1

About the Speakers

Tom Alcott [email protected]

Tom Alcott is Senior Technical Staff Member in the United States. He has been a member of the World WideWebSphere organization since 1998. In this role, he focuses on the WebSphere Application Infrastructureproducts. Tom's background includes over 25 years of application design and development on both mainframe-based and distributed systems. He has written and presented extensively on a number of WebSphere topics as afrequent contributor to WebSphere Developer Technical Journal authoring the “WebSphere Contrarian” columnfor the past few years, co-author of a number of IBM Redbooks as well co-authoring the best selling “IBMWebSphere: Deployment and Advanced Configuration”.

Michael Cheng [email protected]

Michael is the WebSphere Release Architect. He has extensive experience developing middleware,specializing in systems management and large scale production environments.

Tom [email protected]

Tom is a WebSphere Architect and Lab Advocate. He has a special interest in virtualization and verylarge scale WebSphere topologies running on leading edge platforms.

Abstract

2

Customers have a huge investment in WebSphere ND infrastructure includinginstallation, development, deployment, management, support, and 3rd partyproducts. At the same time there are significant new workloads. Mobile is drivingvery high transaction rates using new device types. New applications often requireextremely fast response times. The Cloud economy based on Restful services israpidly expanding the very nature of applications. Meanwhile, teams need toimprove efficiency and drive higher density on their platforms.

In this session we will show you how to evolve your WebSphere ND environment tomanage new workloads while preserving your existing investment. See how to addLiberty servers into ND. Explore how Intelligent Management and the ODR extendND to support Restful services. Examine the benefits of a caching tier to improveresponse time and availability. See how to add Worklight into your ND environmentto provide mobile device and application support. Explore continuous delivery anddevOps options for WebSphere ND.

When did IT go from this:

3

Dilbert

C2C – Can to Can protocol v1

To this:

4

Internet

Social &Internet Data

sources

Trading partnercommunities

Mobile, PoS,ATMs Internet

Public Cloud

API

Developer & Customercommunities

Internet of ThingsSensors

APP

APP

Service

Service DBAPPDB

APP

APP

Enterprise

DB

Private Cloud

Master DataManagement

Big Data

API

DMZ DMZ

It evolved

5

Just as we say – yes – we have CICS COBOL coderunning critical apps in our enterprise today…

Our kids will be asking us - where the source code forC2C protocol feature? (can 2 can)

<server description="new server"><featureManager>

<!– elbonian protocol support --><feature>c2c-1.0</feature> </featureManager>

</server>

Liberty server.xml:

Agenda

6

• Overview of customer's current investment in ND

• Topology overview and the expanding universe

• Overview of WAS

• Adding resilience and flexibility via Intelligent Management

• Adding Liberty to your ND topology

• Supporting extreme response and transaction rate requirements

• Mixing batch into the infrastructure

• ND in your dev ops environment

• ND in Cloud environments

Customer investment in WebSphere ND

7

• More than 10,000 WebSphere customers• > 70% of customers run ND

• > 30% overall market share

• Huge ecosystem around:• installation, development, deployment, management, support,

WebSphere family products, 3rd party products....

• Scripting: millions of wsadmin and other scripts

• Know how, education, course-ware, books, careers

WAS is the Java Foundation for IBM SoftwareOver 300 IBM offerings embed

or build upon WAS

8

9

The topology of a Traditional Enterprise

APP

APP

Service

ServiceDBAPPDB

APP

APP

Enterprise

DB

Applications andServices

DatabasesIntegration

Enterprise ServiceBus

10

The topology of an Integrated Digital Enterprise

Internet


sources



Public Cloud

API



APP

APP

Service

Service DBAPPDB

APP

APP

Enterprise

DB

Private Cloud


Big Data

API

DMZ DMZ

Overview of changing workload

11

• Scaling• WebSphere ND is a de facto enterprise entry into cloud

• Ever increasing demand

• Batch• What's old is new

• Continuous Delivery / devOps• changes the way you build your development, test, and

deployment approach

• Cloud integration / Hybrid Cloud

Overview of WAS

WebSphere Application Server 2015

Qualities of Service and Enhanced management

WAS Liberty profileincluded w/ Base

WAS Liberty profileincluded w/ ND

Liberty Core

Everything in Liberty Core+ Java messaging+ Web services+ noSQL DB

Everything in Liberty Base+ Enterprise class clustering+ Topology management

Web, mobile, OSGi appsJava EE Web ProfileSubset of Liberty profileHigh performance

transactions

Web, mobile, OSGi,advanced prog models

Full Java EE Distributed transactions Advanced security

Everything in WAS Base+ High availability+ Intelligent mgmt+ High scalability

and more…

Increasing number of servers & concurrent users

WAS Liberty Core WAS (Base) WAS ND or z/OS

WASfull profile

WASfull profile

13

WAS ND V7 WAS ND V8 WAS ND V8.5

WAS ND V8.5.0.1

WAS ND V8.5.0.2

WAS ND V8.5.5

WAS XD

Object Grid

VirtualEnterprise

ComputeGrid

ExtremeScale

IntelligentManagement

Batch FP

* Client Only on z/OS

*

Liberty

Evolution of WebSphere ND

14

15

WAS Operational Roadmap

WebServerTier

AppServerTier

ODRTier

ND Cell

WebServerw/ ODRLIB

TierFull and LibertyProfile Servers

ND Cell

WebServerw/ ODRLIB

Tier

Liberty Collectiveor ND Cell

WAS ND 8.5.5.4+WAS ND 8.5.5.4+

WAS ND 8.5.5WAS ND 8.5.5

WAS ND 8.5WAS ND 8.5

Full and LibertyProfile Servers

WAS v8.5 GA• Lightweight Liberty profile with

z/OS extensions• Intelligent Management &

resiliency (WVE, WCG merged)• WOLA enhancements for z/OS• Java SE 7• WAS 8.5 HV for PureApp

J2EE1.4

WAS v7GA

JEE5

WAS v8 GA•Web 2.0 & Mobile FEP•WAS v8.5 Alpha, Beta•Migration Toolkit Refresh•WAS Tools Bundles

WAS v8.5.5 GA• Liberty Profile

• New prog models• Web Profile Certification• Clustering & resiliency• Extensibility SPI to add

Liberty Features• WAS Liberty Core• Service Mapping

JEE6

WAS v6.1GA

2006 2007 2008 2010 20122011 20132009 2014

15 years of Leadership & Trusted Delivery

WAS v8.5.5.x / BETA• New Java EE7 features

• Web sockets• Java EE Concurrency• Initial EJB 3.2

• Liberty JCA feature (8552)• Open ID 2.0 authentication• Tools updates, adding

Eclipse Kepler• Liberty z/OS Local Adapters

(WOLA) (8552)• z/OS Connect (8552)

Latest

WebSphere Application Server

16

Continuous Delivery of new function

• Beta drivers every month

17

• GA features delivered regularly via Liberty Repository

servlet-3.1websocket-1.0jsonp-1.0openid-2.0couchdb-1.0+others

4Q2014

• GA delivery of Java EE7 features started 4Q 2014

2Q2014

jca-1.6adminCenter-1.0zConnect-1.0+ others

jsp-2.3jdbc-4.1websocket-1.1spnego-1.0

1Q2015

Repository features (up to 8.5.5.4)

webProfile-6.0webProfile-6.0

zosSecurity-1.0 zosTransaction-1.0 zosWlm-1.0

zosnd

mongodb-2.0wsSecurity-1.1

wmqJmsClient-1.1

wasJmsServer-1.0

jmsMdb-3.1

wasJmsClient-1.1jaxws-2.2

jaxb-2.2

wasJmsSecurity-1.0

base

wab-1.0

concurrent-1.0

collectiveMember-1.0

restConnector-1.0

sessionDatabase-1.0

ldapRegistry-3.0

webCache-1.0

jaxrs-1.1

distributedMap-1.0

osgiConsole-1.0

json-1.0

timedOperations-1.0monitor-1.0

oauth-2.0

blueprint-1.0

servlet-3.0

jsp-2.2

jsf-2.0

ejbLite-3.1 jdbc-4.0

jndi-1.0

appSecurity-2.0

managedBeans-1.0

core

ssl-1.0

beanValidation-1.0

cdi-1.0

jpa-2.0

zosConnect-1.0

zosLocalAdapters-1.0

adminCenter-1.0

jca-1.6

servlet-3.1

scalingController-1.0

scalingMember-1.0

dynamicRouting-1.0

openid-2.0

openidConnectServer-1.0

websocket-1.0

openidConnectClient-1.0

couchdb-1.0

serverStatus-1.0

repository-only

jcaInboundSecurity-1.6mdb-3.1

jms-1.1

jsonp-1.0

collectiveController-1.0 clusterMember-1.0

New features continuallymade available via theLiberty Repository

• Production-ready & fully-supported on entitledsupported editions

Topology examplesand evolution

WebSphere ND Topologies

20

HTTP Server

WebSphereplugin

BrowserClient

JMXClient

RESTClient

DeploymentManager

NodeAgent

NodeAgent

NodeAgent

ColletvieController

ColletvieController

CollectiveController

Liberty profile server

Full profile server

Dynamiccluster

Dynamiccluster

Staticcluster

Staticcluster

Assistedlife cycle

dynamiccluster

…

CatalogServer

GridContainer

GridContainer

GridContainer

GridContainer

GridContainer

GridContainer

WXScaching

WXS server

21

WAS Operational Roadmap

WebServerTier

AppServerTier

ODRTier

ND Cell

WebServerw/ ODRLIB

TierFull and LibertyProfile Servers

ND Cell

WebServerw/ ODRLIB

Tier

Liberty Collectiveor ND Cell

WAS ND 8.5.5+WAS ND 8.5.5+

WAS ND 8.5.5WAS ND 8.5.5

WAS ND 8.5WAS ND 8.5

Full and LibertyProfile Servers

22

Large Topology

• Full Profile Cell

• Up to 1000 JVMs tested

– Requires lots of patience

– Core group

configuration

– Lots of tuning

• 200 JVMs a typical practical

limit

• Liberty Profile Collective

• Scales well to 10,000 JVMs

• Used 5 collective controllers

– Mostly out of the box

– Minimal tuning for heap,

OS, and timeout.

HTTP Server

WAS Full ProfileServer X

AppsApps

WAS Full ProfileServer Y

AppsApps

WAS ND Application Cluster

WAS Full ProfileCluster Member

AppsApps


AppsApps

Node Agent Node Agent

WebSphereplugin/ODRLib

WAS NDAdministrative Cell

host 2host 1

Feat

ur

e

Man

ag

er

HTTP

T

ra

ns

p

or

t

Appl

ic

at

io

n

M

anag

e

r

serv

le

t-

3.

0

j

sp-

2.

2

a

pp

s

ec

ur

it

y-1.

0

rest

co

n

nect

or

-1.0

j

pa

-2.0

Apps

Liberty ProfileServer 1

Apps

Feat

ur

e

Man

ag

er

HTTP

T

ra

ns

p

or

t

Appl

ic

at

io

n

M

anag

e

r

serv

le

t-

3.

0

j

sp-

2.

2

a

pp

s

ec

ur

it

y-1.

0

rest

co

n

nect

or

-1.0

j

pa

-2.0

Apps


Apps

Hybrid Management

JMXClient

BrowserClient

DeploymentManager

Admin App

• ND Cells can alsoinclude Libertyservers on nodes

• For “Assistedlifecycle”management

• Uses NodeAgent

• Requires NDlicenses

23

HTTP Server

WAS Full ProfileServer X

AppsApps

WAS Full ProfileServer Y

AppsApps

Messaging Cluster

WAS ND Application Cluster


AppsApps


AppsApps

Node Agent Node Agent

…

CatalogServer

WXSCachingTier

GridContainer

GridContainer

GridContainer

GridContainer

GridContainer

GridContainer

WebSphereplugin/ODRLib

WAS NDAdministrative Cell

Routinginformation

host 3

Feat

ur

e

Man

ag

er

HTTP

T

ra

ns

p

or

t

Appl

ic

at

io

n

M

anag

e

r

serv

le

t-

3.

0

j

sp-

2.

2

a

pp

s

ec

ur

it

y-1.

0

rest

co

n

nect

or

-1.0

j

pa

-2.0

Apps


Apps

host 2host 1

Feat

ur

e

Man

ag

er

HTTP

T

ra

ns

p

or

t

Appl

ic

at

io

n

M

anag

e

r

serv

le

t-

3.

0

j

sp-

2.

2

a

pp

s

ec

ur

it

y-1.

0

rest

co

n

nect

or

-1.0

j

pa

-2.0

Apps


Apps

Feat

ur

e

Man

ag

er

HTTP

T

ra

ns

p

or

t

Appl

ic

at

io

n

M

anag

e

r

serv

le

t-

3.

0

j

sp-

2.

2

a

pp

s

ec

ur

it

y-1.

0

rest

co

n

nect

or

-1.0

j

pa

-2.0

Apps


Apps

F

ea

t

ur

e

Ma

n

ag

er

H

TT

P

T

ra

ns

port

A

pp

l

ic

at

io

n

M

anag

er

s

er

v

le

t-

3.

0

j

sp

-2.2

a

pp

secu

r

it

y-1.

0

r

es

t

co

nn

ec

tor

-1.0

j

pa

-2.0


AppsApps

LibertyCollective

Feat

ureManager

HTT

PTransport

Application

Man

ager

servl

et-3.0

jsp-

2.2

appsecurity-

1.0

restc

onnector-1.0

jpa-2.0

Liberty CollectiveController

AppsApps

Routinginformation

Dynamic Routing and Caching

JMXClient

BrowserClient

DeploymentManager

Admin App

24

Improve Resilienceand Scale of yourTopology

Intelligently Adopting Intelligent Management

26

• Typical WAS-ND Deployments – pre IntelligentManagement

• Cell Isolation and/or Physical Server Isolation• Employed to Ensure Resource Allocation

• Facilitates Chargebacks

• Minimizes “Bad Apple Application” Impact

• “Just in Case“ Server Clusters• Clusters of 2 (or more) for Availability

• We often see 5% or less utilization of the clusters

• Single Server is Adequate for Throughput and Scalability

Health Management Monitor the status of your applications Sense and respond to problem areas. Continuous availability during failures: application,

middleware, or hardware.

Self-protecting

Self-healing

Intelligent Management Overview

Autonomic Computing - Providing Continuous Availability

Enable interruption free application rollout. Continuous availability during app updates.

App Edition Mgmt

Self-managing

Dynamic Clusters &Auto Scaling Elastically scale applications based on demand and

service policies. Continuous availability during traffic surges.Self-optimizing

Intelligent Routing Quickly route around slow or failing servers Automatically route to Auto Scaling Clusters Multi-cell load balancing & failover. Request prioritization

& overload protection (CPU & mem.) Continuous availability during soft-hang or cluster/cell

outage.

Self-configuringSelf-protecting

WAS ND full profile

WAS ND full profile

WAS ND full and Liberty profile

Dynamic Scale

27

Intelligently Adopting Intelligent Management

28

• Service Policies and Health Policies• Eliminates Cell Isolation and/or Physical Server Isolation

• “Bad Apple application” Impact is Limited

• Provide Application Request Priority

• Visualization Service Provides Metrics• Chargebacks/Cost Allocation for Collocated Applications

• Service Policies and Dynamic Clusters• “Just in Time” Dynamic Clusters of Minimum Size “1”

• Allow IM to Adjust as Needed for Workload

• Eliminates Over provisioning and Reduces Server Sprawl

• Lowers Hardware, Software and Administrative Costs

• Effective Only if You Don’t Treat IM as a “Bolt on”

• Don't Go Overboard with Cell Consolidation

Intelligent Management in 8.5.5.x:Adding Liberty to your ND topology

Adding Liberty servers to your topology

30

• Built on Intelligent Management Middleware Server support• Available in v8.5.5.1

• Dynamic clusters for Liberty

• wsadmin scripting and console access to Liberty• Config access (server.xml)

• Lifecycle (start/stop/status)

• Log access (messages.log, etc)

• Based on “assisted lifecycle” support

Liberty managed from ND cell

31

ND Cell Liberty operations:

-AdminTask.createLibertyServer('nodename','[-name ServerName]')

- Add Liberty to cell- Create dynamic cluster- Start/stop server/cluster- Edit config (server.xml)- View logs (messages.log)- Assign scaling policy- Create health policy

Benefits:Incremental approach to Liberty dynamic clustersLeverage existing WAS ND management infrastructure and skills

Use Java ODR or Intelligent Management for Webservers (ODRLib)

ND Cell

ODR Cluster

Dynamic Cluster

nodeagent

ODR

node

ODR

node

dmgr

WLPWLPWLP

nodeagent

node

appserver

appserver

appserver

nodeagent

node

nodeagent

http

WLP=WebSphere Liberty Profile

HTTP

ODRLib

http

Adding a caching tier to yourtopology

Adding a caching tier to your topology

33

• WebSphere eXtreme Scale (WXS)

• Do You Find Yourself Asking:

• What's the Maximum Heap Size of a 64-bit JVM ?

• What's the Maximum Heap Size for a 64-bit JVM with CompressedReferences?

• Furiously Monitoring and Tuning a Database Used for Applicationand/or Transient Data

34

Web Server Tier Back-end SystemsDatabase Tier

App Server Tier Elastic Cache

WebSphere

Application Server

DB2

ImprovePerformance,Scalability &Availability

Highly Scalable WebApplications

Data-intensiveApplications

ExtremePerformance

Mobile Transactions

IBM HTTP

Server

IBM

Mo

bil

eP

latf

orm

Elastic Caching Minimizes Transaction Overload

35

What is a Data Grid ?

Elastic, scalable, coherent in-memory cache

Dynamically caches, partitions, replicates and manages application dataand business logic across multiple servers

Provides qualities of service such as transaction integrity, high availability,and predictable response times

Automatic failure recovery

on-the-fly addition / removal of memory capacity

Primary and Replica shards

Distributed in-memory object cache

Capable of massive volumes of transactions

Self-healing, allow scale-out / scale-in

Splits a given dataset into partitions

36

Client first checks the grid before using thedata access layer to connect to a back enddata store.

If an object is not returned from the grid (acache “miss”), the client uses the dataaccess layer as usual to retrieve the data.

The result is put into the grid to enablefaster access the next time.

The back end remains the system ofrecord, and usually only a small amount ofthe data is cached in the grid.

An object is stored only once in the cache,even if multiple clients use it. Thus, morememory is available for caching, more datacan be cached, which increases the cachehit rate.

Improve performance and offloadunnecessary workload on back-endsystems. Adding extra hardware is not easy

Side Cache

HTTP Session Replication

37

• Many enterprise applications today requireHTTP session persistence.

• A grid of JVMs can be established with thesole purpose of storing HTTP session (orany java) objects.

• Isolating the application runtime from gridruntime, thereby, freeing up the JVM heapfor application use.

• Provide linear scalability to accommodategrowth (in # of sessions or size of sessionobjects).

• Providing replication and management ofsession objects within the grid.

• Can even store session objects acrossdatacenters.

Configuring Session Management to Use Elastic Cache

38

• 1. Select Session management fromthe Enterprise Applications panel forthe application you wish toconfigure.

• 2. Select eXtreme Scale sessionmanagement setting from theSession management panel

• 3. Select Enable sessionmanagement and input theinformation for your elastic gridenvironment

• DONE!

Mixing Java Batch into yourtopology

40

Roll Your Own (RYO) Batch

Seems easy – even tempting

Message-driven Beans or

CommonJ Work Objects or …

But …

No job definition language

No batch programming model

No checkpoint/restart

No batch development tools

No operational commands

No OLTP/batch interleave

No logging

No job usage accounting

No monitoring

No job console

No enterprise scheduler integration…

Sound Familiar ?

7

MessageDrivenBean

msg queuejob definition

CommonJW ork

job definitionWeb

Service

create

41

Comprehensive Java/J2EE batch solution

Built on WAS, leverages inherent QoSTransactions

Security

High availability

etc

Core componentsJob Entry Scheduler

Job dispatcher/WLM

Operational controls/monitoring

Batch Container

Batch application lifecycle

Input/output streammanagement

checkpoint/restart

WebSphere Batch

15

Off-the-shelf solutionfor batch modern

batch

Platform for enterprisebatch

modernization

Unified batch architectureacross z/OS and

distributed platforms

42

WebSphere Batch

Eclipse (or RAD)

BatchSimulator Batch

UTE(WAS standalone)

BatchPackager

BatchQA, Production

(WAS ND)

BatchPOJOs

BDSFW

BatchData

StreamFW

Continuous Delivery and DevOps

What are Continuous Delivery and DevOps?

44

• Continuous Delivery:

• Incremental and quick delivery of new production ready code, e.g., onevery change, hourly, daily

• Shortest time to market

• Always ready for production, but actual release schedule is a businessdecision.

• DevOps: Development + Operations

• Usually in the context of supporting Continuous Delivery

• Relies on automation

• Infrastructure self service

• Automated regression testing

45

Enable your Dev Lifecycle with agile integration options

Third party software integration

Some examples of life cycle software thatintegrates with WAS and WAS Liberty to seizemarket opportunities and reduce time to feedback

Jenkins

IBM UrbanCodeDeploy

Dev Ops Cycle of an Application

Application Release Management

Cloud environments

BuildDevelopment Package Repo Test Env Prod EnvStage Env

Building a test topology

46

Pre-built topology

• Less automation

• Less hardware re-use

• Environment up even if notests being run

• More time to ramp up newapplications

Rebuild on every test

• More automation

• More hardware reuse: only forthe duration of testing

• Less time to ramp up newapplications

Building blocks for fast topology creation

47

• Automation

• Scripting, and other tools

• Configuration templates

• Easy to create new topologies

• shared disk

• Install large shared resource just once, e.g., runtime, large application

• Virtualization

• Allocate/release hardware on the fly

Full Profile Installation

48

• Centralized Installation Manager for remote installation automation

• Register remote Hosts

• Administrative jobs

• install/uninstall/update IBM Installation Manager

• Manage offerings with response files to effect all IBM Installation Managerfunction

• Profile management with response file

• File related jobs: collect file, distribute file, remove file

• Running remote scripts

Full Profile cell creation from template

49

/dmgrNode/node1

backupConfig template.zip

restoreConfig

dmgr dmgr dmgr

addNode addNode addNode

addNode -asExistingNode option

New in WAS 8.0

Full Profile: Leveraging Shared Disk

50

• See Sharing A WebSphere Application Server V8 Installation here:

http://www-03.ibm.com/systems/z/os/linux/resources/doc_wp.html

• Consider lighter weight App deployment options such as -zeroEarCopy -nodistributeApp

See Options for accelerating application deployment

profile

Nodeagent

WAS runtime

applications

sharedfile

system

localdisk

profile

Appserver

dmgr

http://www.ibm.com/developerworks/websphere/techjournal/0812_webcon/0812_webcon.html

http://www.ibm.com/developerworks/websphere/library/techarticles/0710_largetopologies/0710_largetopologies.html

51

Liberty Collective – Push Out Members with File Transfer MBean

Liberty Controller

WLP

Liberty Clusters

WLP

WLP WLP

Liberty Collective

WebSphere Developer Tools

adm

incl

ient

(e.g

.Jy

thon)

File

Tra

nsfe

rM

Be

an

explodearchive

Liberty ServerPackage

51

Liberty Profile Deployment via Chef

52

• Chef: infrastructure as code

• Consistent deployments

• Variable substitution for different environments via Ruby hash

• Download chef cookbook from Chef website

• wlp cookbook:

• Install Liberty runtime

• Create servers

• Set jvm options

• Create init.d service

• application_wlp cookbook:

• Deploy applications: .ear, .war, .eba

Ways to leverage Cloud in WASND environment

How to leverage Cloud in WebSphere environment

54

• Cloud: resource virtualization:

• Allocate/release cpu/memory/disk/network/OS depending on need

• Different ways to adopt cloud:

• Manually pre-allocate or release “guests” as needed.

• Script “guest” allocation/release into your deployment automation, especially for“rebuild on every test” pattern

• Intelligent Management elasticity mode, dynamic clusters

• Leverage IBM pattern engine for pattern based deployment

• Adopt Platform as a Service (PaaS)

• IBM BlueMix, CloudFoundry

Build Your Own CloudUse virtualized WebSphereApp Server on your hardware

IaaS – AmazonBYOS&L - WebSphere App Server

PaaS - Blue MixComposable servicesLiberty Buildpack

Pure Application SystemsBuild reusable & redeployablepatterns using the WebSphereApp Server

PaaS - Cloud FoundryLiberty Buildpack

IaaS - SoftLayerBYOS&L - WebSphere App Server

WebSphere Application Server - Flexibility in cloud

Public CloudEconomies

Time to Market

Shared EverythingEconomics

Packaged Services

Total ControlMaximum FlexibilityMaximum Security

On-Premises IaaS PaaS

55

IaaS – Microsoft AzureBYOS&L - WebSphere App ServerPay-as-you-Go WAS VMs

56

Model Software Charge

Developer options

No Charge

Bring Your Own Software & License

PREPAID: perpetual,yearly, monthly

Bring Your Own License

PREPAID: perpetual,yearly, monthly

Pays-As-You-Go

By Usage: hourly,monthly

Customer Licensing Models

Many Developer use optionsavailable at no charge. Manyincluding support.

Customers uses the pre-builtimages and are billed for theusage.

Customer owns softwarelicense. Use their own softwareto build their own image

Customer owns an IBMSoftware License and can usethe pre-build IBM image

WebSphere Application Server Deployment Map

On-Premises IaaS PaaS *

SoftLayer EC2 Azure IBM Bluemix

PVU-based X

Subcapacity X

FTL (1 year) X

BYOS&L X X X

PAYG X X

FreeDevelopers

X X X X X*

Patterns X X

LicenseMobility

X X X X

Notes:• Free for Developers desktops physical or virtual. WDT tooling as well.• License mobility across all PVU-based options.• Subcapacity: only pay for the core capacity within virtual partitions being utilized by the software, not the capacity of

the entire server.• Other PaaS: Pivotal, OpenShift, & Heroku is Free for Developers

57

You Have Options to Get to Here!

58

Internet


sources



Public Cloud

API



APP

APP

Service

Service DBAPPDB

APP

APP

Enterprise

DB

Private Cloud


Big Data

API

DMZ DMZ

59

Related Sessions

• AAI 1435: What is WAS?

• AAI 3590: Managing WebSphere Large Topologies

• AAI 2827: 10,000 Servers and Climbing- Achieving Liberty at Scale

• AAI 2343: Deploying IBM WebSphere Application Server to the cloud

Notices and DisclaimersCopyright © 2015 by International Business Machines Corporation (IBM). No part of this document may be reproduced ortransmitted in any form without written permission from IBM.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM.

Information in these presentations (including information relating to products that have not yet been announced by IBM) has beenreviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBMshall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY,EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OFTHIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFITOR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of theagreements under which they are provided.

Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal withoutnotice.

Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples arepresented as illustrations of how those customers have used IBM products and the results they may have achieved. Actualperformance, cost, savings or other results in other operating environments may vary.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products,programs or services available in all countries in which IBM operates or does business.

Workshops, sessions and associated materials may have been prepared by independent session speakers, and do notnecessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neitherintended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.

It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legalcounsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’sbusiness and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice orrepresent or warrant that its services or products will ensure that the customer is in compliance with any law.

60

Notices and Disclaimers (con’t)

Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products in connection with thispublication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.IBM does not warrant the quality of any third-party products, or the ability of any such third-party products tointeroperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED,INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE.

The provision of the information contained herein is not intended to, and does not, grant any right or license under anyIBM patents, copyrights, trademarks or other intellectual property right.

• IBM, the IBM logo, ibm.com, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise DocumentManagement System™, Global Business Services ®, Global Technology Services ®, Information on Demand,ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™,PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®,pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ, Tivoli®, Trusteer®,urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks ofInternational Business Machines Corporation, registered in many jurisdictions worldwide. Other product andservice names might be trademarks of IBM or other companies. A current list of IBM trademarks is available onthe Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

61

Thank YouYour Feedback is

Important!

Access the InterConnect 2015Conference CONNECT AttendeePortal to complete your sessionsurveys from your smartphone,

laptop or conference kiosk.