WebSphere XD Virtual Enterprise v7.0: virtualization and infrastructure optimization

Transcription

1 Antonella Bertoletti Executive IT Specialist WebSphere Client Technical Professional Team IBM Software Group WebSphere XD Virtual Enterprise v7.0: virtualization and infrastructure optimization

2 WAS family overview Extended Deployment (XD) Network Deployment On demand operating environment Virtual Enterprise Compute Grid extreme Scale Application Server Express Full J2EE Web based admin Messaging Web/EJB containers JDK PMEs Like Express without license limitation Clustering Failover Workload Management Distributed Administration Web Services Web Services Gateway 2011 IBM Corporation 2

3 Scalability and availability Firewall Application Server HTTP Plug-in Edge Comp Application Server HTTP Plug-in Application Server HTTP Plug-in Edge Comp HTTP Plug-in HTTP Plug-in HTTP Plug-in Application server Application server Connectors z/os IMS CICS DB2/ Oracle Stand-alone Scenario Network Deployment Scenario I Network Deployment Scenario II 2011 IBM Corporation 3

4 Why Virtualization is important Smart is: Leadership virtualization and consolidation solutions that reduce cost, improve asset utilization, and speed provisioning of new services. Reduce operating costs Improve service responsiveness Consolidate via virtualization to fewer systems. Simplify management of the infrastructure. Recapture floor space through consolidation. Improve system, network and application performance. Process more information in real-time to make better business decisions. Bring new services online quickly. Manage availability in a 24/7 world Dynamically adapt to the peaks of the business Increase availability and improve resiliency. Increase availability and improve resiliency. Manage and secure data without affecting its availability. Manage and secure data without affecting its availability. Dynamically deliver resources where needed most. Make data available from anywhere, anytime IBM Corporation 4

5 The alignment of Business and IT with SOA Creating an Enduring Impact Infrastructure Services WebSphere XD Improve flexibility 2011 IBM Corporation 5

6 Delivering application quality of service Can result in poor business performance Denial of Service during periods of peak demand Managing complex, heterogeneous environments is costly and personnel intensive Data volume challenges lead to poor application performance and scalability Processors average just 5% - 20% utilization, driving up costs The skills needed to develop highly reliable, highly scalable OLTP applications are scarce and expensive 2011 IBM Corporation 6

7 Addressed market/customer needs Best possible usage of the owned infrastructure Consolidate multiple under-utilized servers into a shared environment Ability to share resources across server pools, especially during peaks Traffic management Consistent quality of service for business critical applications Differentiate and classify the applications based on SLA and importance Make the applications more stable and more scalable Application versioning Unified administration and management across different Application Servers Open Source Application Servers Non WebSphere Application Servers Improve Environment Manageability Enable the Middleware Operations team to run the environment easier Reduce the human-intensive monitoring 2011 IBM Corporation 7

8 What is WebSphere XD? Software to virtualize, control, and turbo-charge your application infrastructure Infrastructure Optimization Intelligent Workload Management Virtualization Automatic Sense & Respond Management Data Fabrics & Caching Innovative Application Patterns (beyond OLTP) 2011 IBM Corporation 8

9 WebSphere XD Packaging Structure Available as a single, integrated package, or as 3 individual components Virtual Enterprise extreme Scaling Compute Grid 2011 IBM Corporation 9

10 WebSphere Extended Deployment - Virtual Enterprise v IBM Corporation 10

11 Middleware Virtualization Traditionally Server Topology is fixed XD treats the cell as a virtualized resource pool It is a collection of machines that will host the applications. Nodes within a cell are tagged with capabilities. Custom capabilities may be defined. A Dynamic Cluster is a virtual cluster of servers hosting the application. The membership of the Dynamic Cluster is managed automatically The active size of the Dynamic Cluster is managed automatically based on service policy and current conditions Cluster members are placed on nodes which meet a set of specified capabilities Limits can be placed on the size of the dynamic cluster (min-max from 0-n) Applications are assigned to Dynamic Clusters A Dynamic Cluster can be configured in Manual, Supervisor or Automatic mode Isolation policies can be configured when dynamic cluster members are colocated on a node The combination of Node Capabilities and Dynamic Clusters provides the virtualization construct in XD 2011 IBM Corporation 11

12 WXD VE: Middleware virtualization Conventional Distributed Environment Environment Multiple business critical applications Hundreds of application servers Challenges Underutilized servers Inability to share resources across server pools especially during peaks Inconsistent quality of service for business critical applications Human-intensive monitoring and management environment Stock Trading 100% 0% 50% Account Management 100% 0% 50% Portfolio Forecasting 100% 100% 20% 55% 75% Utilized Servers 15% Utilized Servers 10% Utilized Servers 0% 50% 2011 IBM Corporation 12

13 WXD VE: Middleware virtualization WXD Environment Virtualized Pooled resources Virtualized applications Goals based Operational policies are attached to Application to reflect operational goals and importance of application Autonomic managers monitor environment for maximum utilization using business goals Results Reduce total cost of ownership (doing more with same/less) Increase stability and repeatability of environment Stock Trading Customer Support Account Management Risk Management Portfolio Forecasting 100% 0% 50% 55% Utilized Servers RESOURCE POOL 2011 IBM Corporation 13

