IBM WebSphere Application Server 8. Clustering Flexible Management

Transcription

1 IBM WebSphere Application Server 8 Clustering Flexible Management Thomas Bussière- bussiere@fr.ibm.com IT Architect Business Solution Center La Gaude, France

2 WebSphere Application Server: High Availability concepts

3 Vertical scaling

4 Horizontal scaling

5 Horizontal & Vertical scaling

6 Controlling a cluster Start the cluster Start starts all servers together Ripplestart starts servers one at a time Status Started all servers are started Partial Start some servers are started Stopped all the servers are stopped Partial Stop some servers are stopped

7 Basic WLM request routing Routing decision points Load Balancer Routing decision table stored internally Configured using Load Bbalancer tool Multiple intelligent routing options HTTP Server plug-in Routing table part of plugin-cfg.xml Configured using administrative console or wsadmin scripting tool WLM-aware client Includes Web container, Java client, EJB Routing table supplied by name server Configured using administrative console or wsadmin scripting tool Options: Prefer local -- yes or no

8 Weighted routing example No affinity

9 Weighted routing example With affinity

10 Edge components failover Load Balancer can be paired with a backup machine Topology is active/standby One machine does all the work The other waits for a failure to begin handling routing

11 HTTP Server failover Multiple HTTP servers provide coverage Load Balancer can route around a failed HTTP server HTTP plug-in Every plug-in knows about all Web containers Session key contains address of server Sessions get properly routed All HTTP servers handle load before failover

12 Web container failover HTTP server plug-in Detects failure of Web containers Marks container as unavailable Tries next cluster member in the cluster What about in-flight sessions? Sessions may be persisted to database Sessions may be replicated in memory

13 Session persistence Session objects are cached in server memory by default, and therefore are lost if server fails Two methods to enable session persistence Database Session objects persisted using JDBC datasource DB2 included in package for session persistence Memory-to-memory replication Sessions copied to another server using WebSphere Platform Messaging

14 Session affinity An application may retain state information for a user s session in memory Other servers in the cluster might not have this information HTTP server plug-in routes subsequent servlet requests consistently to the same application server after the session created Using server ID passed with session ID in cookie or URL

15 WebSphere Application Server: Flexible Management

16 WebSphere ND V5/V6 Topology

17 WebSphere ND V7 Topology with Flexible Mgmt

18 Flexible Management Characteristics Loose coupling of various pieces Offers asynchronous job queuing mechanism for administration purposes Not meant to replace the existing deployment manager or base servers Offers administrators additional management options not previously available

19 New flexible management capabilities Management of multiple base servers, up to a server farm containing hundreds of base servers Coordinate management actions across multiple Network Deployment (ND) deployment managers Management of branch servers geographically dispersed and reachable only through low bandwidth, high latency network Asynchronous administrative job submissions that Take effect at a specified time Expire after a specified time Recur at a specified time interval Notify the administrator through when job is complete

20 Flexible Management Topology Example Admin Agent Centralized Node Administration Job Manager Asynchronous Remote Management Multiple Admin Agents and/or Deployment Mgrs Loosely Coupled: one-to-many and many-to-one Highly Scalable Admin Agent WAS Server Admin Agent WAS Servers Admin Agent WAS Express Server Job Manager Deployment Manager Server Server Server Server Server WAS Network Deployment Cell Deployment Manager Server Server Server Server Server Server WAS Network Deployment Cell

21 The Admin Agent A key component of Flexible Management New administrative process Admin Agent allows registration of profiles not registration of servers When a profile is registered with the Admin Agent, it is called a Managed Node Managed Nodes may contain multiple servers Some code that used to be part of every server is kept in the Admin Agent, reducing footprint and startup time Admin Agent polls for jobs from job manager on behalf of base nodes Note: dmgr will register with job manager directly i.e., no admin agent will be used for registration. dmgr also polls job manager directly and does not rely on admin agent for this.

22 The Admin Agent (continued) True remote management through admin agent: Create/start/stop/discovery/monitoring of servers Preserve existing management experience: Base nodes retain their configuration: no master repository or node sync Isolation between base nodes in admin agent different connector ports for each node different admin runtime instances for each node Reduce application server footprint; migrate admin functions to admin agent: Configuration management Application management Command Manager File transfer Admin console (can optionally disable)

23 The Job Manager Value add of job manager: Coordinate management action on group of nodes For example: one flexible management job to install the same application on a group of nodes Works with mixed platforms Can manage remote nodes Install IIM remotly

24 The Job Manager (continued) Base nodes retain their autonomy and isolation User can still manage base nodes separately via admin agent, with or without job manager Job Manager does not take over node s configuration Job Manager caches: Metadata of jobs available at each node List of available resources and their states, e.g., servers, applications. Job manager created as an option to the management profile template

25 WebSphere Application Server: Centralized Installation Manager in Job Manager

26 WebSphere Application Server v7 CIM in Deployment Manager Deployment manager pushes binary payload to targets. Binary payload V7, Fixpack, ifixes,updi Deployment Manager CIM V7, UPDI, Fixpack, ifixes Target node-metadata.properties

27 What s new in Centralized Installation Manager in V8 CIM is now available from the Job Manager Remotely drive IBM Installation Manager Install WebSphere Application Server, IBM HTTP Server, Application Clients, DMZ Secure Proxy Server, Web Server Plug-ins and WebSphere Customization Toolbox Support job scheduling Support multiple cells Better scalability

28 WebSphere Application Server V8 CIM in Job Manager Separation between Job Manager, Target Hosts and IM repositories. IM install kits Job Mgr IM repository (offerings) Binary payload CIM IM Install Kit; Response File Install jobs IM Host Inventory info

29 New Centralized Installation Manager Jobs Inventory Install, update and uninstall Installation Manager (New capability in version 8) Manage offerings (e.g. install, update, uninstall WebSphere Application Server) Manage profiles (New capability in version 8) Run command (New capability in version 8) Install SSH public key Distribute, collect and delete file (New capability in version 8) Test connection Add or search Installation Manager agent data locations

30 Supported platforms and software Supported platforms Windows, Linux, AIX, Solaris, HP-UX, IBM i and z/os Supported Installation Manager version Version and later Supported WebSphere Application Server version Install and uninstall of WebSphere Application Server V8 and the supplemental products IBM HTTP Server Web Server Plug-ins WebSphere Customization Toolbox Application Client DMZ Secure Proxy Server

31 Centralized Installation Manager in Job Manager

32 Register a New Host

33 Add Installation Manager Installation Kit

34 Install IBM Installation Manager

35 Select Targets

36 Input the Job Parameters

37 Schedule Job

38 Job Status

39