Websphere zos Mettle Test 2003 Can Your Enterprise Server Do This? ebu 2004, Las Vegas Carl Parris - IBM WebSphere Introduction and Overview zseries
Trademarks The following are trademarks of the IBM Corporation in the United States or other countries or both: IBM MVS OS/390 RACF Language Environment Resource Measurement Facility RMF S/390 System/390 Sysplex VisualAge VTAM WebSphere zseries Lotus, Notes, and Domino are trademarks or registered trademarks of Lotus Development Corporation Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation Permission is granted to SHARE to publish this presentation in the SHARE proceedings. IBM retains its rights to distribute copiesof this presentation to whomever it chooses. IBM Corporation 2003
Agenda Why the Mettle Test? Websphere zos Runtime structure Configuration overview WebSphere, WLM and transaction priorities WebSphere and IRD View the gauges from the Mettle Test system Why run Websphere on zos/zseries?
Why the Mettle Test? Industry Standard Benchmarks do not adequately reflect operational performance requirements Static loads Unconstrained resources Single application per operating system, single operating system per box Benchmarks are not a good indicator of deployment configurations Benchmark at 100% - in production run at much less Under utilized hot-standbys for failover, development, test systems, etc. Operational footprint much larger than benchmarks would indicate needed Price/performance calculations based on a single instance benchmark at 100% cpu utilization can be misleading New application environments are leading to increasing volatility in loads on backend IT infrastructures Websphere Portal - view of entire enterprise Websphere Business Integrator J2EE connectors to ERPs, Collaboration, Decision Support, Legacy systems Workflow - orchestrated sequences of transactions to multiple back-end applications Webservices - enterprise to enterprise, application to application interaction Is your IT infrastructure ready to handle this??
What is the Mettle Test? The Mettle Test is an operational performance demonstration highlighting the reliability and availability characteristics of zseries and WebSphere Self-Optimizing Scenarios Dynamic Resource Management Distinquish between high priority and low priority websphere users Distinguish between high priority and low priority applications On demand response to changing processing capacity requirements with IRD Self-Healing Scenarios Planned and Unplanned Outage Avoidance Websphere/zOS application failure isolation Continuous availability of sysplex Hardware failure isolation and recovery Non-disruptive installation of application and middleware maintenance
State of the Art Transactional Runtime Merges the best of 30 years of mission critical transaction monitors and the J2EE programming model Isolation Availability Consistency Resource management Two phase commit High Priority Users or Trxs Server Regions Application Medium Priority Users or Trxs RRS IMS catalog HTTP Control Region Server Regions RRS IIOP WLM Application Socket endpoint Authorized Recoverable Low Priority Users or Trxs Server Regions RRS Application
Mettle Test System Configuration Designed for availability EdgeServer and backup EdgeServer Windows 2000 Server EdgeServer Network Dispatcher V4.0 Two HTTP Servers on zlinux zlinux z/vm guests running SuSE SLES 7, Kernel 2.4.7 IBM HTTP Server 1.3.19.3 WebSphere on multiple systems in parallel sysplex 1.3, WebSphere 4.0.1, Java 1.3.1 V7, TS 2.2, CTG V4
Mettle Test Configuration Users Win2000 Backup Edge Server Edge Server: Network Dispatcher MAC forwarding to HTTP Servers 2064-216 VM z/linux HTTP Server z/linux HTTP Server HTTP Server: WebSphere Plug-in plug in plug in Sysplex Distributor - VIPA 2064-216 1.3 SYSA WAS ERWW SYSB WAS ERWW SYSC WAS ERWW SYSD WAS Trade2 SYSE TestWAS Trade2 Test Batch Testing Group
HTTP Server System 2064-216 SYSA SYSB CF01 z/vm CMS Users z/linux Guests z/vm zlinux SYS1 CF03 SYSC SYSD CF02 HTTP Server HTTP Server Other HTTP project Server Other project Other project Other project z/vm SYS2 CF04 The HTTP Servers are z/linux guests under VM The VM system is one of fifteen partitions on the z/900 processor Partitions are running, z/vm systems or coupling facilities
Sysplex Configuration Sysplex Distributor - VIPA 2064-216 1.3 SYSA WAS ERWW SYSB WAS ERWW SYSC WAS ERWW SYSD WAS Trade2 DSNA Data Sharing DSNB Data Sharing DSNC Data Sharing DSND Data Sharing SYSE DSN7 Batch Test TestWAS Trade2 CF 2064-100 data sharing ERWW data base Trade2 data base test system Trade2 test data base
Workloads Order Entry SYSA, SYSB, SYSC Service class BBERWW Importance 1 Order Analysis SYSA, SYSB, SYSC Service class BBITLOW Importance 4 Trade2 production SYSD Service class BBTRD2 Importance 2 Trade2 test Runs on SYSE Service class TZTRD2 Importance 3 Batch work Runs on SYSE Service class BATLOW Importance 4
Three levels of resource management 1. WLM within the Websphere run-time OE and OA in different service classes Priority 1 and Priority 4 2. WLM within a single instance of zos Batch and Trade2 in different service classes Priority 3 and Priority 4 3. IRD across LPARs Weighted distribution of cpu and I/O resources WAS OE Priority 1 WAS OA Priority 4 1 WAS OE Priority 1 1 1 WAS OA Priority 4 3 WLM and IRD WAS OA Priority 4 WAS OE Priority 1 WAS TP Priority 2 WAS TP Priority 2 WAS TT Priority 3 BATCH Priority 4 SYSA SYSB SYSC SYSD SYSE 2 Logical cpus SYSA SYSB SYSC SYSD SYSE Physical cpus
WLM and IRD Resource Management Scenario Flow Night shift Batch and Test activity on the Test Partition SYSE Production work coming in from other time zones SYSD Early morning Employees arrive at work Put load on mission critical application - Order Entry High priority SYSA, SYSB, SYSC Mid morning Business Intell. dept. starts querying customer buying behavior - Order Analysis Low priority SYSA, SYSB, SYSC Mid afternoon Order Entry activity increases to fully utilize system Late Afternoon Employees go home - Order Entry stops Order Analysis and other application activity increases