14 Defining SLAs through Service Policy Service Policy is the definition of a performance goal used by XD to decide how to manage resources in the server environment Defined in terms of the end user result the customer wishes to achieve Comprised of three parts: A set of classification rules to decide which policy applies to a given request A performance goal the user desires to be achieved (i.e. 500ms average response time) An importance level to inform XD of the relative priority of different classes of work 2011 IBM Corporation 14

15 Policies Applying Business Goals to Applications Application Solutions Service Policies Goals Priorities Stock Trading Gold Gold RT < 1sec Very High Account Management Portfolio Forecasting Silver RT < 2sec Medium Customer Support Bronze Bronze RT < 5sec Medium Risk Management Idle Idle Best Effort Low 2011 IBM Corporation 15

16 Example Topology 2011 IBM Corporation 16

17 On Demand Router (1/2) The On Demand Router (ODR) is a component that logically replaces and extends the functionality of the ND HTTP Plug-in The ODR provides the standard functionality of a proxy server with added On Demand features Request classification and prioritization Request queuing Routing and load balancing Weighted round robin dispatching with Dynamic WLM weights Dynamic routing table updates with multiple WebSphere backend cells HTTP Session affinity SSL ID Affinity 2011 IBM Corporation 17

18 On Demand Router (2/2) The ODR does not need a plugin config file for request routing and load balancing (unlike an http server) The ODR uses On Demand Configuration component (ODC) to handle retrieval and distribution of back-end routing information Each ODR can be configured with one or more cell destinations Each ODR will automatically update its routing tables as applications are installed or removed from the back ends cells In the event that the DMGR is down or unavailable, the ODR continues to use its current configuration data The current configuration data is persisted to disk so that the ODR can be stopped and started even when the DMGR is not available 2011 IBM Corporation 18

19 Techniques to Meet the SLAs XD/ODR implements two primary techniques to meet Service Policy objectives Traffic Shaping Based on the notion that not all requests are equal and serving work firstcome-first-serve is not necessarily the best approach Controls Traffic in a number of ways Prioritization Processed in order of importance Flow Control Using queuing, the rate of work being sent to the server cluster is controlled Traffic Spraying - Dynamic Weights Overload Protection Control total amount of outstanding work for each class of service Application Placement The ability to adjust the size of a Dynamic Cluster in real-time Controls how much capacity is online for an application at any moment in time. Provides integration with Tivoli Intelligent Orchestrator to enable new hardware to be provisioned into XD s Node Group IBM Corporation 19

20 Dynamic application Placement with WebSphere XD Classification Scheduling and Flow Control Routing and Load Balancing Node 1 APC C B Client Client Node 2 C B Client Node 3 A B Client Node 4 A C 2011 IBM Corporation 20

21 Dynamic application Placement with WebSphere XD Classification Scheduling and Flow Control Routing and Load Balancing Node 1 APC C B Client Client Node 2 C B Client Node 3 A B Client Node 4 A C 2011 IBM Corporation 21

22 Dynamic application Placement with WebSphere XD Classification Scheduling and Flow Control Routing and Load Balancing Node 1 APC C B Client Client Node 2 C B Client X Node 3 A B Client Node 4 A C 2011 IBM Corporation 22

23 Dynamic application Placement with WebSphere XD Classification Scheduling and Flow Control Routing and Load Balancing Node 1 APC C B Client Client Node 2 CA B Client Node 3 A B Client Node 4 A C 2011 IBM Corporation 23

24 Dashboard and personalized views Example of CPU utilization for pseries LPARs with AIX configured in shared uncapped mode 2011 IBM Corporation 24

25 Unified Administration across Middleware Common collection views allow administrators to interact with their servers regardless of type 2011 IBM Corporation 25

26 1st Class Support for Non-WebSphere Platforms Three categories of support for middleware server types Complete Lifecycle Management - Create/remove server instances - Govern all aspects of server configuration - Provide operational control - Deploy applications - Server health and performance is monitored and visualized. Assisted Lifecycle Management - Provides specific templates for creating representations of existing servers and applications - Servers can be controlled operationally - Administrative utilities are provided to manage the external configuration and runtime - Server health and performance is monitored and visualized. Application Server V7.0/v6.1 Community Edition Community Edition Tomcat Application Server v1.x v2.x v6.0.x v5.x Generic Lifecycle Management - Provides generic templates for the user to manually define servers and operational commands. - Control server operations and monitor health and performance 2011 IBM Corporation 26

