Upload
ibm-cics
View
1.279
Download
6
Tags:
Embed Size (px)
DESCRIPTION
In this presentation, Software Architect Richard Gamblin outlines the uses and benefits of Java on System z as well as possible topologies. .
Citation preview
© 2014 IBM Corporation
July 2014
Java Topologies on System z
Richard Gamblin WebSphere Software Architect [email protected] | @RichGx
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Important Disclaimer THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.
WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.
IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE.
IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.
NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF:
• CREATING ANY WARRANTY OR REPRESENTATION FROM IBM (OR ITS AFFILIATES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS); OR
• ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF IBM SOFTWARE.
2
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Contents
• Java workloads: factors & selection criteria
• Use-cases and scenarios
• Java platform options & topologies
• Tooling, process & application lifecycle
• Making informed platform decisions
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Java workloads: factors & selection criteria
• Requirement • Recognition that Java can be delivered across all platforms,
depending on the project/ implementation use-case
• Objectives: platform choice for Java – When & Why?
• Java hosting options 1. Native Java on z/OS 2. WebSphere Application Server for z/OS (Traditional and Liberty Profile) 3. WebSphere Application Sever ND on Linux on z (Traditional and Liberty Profile) 4. Java hosting within CICS Transaction Server
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Java workloads: factors & selection criteria
Cost
Performance
Resilience
Development
Operations
Process
Industry Adoption
Java Technology
Decision
Tooling & Skills
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Java workloads: factors & selection criteria Prioritising different factors will (and should) give selection criteria
Cost
Performance
Resilience
Development
Operations
Process
Industry Adoption
Technology
Decision
Tooling & Skills
Q. What is the priority of the factors?
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Contents
• Java workloads: factors & selection criteria
• Use-cases and scenarios
• Java platform options & topologies
• Tooling, process & application lifecycle
• Making informed platform decisions
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Java Platform Options: Scale up vs. Scale out
8
© 2014 IBM Corporation
Java Topologies on System z | July 2014
9
Java Topologies on System z
zVM
IFL
Linux for System z
System z Hardware Logically Partitioned
zOS
z/OS Guest
WebSphere Application Server
for Linux
WebSphere Application Server for z/OS
Guest IFL zOS
Coupling Facility
LPAR or CEC
Parallel Sysplex
System z Hardware Logically Partitioned
Guest 2
IBM Java SDK for z/OS
CICS Transaction Server for z/OS
zOS zOS
Liberty
USS
1 2 3 4
zIIP zIIP zIIP zIIP
Liberty Liberty
© 2014 IBM Corporation
Java Topologies on System z | July 2014
10
Java Topologies on System z: Native Java
zVM
IFL
Linux for System z
System z Hardware Logically Partitioned
zOS
z/OS Guest
WebSphere Application Server
for Linux
WebSphere Application Server for z/OS
Guest IFL zOS
Coupling Facility
LPAR or CEC
Parallel Sysplex
System z Hardware Logically Partitioned
Guest 2
IBM Java SDK for z/OS
CICS Transaction Server for z/OS
zOS zOS
Liberty
USS
1 2 3 4
zIIP zIIP zIIP zIIP
Liberty Liberty
© 2014 IBM Corporation
Java Topologies on System z | July 2014
11
l IBM Java SDK for z/OS can run within the Unix System Services environment
l Also packaged with the WAS z/OS binaries, and maintenance of Java is part of WAS z/OS maintenance
l Java 7 is the latest deliverable and includes specific exploitation of instructions in new IBM System z EC12 machine
IBM Java SDK for z/OS
Specialty Engines
IBM Java SDK for z/OS and USS
© 2014 IBM Corporation
Java Topologies on System z | July 2014
12
Java for Batch Processing? Yes ... for many very good reasons:
z/OS Specialty Engines Pressures on cost containment often dictate greater use of z/OS specialty engines. Java offloads to zAAP. Java batch does as well.
Tooling Support Development tooling for Java has advanced to the point where some tools (IBM Rational Application Developer) are very powerful and sophisticated. This also provides an opportunity to consolidate to a common tooling environment for both OLTP and batch development.
Processing in OLTP Runtime Running Java batch in the same execution runtime as Java OLTP provides an opportunity to mix and manage the two processing types together under the same management model.
Availability of Skills Java is a programming language with wide adoption in the industry. Skills for Java programming are common and affordable.
© 2014 IBM Corporation
Java Topologies on System z | July 2014
13
Java Topologies on System z: WAS on z/OS
zVM
IFL
Linux for System z
System z Hardware Logically Partitioned
zOS
z/OS Guest
WebSphere Application Server
for Linux
WebSphere Application Server for z/OS
Guest IFL zOS
Coupling Facility
LPAR or CEC
Parallel Sysplex
System z Hardware Logically Partitioned
Guest 2
IBM Java SDK for z/OS
CICS Transaction Server for z/OS
zOS zOS
Liberty
USS
1 2 3 4
zIIP zIIP zIIP zIIP
Liberty Liberty
© 2014 IBM Corporation
Java Topologies on System z | July 2014
WebSphere Application Server
• WebSphere Application Server (WAS) is an runtime execution environment for applications that provides numerous standard functions… • Communication interface • Security interface • Transactional interface • Standard services for logging, alerts, administration, etc.
• With WAS, you’re getting a runtime environment • But exclusively in Java, and standardised (JEE)
14
© 2014 IBM Corporation
Java Topologies on System z | July 2014
15
Convergence of WAS z/OS and WAS ND WAS z/OS Distributed WAS ND
2004
2005
2006 2007
5.1 5.1 5.1.1
6.0 6.0.1 6.0.2 6.1
2008 7.0
2009 8.0
2011 8.5
2012
© 2014 IBM Corporation
Java Topologies on System z | July 2014
16
The standards supported by WAS are common and consistent across all the operating systems and hardware platforms:
Open Standard Application Interface Specifications
API API API API API API API API
"WAS is WAS" at this level
That's of value because ... l Applications are platform neutral Which means application design and coding does not
require platform specific considerations
l Allows you to consolidate on a common set of tooling
Which provides savings in licensing as well as skill development and skill utilization
l Applications are portable across platforms Which provides flexibility for code promotion from test and
quality assurance on one platform up to production on another
"WAS is WAS" Above the Standard Spec Line
© 2014 IBM Corporation
Java Topologies on System z | July 2014
17
The code under the open specification APIs is not 100% common across all platforms. It is mostly common, but each platform has a portion of code specific to that OS:
Open Standard Application Interface Specifications API API API API API API API API
Implementation Code Common to All Platforms
~90%+ ... all the Java code is common
Platform Specific
l Every platform OS has at least some code unique to that platform
l The z/OS operating system has a long list of features and functions to take advantage of
l WAS z/OS is designed to know about and take advantage of many of those functions
Implementation is not 100% Common
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Platform Native Code
IBM Java Code
Your Application
Your Application
Servant Region
Request
Request
Request
zWLM Work Request Queue
Platform Native Code
Java Code
Controller Region
Listener Ports
Platform Native Code
IBM Java Code
Your Application
Your Application
Servant Region
Request
Request
Request
zWLM Work Request Queue
Servant region hosts applications zWLM work queue acts as intermediary point for requests Servants "pull" work
Controller hosts all the IBM "plumbing" code as well as the listener ports
Additional servants may be started ... by your or by zWLM Provides vertical scaling ... ... also classification and work placement
WAS z/OS and the "Multi-JVM" Design
18
© 2014 IBM Corporation
Java Topologies on System z | July 2014
19
Leveraging co-location with enterprise applications and System z qualities of service
§ WAS inherits the System z Qualities of Service such as reliability, availability, scalability, security
§ WebSphere Optimized Local Adapters continue to gain momentum for high performing local access to CICS, IMS and batch
WAS Co-Location with z/OS Applications and Data
© 2014 IBM Corporation
Java Topologies on System z | July 2014
20
WAS z/OS is capable of taking advantage of native interfaces to key data systems to exchange communications over a cross-memory boundary:
DB2 JDBC Type 2 Driver
CICS CTG EXCI
MQ Bindings MQ
See WOLA Chart
WOLA
WAS z/OS
Applications l Very low latency The problem of latency tends to be additive in high volume, repetitive
transactions
l Very secure Data can not be sniffed, intercepted or modified
l Avoid encryption / decryption overhead Since exchange is so secure, the need to encrypt may be eliminated
l Security identity assertion across interface Avoid coding identity "aliases" in different locations across enterprise
l Avoid TCP/IP stack processing overhead Reduces overall system CPU usage
l Single thread of execution across interface Avoid task switching overhead
l Reduced complexity for debug and troubleshooting
When sender and receiver are in same OS environment one set of tools may be used.
Benefits :
Cross-Memory
© 2014 IBM Corporation
Java Topologies on System z | July 2014
21
WebSphere Optimized Local Adapters provides an efficient low-latency mechanism to exchange data bi-directionally between WAS z/OS and other address spaces:
WAS z/OS
Applications
CICS WOLA
IMS WOLA
Batch WOLA
USS WOLA
ALCS WOLA
l Very efficient byte-array transfer l First available with WAS z/OS 7.0.0.4
l Bi-directional n Outbound -- Java in WAS invokes program in external n Inbound -- Program in external invokes Java in WAS
l Two phase commit, identity assertion l Supplied JCA resource adapter for applications
going outbound l Supplied native APIs for cases where their
usage is indicated n COBOL, C/C++, PL/I, High Level Assembler n 31-bit and 64-bit modules
Cro
ss-m
emor
y ...
no
TCP
/IP s
tack
ove
rhea
d WebSphere Optimized Local Adapters (WOLA)
© 2014 IBM Corporation
Java Topologies on System z | July 2014
22
System z speciality engines (zAAP, zIIP, zAAP-on-zIIP) provide a means of running certain work on processor engines which are: (a) priced lower than general processors, and (b) Not counted in processor-based software licensing. The offload of work to specialty engines is transparent to applications. WebSphere Application Server for z/OS execution involves Java, and Java work is offloaded to a zAAP. • Lower acquisition Cost -- specialty engines are priced well below general processor (GP), allowing for capacity with a lower acquisition cost. • Less GP usage -- WAS z/OS Java execution offloaded to a specialty engine is not counted towards GP usage license charges. • More GP for other work -- offload to a specialty engine means general processors are more available for work that requires them, which might allow avoidance or delay of acquiring additional GP.
WAS and Speciality Engines
© 2014 IBM Corporation
Java Topologies on System z | July 2014
23
SAF -- and the security product behind it -- provides a security management tool for WAS z/OS ... infrastructure security, application security, user identity security:
SAF Interface
z/OS Security Product IBM = RACF
System Resources
WAS z/OS l SAF may be used to store user ID and
password information for authentication l Digital certificates may be stored in SAF,
eliminating separate keystore files l Application EJB roles may be enforced by
SAF l SAF controls what address space ID is
assigned to WAS z/OS started tasks l SAF may be used to reserve TCP ports for
WAS by WAS server name l SAF provides a single point of security
administration with a strong tradition of careful, controlled security management
Security – SAF
© 2014 IBM Corporation
Java Topologies on System z | July 2014
~5x aggregate hardware and software improvement comparing WAS 6.1 Java5 on z9 to WAS 8.5 Java7 on zEC12
History of WAS Performance on System z: Hardware/ Software
Performance
© 2014 IBM Corporation
Java Topologies on System z | July 2014
25
Java Topologies on System z: WAS Liberty on z/OS
zVM
IFL
Linux for System z
System z Hardware Logically Partitioned
zOS
z/OS Guest
WebSphere Application Server
for Linux
WebSphere Application Server for z/OS
Guest IFL zOS
Coupling Facility
LPAR or CEC
Parallel Sysplex
System z Hardware Logically Partitioned
Guest 2
IBM Java SDK for z/OS
CICS Transaction Server for z/OS
zOS zOS
Liberty
USS
1 2 3 4
zIIP zIIP zIIP zIIP
Liberty Liberty
© 2014 IBM Corporation
Java Topologies on System z | July 2014
What is the Liberty profile?
26
A lightweight, dynamic, composable runtime • Lightweight
• Server install is only about 55 MB • Extremely fast server starts – typically well under 5 seconds
• Dynamic • Available features are user selected and can change at runtime • Restarts are not required for server configuration changes
• Composable • Features are implemented as loosely coupled components with
lazily resolved optional and mandatory dependencies • The availability of features and components determines what
Liberty can do and what’s available to applications
© 2014 IBM Corporation
Java Topologies on System z | July 2014
What is the WAS for z/OS Liberty profile?
27
• The WAS for z/OS Liberty profile is Liberty with optional, independently enabled extensions that exploit z/OS facilities • Only enable exploitation of z/OS features you need • Only configure the z/OS functions you use
• Focus of v8.5 is basic integration and exploitation
jndi-1.0 jdbc-4.0
sessionDatabase-1.0
monitor-1.0 transaction-1.1
ssl-1.0
localConnector-1.0 restConnector-1.0
appSecurity-1.0
zosSecurity-1.0 zosWlm-1.0
zosTransaction-1.0
Common Feature Sets
z/OS Feature Sets
© 2014 IBM Corporation
Java Topologies on System z | July 2014
28
WAS for z/OS 8.5.5 Liberty feature set
Application Manager HTTP Transport Feature Manager
New in Liberty 8.5.5
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Liberty and traditional profile capabilities
29
There are functional differences between traditional WAS and the Liberty profile – Liberty provides a useful subset of traditional WAS
Liberty Profile Traditional WAS Profile Bean validation Blueprint Java API for RESTful Web Services Java Database Connectivity (JDBC) Java Naming and Directory Interface (JNDI) Java Persistence API (JPA) Java Server Faces (JSF) Java Server Pages (JSP) JMX Monitoring OSGi JPA Remote connector Secure Sockets Layer (SSL) Security Servlet Session Persistence Transaction Web application bundle (WAB) z/OS Security (SAF) z/OS Transactions (RRS) z/OS Workload Management
Enterprise Java Beans (EJBs) Messaging (JMS) Web Services Service Component Arch (SCA) Java Connector Architecture (JCA) Clustering WebSphere Optimized Local Adapters Administrative Console WSADMIN scripting Multi-JVM Server Model And much more …
Everything Liberty has…
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Why Liberty on z/OS?
30
Performance: Startup time – 3.2 seconds
0.00
5.00
10.00
15.00
20.00
25.00
Tradi,onal Liberty
Second
s – Low
er is be/
er
Server Startup – Elapsed
0.00
5.00
10.00
15.00
20.00
25.00
Tradi,onal Liberty
Second
s – Low
er is be/
er
Server Startup – CPU
• Liberty – 64bit IBM Java 6.0.1, 64/64MB min/max heap, 60MB shared class cache, TradeLite installed • Traditional – 64bit IBM Java 6.0.1, 1SR,128/256MB min/max CR heap, 256/512MB min/max SR heap, 75MB
CR shared class cache, 75MB SR shared class cache, no applications installed
5.1x 6.8x
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Why Liberty on z/OS?
31
Performance: Memory footprint – 80% reduction
0
50
100
150
200
250
300
350
400
450
Tradi,onal Liberty
MB – Lower is be/
er
Server Footprint
5.2x
• Liberty – 64bit IBM Java 6.0.1, 64/64MB min/max heap, 60MB shared class cache, TradeLite installed • Traditional – 64bit IBM Java 6.0.1, 1SR,128/256MB min/max CR heap, 256/512MB min/max SR heap, 75MB
CR shared class cache, 75MB SR shared class cache, no applications installed
© 2014 IBM Corporation
Java Topologies on System z | July 2014
32
Java Topologies on System z: WAS on Linux on z
zVM
IFL
Linux for System z
System z Hardware Logically Partitioned
zOS
z/OS Guest
WebSphere Application Server
for Linux
WebSphere Application Server for z/OS
Guest IFL zOS
Coupling Facility
LPAR or CEC
Parallel Sysplex
System z Hardware Logically Partitioned
Guest 2
IBM Java SDK for z/OS
CICS Transaction Server for z/OS
zOS zOS
Liberty
USS
1 2 3 4
zIIP zIIP zIIP zIIP
Liberty Liberty
© 2014 IBM Corporation
Java Topologies on System z | July 2014
33
The benefits relate to how multiple Linux instances can be efficiently hosted on System z:
l Ability to consolidate many Linux and WAS instances to a single server footprint
Savings: floor space, electrical, cooling, potential for software license savings
l Disaster recovery (DR) capabilities since all artifacts grouped by System z
l Ability to share WAS product binaries across multiple Linux instances hosted by z/VM
WAS maintenance updates quickly apply to all
l Ability to create new instances of Linux and WAS very quickly
Using z/VM and System z Cloud functions
l Ability to access z/OS data across Hipersockets
TCP/IP network mapped to real memory backplane of System z CEC
PR/SM Logical Partition Virtualization
z/VM Virtualization OS
IFL Integrated Facility for Linux
WAS Linux
WAS Linux
WAS Linux
WAS Linux
WAS Linux
WAS Linux
DB2
CICS
MQ
IMS
z/OS
Note: WAS running on Linux for System z does not have access to z/OS functions such as WLM,
RRS, SMF. Linux images running on System z can not participate in Parallel Sysplex.
Those are all functions of z/OS on System z
WAS on Linux for System z
© 2014 IBM Corporation
Java Topologies on System z | July 2014
What is WebSphere Application Server for Linux on z?
• Since Linux is the same (few tweaks), from a Linux app perspective… • WAS is the same product/ configuration as on any other Linux
34
Linux Applications
System z Instruction Set and I/O Hardware
Linux Kernel
HW Dependent Drivers
Linux Apps
Generic Drivers
Network Protocols Filesystems
Platform Dependent Code
Backend GNU Runtime Environment
Process Management
Memory Management
Architecture Independent Code
Backend
GN
U C
omplier S
uite
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Same WebSphere Application Server on Linux on z
• Same access to new capabilities in the latest versions: e.g. Version 8.5 • Liberty Profile [simplified, light-weight, single XML-configurable profile]
• Expanded tools & tool bundles with IBM Rational
• OSGi programming models
• Support for Java 7
• Web 2.0 & Mobile toolkit, supporting Ajax & REST
• Inherits the benefits of the underlying System • Scale up to very large system
• Non-disruptive updates
• Many multiple Linux guests on a single footprint
• Cost benefit in licensing
• Availability benefit…
35
© 2014 IBM Corporation
Java Topologies on System z | July 2014
WAS: Continuous Availability
36
WebSphere Active/Active Cluster with Database Sharing on z/OS Between Cities
z/OS LPAR on System A z/VM LPAR 1 on System A
Fire
wal
l
z/VM LPAR 2 on System B
Router
Fire
wal
l
Fire
wal
l
WebSphere Cluster
Primary Edge
Server
Backup Edge
Server
HTTP Server
HTTP Server WAS
Server Fi
rew
all
DVIPA --------- DB2
SD Backup
WAS Dmgr
z/OS LPAR on System B
Router
SD
Metro Mirror Max 300KM
DS8000 Remote Mirror
DVIPA --------- DB2
WAS Server
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Benchmark comparison for WAS/DB2 banking app consolidation
• WAS DB2 sample Banking application • Fairly old kit now, however there are a few
things to note: • On reaching the limits of the machine scalability… • …consider the performance… • …z/VM tails off in a predictable manner • …vs. sudden drop in performance
37
Positions Linux on System z vs. Intel Nehalem and Hyper-V
© 2014 IBM Corporation
Java Topologies on System z | July 2014
38
Java Topologies on System z: WAS Liberty within CICS
zVM
IFL
Linux for System z
System z Hardware Logically Partitioned
zOS
z/OS Guest
WebSphere Application Server
for Linux
WebSphere Application Server for z/OS
Guest IFL zOS
Coupling Facility
LPAR or CEC
Parallel Sysplex
System z Hardware Logically Partitioned
Guest 2
IBM Java SDK for z/OS
CICS Transaction Server for z/OS
zOS zOS
Liberty
USS
1 2 3 4
zIIP zIIP zIIP zIIP
Liberty Liberty
© 2014 IBM Corporation
Java Topologies on System z | July 2014
39
CICS Transaction Server: Liberty Profile Web Container
New Java web container is built on WebSphere Application Server Liberty profile technology:
• Provides a fast and lightweight Java web container • Provides “off the shelf” Web-server capabilities (JSPs
and Servlets) • JSP and Web servlets have direct, local, access to CICS
data and resources • Servlets can take advantage of existing CICS OSGi
applications to provide a Dynamic Web front end
© 2014 IBM Corporation
Java Topologies on System z | July 2014
40
Web App
CICS
Liberty JVM server
CICS Resources
Web Client
HttpRequest
HttpResponse
• Optimal scenarios for Web app. deployment to CICS • Access to existing CICS programs • Access to CICS/VSAM data • Sharing access to DB2 tables controlled by CICS • Reducing network I/O by removing remote connector
CICS Transaction Server: Liberty Profile Web Container
© 2014 IBM Corporation
Java Topologies on System z | July 2014
41
Oct
201
2
CICS Liberty Roadmap - 2014
WAS 8.5.0 Liberty profile
WAS 8.5.5 ü Liberty core ü Liberty base ü EJB, JMS, clustering,
jaxws
2013 2012
CICS TS V5.1 ü Liberty 8.5.0 ü Servlet/jsp ü Explorer SDK for Web
2014
CICS TS V5.2 ü Liberty 8.5.5.1 ü JTA ü JDBC ü zosSecurity, appSecurity ü jndi, blueprint, jaxws
2Q12
WAS 8.5.0.1
WAS 8.5.0.2
WAS Liberty Repository features
ü JCA 1.6 ü Web sockets ü EJB 3.2 …..
Apr
il 20
13
2Q13
4Q20
12
2Q20
13
Oct
201
3
V5.1APAR PM91667 Liberty 8.5.5
V5.1 APAR PM85279
JAX-RS, JSON
V5.1 APAR PM80214
Liberty 8.5.0.1 EBA support
WAS 8.5.5.1
WAS 8.5.5.2
June
201
4
© 2014 IBM Corporation
Java Topologies on System z | July 2014
42
WAS 8.5.5 Liberty feature set
Application Manager HTTP Transport Feature Manager
New in Liberty 8.5.5
© 2014 IBM Corporation
Java Topologies on System z | July 2014
43
Feature Manager
CICS/Liberty feature set - CICS TS V5.2
Application Manager HTTP Transport
CICS TS V5.1
cicsts:security-1.0 cicsts:jdbc-1.0
CICS TS V5.2
cicsts:security-1.0
jaxb beanvalidation
appSecurity jdbc
zosSecurity
jaxws
blueprint
jaxws
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Contents
• Java workloads: factors & selection criteria
• Use-cases and scenarios
• Java platform options & topologies
• Tooling, process & application lifecycle
• Making informed platform decisions
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Systems of Engagement (SoE) Apps
Rapid Releases AppStore
Monitor and Optimize
Release and Deploy
Develop and Test
Inte
grat
ion
Test
45
Monitor and Optimize
Develop and Test
Web Apps Frequent Releases
Production Environment
Databases
Systems of Record (SoR) Apps Fewer
Releases Databases
Integrate Systems of Engagement & Systems of Record By bringing together the culture, processes, and tools across the entire software delivery lifecycle – spanning mobile to mainframe platforms
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Leverage common tools to build multiplatform apps
• Leverage common Eclipse-based IDEs for all types of development
• Access broad coverage of runtimes, languages, compilers, and platforms
• Access via cloud-based environments like SmartCloud Enterprise+ (SCE+)
• Create agile services from existing mainframe assets
Open Lifecycle and Service Management Integration Platform
Continuous Delivery
Boost developer productivity Rational Developer for the Enterprise IBM Worklight for MobileFirst platform
Enabling you to…
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Line of Business
Ra,onal Focal Point Ra,onal Doors Next Genera,on
SmartCloud Applica,on Performance Management Tealeaf
UrbanCode Deploy
UrbanCode Release
Ra,onal Quality Manager Ra,onal Test Workbench Ra,onal Development and Test Environments for System z Ra,onal Test Virtualiza,on Server InfoSphere Op,m Test Data Mgmt
Building a continuous delivery pipeline Built on an open standards based platform and a set of services enabling software teams to leverage open source and third party tools
47
Jenkins
Ra,onal Build Forge
Ra,onal Team Concert Ra,onal Developer for System z Ra,onal Developer for IBM i Ra,onal Applica,on Developer Compilers
SmartCloud Orchestrator Pure Applica,on System Enterprise Systems
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Promote
Deploy
Test Environment – RD&T
• Download build output from artifact repository on z/OS
• Deploy to z/OS or RD&T to test application changes
Application under test
IBM UrbanCode Deploy for z/OS
Continuous Delivery for the Mainframe New capabilities to speed delivery of dependent, multi-platform applications
• Unified solution for continuous delivery of heterogeneous enterprise applications • Accelerate delivery and reduces cycle time to develop/test multi-tier applications across
heterogeneous environments and platforms • Reduce costs and eliminate delays for delivering mainframe applications • Minimize risk improve productivity across disparate teams w/ cross-platform release plans
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Contents
• Java workloads: factors & selection criteria
• Use-cases and scenarios
• Java platform options & topologies
• Tooling, process & application lifecycle
• Making informed platform decisions
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Platform Selection for Java Workloads Factors, Weighting Criteria & Platform
50
Criteria Weight WAS ND Linux /x86
Liberty Linux /x86
WAS ND Linux /z
Liberty Linux /z
WAS z/OS
Liberty z/OS
Performance
Cost
Resilience
Technology
Operations
Development
Process
Industry Adoption
TOTAL
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Platform Selection for Java Hosting Decision Tree: Example 1
51
New Application
IT Strategy Java Hosting Technology
IT Strategy Platform Options
Project Requirements Decision
WAS ND
WAS Base
WAS Liberty
Linux on x
Windows
Linux on z
z/OS CICS Liberty
Discarded
Discarded
Discarded
Decision Linux on z
© 2014 IBM Corporation
Java Topologies on System z | July 2014
Platform Selection for Java Hosting Decision Tree: Example 2
52
New Application
IT Strategy Java Hosting Technology
IT Strategy Platform Options
Project Requirements Decision
WAS ND
WAS Base
WAS Liberty
Linux on x
Windows
Linux on z
z/OS CICS Liberty
Discarded Discarded
Discarded
Decision WAS z/OS
© 2014 IBM Corporation
Java Topologies on System z | July 2014
53
Thank You
Merci
Bedankt
Gracias!
Obrigado
Danke
Japanese
English
French
Russian
German
Nederlands
Spanish
Brazilian Portuguese Arabic
Traditional Chinese
Simplified Chinese
Thai
© 2014 IBM Corporation
Java Topologies on System z | July 2014
54
Trademarks, Copyrights, and Disclaimers The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM CICS IMS MQSeries Tivoli IBM(logo) Cloudscape Informix OS/390 WebSphere e(logo)business DB2 iSeries OS/400 xSeries AIX DB2 Universal Database Lotus pSeries zSeries Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Other company, product and service names may be trademarks or service marks of others. Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This document could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or program(s) described herein at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. 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. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectual property rights, may be used instead. Information is provided "AS IS" without warranty of any kind. THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted, if at all, according to the terms and conditions of the agreements (e.g., IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. IBM makes no representations or warranties, express or implied, regarding non-IBM products and services. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users - Documentation related to restricted rights-Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract and IBM Corp.