27 XD Management Topologies Non-WebSphere Machine XD Machine Non-WAS Middleware Servers (BEA, Tomcat, Jboss,.NET, Geronimo, WebSphere CE, etc) Grid Applications (Native App, Java Main, Standalone CIWork) ODR XD Agent PHP Server (Apache/mod_php) XD Agent Node Agent Node Agent XD Agent XD-Enhanced WebSphere Machine WebSphere Server (J2EE, CIWork, ParallelCIWork, Batch, WPF, ObjectGrid) XD Machine XD Agent XD-Enhanced Mixed Machine XD Agent DMgr Node Agent PHP Server (Apache/mod_php) Non-WAS Middleware Servers (BEA, Tomcat, Jboss,.NET, Geronimo, WebSphere CE, etc) WebSphere Server (J2EE, CIWork, ParallelCIWork, Batch, WPF, ObjectGrid) Grid Applications (Native App, Java Main, Standalone CIWork) 2011 IBM Corporation 27

28 Server Maintenance Mode XD provides the capability to isolate a running server (of any type) from production traffic. This allows for problem determination to be performed on the server or other maintenance without disruption to production traffic. If the server is a member of a dynamic cluster, a new cluster member will first be started before the server is placed into maintenance mode in order to assure the minimum policy on the dynamic cluster is met IBM Corporation 28

29 Highly Available Deployment Manager Configuration Each deployment manager on a separate machine Only one is active Others are standby administrative console active dmgr Shared file system required for dmgrs to share configuration repository File system with recoverable locks required - e.g. GPFS JMX traffic proxied through XD Ondemand Router (ODR) wsadmin scripting admin client On-Demand Routers standby dmgr SAN FS SOAP connector only HA ODRs recommended (they re recommended for production XD configurations anyway) hadmgrconfig command line utility provided to perform configuration administrative console wsadmin scripting admin client On-Demand Routers Standby dmgr Standby dmgr SAN FS Active dmgr 2011 IBM Corporation 29

30 Monitoring Operations XD provides a set of views for understanding the dynamic goals directed environment the application is being hosted in. The administrative console is enhanced with Operations and Reporting tabs off the detail view of servers, clusters, applications and service policies 2011 IBM Corporation 30

31 Monitoring XD Itself An XD Summary View is introduced for operators to monitor and receive visual alerts to when the stability of XD becomes questionable or unstable. Core runtime components can be tracked (location and stability) State and stability of ODRs Coregroup stability Node state and stability A reporting summary view provides operators with the ability to configure sets of indepth charts into groups that can be pulled up and viewed at any time for a real-time snapshot of the environment's performance IBM Corporation 31

32 Health Management Health Policies Health policies can be defined for common server health conditions Health conditions are monitored and corrective actions taken automatically Notify administrator Capture diagnostics Restart server Application server restarts are done in a way that prevent outages and service policy violations Health Conditions Age-based: amount of time server has been running Excessive requests: % of timed out requests Excessive response time: average response time Excessive memory: % of maximum JVM heap size Memory leak: JVM heap size after garbage collection Storm drain: significant drop in response time Workload: total number of requests 2011 IBM Corporation 32

33 Custom Health Conditions XD enables customers to create expressions defining what unhealthy means in their environment Custom expressions can be built using operands which represent metrics from the On Demand Router, base PMI metrics (WAS only), MBean operations and attributes (WAS only), and/or URI return codes. Complex expressions using a mix of operands is supported. Other middleware server types can leverage the ODR metrics and URI return code operands Create the health policy by using the createhealthpolicy AdminTask command 2011 IBM Corporation 33

34 Application Edition Management Administrative and workload management support for application versions Deploying a new application into production can lead to loss of service Application Edition Manager allows interruption-free deployment of application editions Coordinates the activation of application editions and the routing of requests to the application Validation Mode enables final preproduction testing of an application edition by a select group of users Routing Rules allow intelligent routing to multiple application editions in production Designate application edition or version levels Multiple application editions can run in production at the same time 2011 IBM Corporation 34

35 Application Edition Management WebSphere XD supports managing multiple editions of an application in a WebSphere cell Only on Complete Lifecycle Management servers Interruption-free rollout of application updates (grouped or atomic rollout) Ability to roll back to a previous application version Validation mode to verify functionality using a subset of users An edition is a distinct instance of a J2EE or PHP application (similar to version) Each edition is identified by a label An edition is a deployment version of an application May be a distinct build version May be the same build version with different deployment bindings (e.g., resource-ref) May be both Useful for maintaining work classes from one edition to another IBM Corporation 35

36 Edition Control Center: Manage Editions 2011 IBM Corporation 36

37 Edition Rollout 2011 IBM Corporation 37

38 Configuring Routing Policy On-Demand Router can be configured to route requests to a particular application edition By IP address By user or group By HTTP cookie By Header name By HTTP method Etc. Any combination of the above 2011 IBM Corporation 38

39 WebSphere Virtual Enterprise v7.0: key features Administrative Enhancements Fine-grained security support for WebSphere Console Historic Charting SNMP trap generation Health Policy Violations Dynamic Cluster state changes Centralized Logging On Demand Router Enhancements Dynamic Clusters Maintenance Mode Traffic Routing Health Monitoring Out of Memory Protection Performance Management Enhancements Solaris Zones AIX WPARs Multi-cell Performance Management APC Enhancements Service Policies without response time goals 2011 IBM Corporation 39

40 2011 IBM Corporation 40