Multi-tier Application Environments

Transcription

1 Agenda: Multi-tier Application Environments Multi-tier Application Environments SOA: What is a Service Oriented Architecture (SOA) Tier-1 Clients Benefits of an SOA SOA with IBM products ESB and SOA lifecycle WebSphere Application Server V6.1: Workflow Message Exchang e Features Scalability and high availability B2B Connections Document Exchange JSP EJB Transaction management Servlet EJB EJB EIS integration Q & A PvC Tier-1 Servers Presentation Logic Tier-2 Servers Business Logic Tier-3 Servers Data Logic Tier-0 Web Browsers 1 2 Editions WAS v6.0 Packaging and Install Product install has a new look and feel compared to WAS V5 Extended Deployment (XD) Product images are distributed electronically on DVDs as well as CDs Enhancements have been made to the profile support On demand operating environment Network Deployment WebSphere Process Server Mainframe Qualities of Service Application Server Express Full J2EE 1.4 Web-based Admin Messaging Web Container EJB Container JDK PMEs Like Express with no limitation up to 2 CPUs Clustering Failover Workload Management Distributed Administration Web Services UDDI Registry Web Services Gateway Single integrated web-based platform Process Choreography Business Rules Business State Machines Human Task Business Object SCA based With full ESB connectivity and Adapters WebSphere Application Server for zos WebSphere Application Server Network Deployment (Clustered, multi-machine ) Base (Single Server) High Availability Manager, Edge Components Deployment Manager, Node Agent, Clustering Service Data Objects Work Manager, Application Profiles, etc. Web-based Administration, Web Services EJB Container, Messaging Web Container (Servlets, JSPs, XML) JDK 3 4

2 Packaging and Product Install Single Install Image for Application Server and Deployment Manager Product Binaries Separated from Configuration Greatly Reduced Number of Product CDs Support for multiple product profiles from single binary installation Creating Server Profiles V6 offers a tool (wasprofile) that creates different profiles Based on templates Product ships templates for default application, Deployment Manager, managed node Additional templates may be created with Profile Creation Wizard Changes for WebSphere Application Server 6.0 The default product configuration will itself be a profile Profile Templates that ship with WAS 6.0 Standalone Server similar to WAS 5.x default configuration Managed Node An empty node for the initial install of a production Deployment Manager A profile that defines the Deployment Manager for a Cell 5 6 WebSphere Configuration Archives Administrative options for exporting and importing: Full configurations Subset of a full configuration Configuration information is made generic so that it can be ported Removes any explicit reference to the environment where the archive was captured, like the host name Many different uses: Saving a portion of a configuration prior to making changes Creating a customized configuration archived to be imported at many different locations Creating definitions to be shipped with applications J2EE 1.4 Highlights Web Services and XML support Standards / Portability - XML Schema definitions for all deployment descriptors JAX-P New properties for XML parsers JAX-R - XML registry API JAX-RPC - APIs for representing WSDL-based services as RPCs in Java (and vice-versa) JSR Web services programming and deployment model SAAJ SOAP Attachments API for Java Messaging EJB 2.1 Typed message beans (used for any inbound JCA including pluggable JMS provider) Timer service Web service end-point support JMS 1.1 Unification of point-to-point and pub-sub interfaces ISV Enablement JMX 1.2 / JSR-077 (J2EE Management) Notification emitters, and standard patterns Information model representing J2EE application concepts JSR-088 (J2EE Deployment) XML-based deployment interfaces for J2EE JACC 1.0 Java Authorization Contract with Containers APIs for registering J2EE component authorization policies Other Servlet 2.4 Extensible deployment descriptors Request/response listeners JSP 2.0 Expression Language Simple Tag Extension EJB 2.1 Timer Service JDBC 3.0 Meta data and cursor support JavaMail 1.3 updates J2CA 1.5 In-bound connections RA lifecycle support Work manager (threads for resource adapters) 7 8

3 Changes in Web Services WebSphere 4.0 & 5.0 WebSphere 5.02/5.1 WebSphere 6.0 Apache SOAP The programming model, deployment model and engine Proprietary APIs Because Java standards for Web services didn t exist Not WS-I compliant JAX-RPC (JSR-101) 1.0 New standard API for programming Web services in Java JSR New J2EE deployment model for Java Web services SAAJ 1.1 WS-Security Extensions added WS-I Basic Profile 1.0 Profile compliance UDDI4J version 2.0 (client) Apache Soap 2.3 enhancements The engine is a new high performance SOAP engine supporting both HTTP and JMS JAX-RPC (JSR-101) 1.1 Additional type support xsd:list Fault support Name collision rules New APIs for creating Services isuserinrole() JSR WSEE Moved to J2EE 1.4 schema types Migration of web services client DD moving to appropriate container DDs Handlers support for EJBs Service endpoint interface (SEI) is a peer to LI/RI SAAJ 1.2 APIs for manipulating SOAP XML messages SAAJ infrastructure now extends DOM (easy to cast to DOM and use) WS-Security WSS 1.0 Username Token Profile 1.0 X.509 Token Profile 1.0 WS-I Basic Profile 1.1 Attachments support JAXR support UDDI v3 support Includes both the registry implementation and the client API library Client UDDI v3 API different than JAXR (exposes more native UDDI v3 functionality) Programming Model Extensions Programming model extensions (PMEs) are IBM-developed extensions to the J2EE model Core extensions included in all versions Formerly available only in Enterprise Edition Last Participant Support Internationalization Service WorkArea Service ActivitySession Service Extended JTA Support Startup Beans Asynchronous Beans (now called WorkManager) Scheduler Service Object Pools Dynamic Query Web Services Gateway Filter Programming Model (with migration support) DistributedMap Application Profiling 9 10 Service Data Object (SDO) Unified data representation & retrieval across heterogeneous data sources in a disconnected, source-independent format Exploitable by tooling to provide simple application development experience Support of XML typed data Support for dynamic and statically type data Client SDO Core APIs Data Mediator 1 Data Mediator 2 Data Mediator 3 Access APIs Data APIs Metadata Access APIs Metadata APIs Access APIs Data APIs Metadata Access APIs Metadata APIs Access APIs Data APIs Metadata Access APIs Metadata APIs Data Store 1 Data Store 2 Data Store 3 Supported Mediators: Relational database EJB Future Web Services XML Enhanced Application Server ToolKit (ASTK) Provides WebSphere users with a set of basic Eclipse-based tools for assembling, deploying, debugging and profiling their WebSphere applications Includes the following capabilities Eclipse 3.0 based workbench and JDT J2EE Assembly Support DD editors including WAS extensions (including PMEs that are now in the base) and bindings Module/EAR creation and editing WebSphere Rapid Deployment Capabilities Debug and Trace/Profiling Tools Server Tools Configuration Validation Automated Table and Datasource creation WebSphere Test Environment For both local and remote s (including ND managed s) Universal Test Client EJB/Web Services Deployment Tools CMP/RDB Mapping Editor 11 12

4 Application Management: Enhancements Enhanced EAR File Can include all of the information needed to run the application on a Bindings Information Resource definitions Per application security settings Integrated with the WebSphere Test Environment in Studio and ATK Fine-grained Application Update Ability to introduce small delta-changes to installed applications Ability to add/remove(*) modules to installed applications System Applications Binaries are stored in the product binary folder Simplifies PTF/Service Pack updates, prevents accidental removal Includes Admin Console, File Transfer App, etc. Web Server Administration Support for extensible types Web Server Generic Server Console allows management of Web Servers: Check the status of the Web Server Generate the plug-in configuration file for that specific Web Server No manual editing needed any longer Allows specifying keyring and keystore files In addition, if the Web Server runs on a managed node: You can propagate the file to the node using the console Special treatment for the IBM HTTP Server (IHS) Console allows stopping/starting, editing httpd.conf file, displaying error.log, and propagating plug-in configuration even on an un-managed node New Admin Console Look and Feel Integrated Web Performance Viewer (TPV) 15 16

5 Migrating to Version 6 Migration paths and tools available to migrate from V4 and V5 Mixed Version Cells WebSphere Application Server 6.0 supports a cell composed of multiple WebSphere nodes at different version levels Server 1 Version 6 supports J2EE 1.2, 1.3, and 1.4 applications In general, no changes to the application code are required Migrating from Version 5 significantly simpler than any past migration Thanks to mixed cells support Cell 6.x The cell can operate in this mode for indeterminate amounts of time Node 5.x Supported node versions include: WebSphere Application Server 5.0.x Distributed WebSphere Application Server 5.1.x Distributed WebSphere Application Server 6.x Distributed Node 6.x Server 2 Server 3 Server 4 J2EE 1.3 Capabilities J2EE 1.4 Capabilities TransportChannel Service WebContainer WebContainer Channel HTTP Channel Thread pools and other resources shared between WebContainer and Messaging TCP Channel 1. Non-blocking IO improves scalability (Does not require 1 thread per connection) 2. WebContainer and Messaging can share the same port can share the same thread pool Small number of threads only doing work for active operations hold state for many connections waiting on network I/O operations Port Shared between WebContainer and Messaging Messaging JFAP Channel 19 JMS Support WebSphere V6 will provide a pure Java JMS 1.1 provider that is installed as part of the base installation not a silent install of another product with its owns prereqs and runs completely inside the application JVM Persistent messages are stored either in an embedded Cloudscape database or an external database of customer choice (DB2, Oracle, etc) via JDBC driver Each application can host a messaging engine. Messaging engines can be interconnected to form a messaging bus Fully integrated with application management including high availability. Messaging engines will failover along with application s Interoperable with WebSphere MQ R5 App Server 1 process app security Java app cluster modelcode Event Broker JMS (MA88) MQ C & Java 9 messaging code processes R6 integrated security 1 process... Base Server with J2EE, Integrated messaging all Java code Cloudscape or other RDBMS for persistence support 20

6 Enterprise Service Bus Enablement V6 includes the Service Integration Bus (SIB) An important contribution to the ESB concept JMS resources and Web Services can be exposed to the Bus Multiple Buses can communicate Fully administered via the console WebSphere 6.0 High Availability Services WebSphere 6.0 has significant improvements in its high availability capabilities Goal WebSphere 6.0 be used as part of an overall % availability solution A built-in high availability manager Provides Key Services needed to manage the clusters Reliable, high-speed, low-latency interconnect (Reliable Multicast UDP or Multicast over TCP) Distributed Computing Services Elections, Quorums, Heartbeats (Active or TCP Keepalive), Virtual Synchrony Singleton Management 1 of N Runs key services on available s rather than on a dedicated one (such as the deployment manager) Offers hot standby and peer failover for critical singleton services Transaction Logs Messaging Engines Takes advantage of fault tolerant storage technologies such as Network Attached Storage (NAS) to significantly lower the cost and complexity of High Availability configurations The configuration of high availability systems is significantly simplified WAS and JMS Highly Available V6 System Enhanced Data Replication Service No HACMP software on any blades, just install WAS If a blade running the messaging engine fails then a peer restarts the engine from the failed blade after 20 seconds. Messaging engine keeps messages in remote DB. WAS elects an online to run the messaging engine and WLM routes JMS connections to that. Blades 100M/1GB Ethernet Active/Standby Clustered/HACMP DB Rebasing on top of / Integrating with HA Manager and Transport Channel services Improves performance and scale: Improvements in the range of 4x to 8x Improves high availability and failure recovery: Leverages the failure detection provided by high availability services Allows for "active failure recovery" For example, with HttpSession replication, if the affinity for a HttpSession goes down, WLM can route to another that has a backup copy ready to use Improves usability: Leverages group services to simplify partitioning Now have "n-replica", where the customer simply defines the number of backup copies they want for data Stateful Session Beans state now replicated 23 24

7 WebSphere Administration Configuration Repository XML Document Repository all configuration stored in collection of XML and XMI documents on the file system no RDBMS WebSphere Common Configuration Model (WCCM) Data-model representing the configuration of the system Documented API for manipulating WebSphere configuration files Servers load directly off of documents In a cluster, WebSphere manages synchronization of documents across machines Application Binaries are managed as part of the repository WebSphere System Management - JMX Java Management Extensions (JMX) used both internally and externally to manage WebSphere runtime components and resources Provides Runtime Attributes Access to runtime operations Access to configuration Access to performance data Provides management tool vendors with a standard interface for monitoring and controlling WebSphere WebSphere Admin Security Authorization WebSphere Application Server ND - Terminology WebSphere 4.0 adminstration had no granularity of access control for the administrative sub systems anyone with a userid/password can configure/operation on the entire domain WebSphere 5.0 has finer granularity of access control. Defines 4 security roles: "monitor" role can observe system state and configuration data but cannot make changes "configurator" role is a monitor who make changes to the WebSphere system configuration "operator" role is a monitor who can change runtime state (e.g. start, stop) "administrator" role which is basically a configurator and also an operator configurator monitor operator Administrative Security Role Inheritance Relationship Cell Network of multiple nodes in a single logical administration domain Deployment Manager Manages the multiple nodes in a distributed topology Node Agent Resides on a single node Manages the s running on the node Managed Process or Server Each running in its own JVM Application Servers JMS Server Node Agent App Server Node Agent App Server Node Agent App Server XML XML Config XML Config Config Deployment Manager -Admin Node Agent App Server App Server XML XML Config Config App Server XML Config administrator 27 28

8 Architectural design: scalability and availability WebSphere as Transaction Manager WebSphere AS as Transaction Manager Application HTTP plug-in HTTP Edge Application plug-in Application HTTP plug-in Edge HTTP plug-in HTTP plug-in HTTP plug-in Firewall Application Connectors Application zos/390 IMS CICS DB2 MQ Oracle ResourceManager ResourceManager ResourceManager DataSource DataSource DataSource Jdbc TransactionManager I scenario II scenario III scenario DB user HA DB session UserTransaction Container EJB EJB EJB Request Interceptors ORB ApplicationServer WebSphere WebSphere AS as Transaction Manager WebSphere Application Server v6.1 Overview Application CTG TCP62 TCP/IP Netbios LU6.2 RPC WAS v6: Last Participation support feature for twophase commit with CICS CICS zos Application EJB container RMI/IIOP CICS solo TS2.2 EJB container zos 31 32

9 Upgrade to Java SDK 5.0 Web Services evolution WAS V5.0.2/5.1 WAS V6.0 WAS V6.1 IBM s Virtual Machine for Java and JIT includes Improved performance Improved startup Improved garbage collection No Sun intellectual property IBM s Virtual Machine for Java used on Windows, Linux, AIX, i5/os, z/linux and z/os Sun s JVM used on Solaris and HP-UX JAX-RPC (JSR-101) 1.0 New standard API for programming Web services in Java JSR New J2EE deployment model for Java Web services SAAJ 1.1 WS-Security Extensions added WS-I Basic Profile 1.0 Profile compliance UDDI4J version 2.0 (client) Apache Soap 2.3 enhancements The engine is a new high performance SOAP engine supporting both HTTP and JMS JAX-RPC (JSR-101) 1.1 Additional type support xsd:list Fault support Name collision rules New APIs for creating Services isuserinrole() JSR-109 WSEE 1.1 Moved to J2EE 1.4 schema types Migration of web services client DD moving to appropriate container DDs Handlers support for EJBs Service endpoint interface (SEI) is a peer to LI/RI SAAJ 1.2 APIs for manipulating SOAP XML messages WS-Security WSS 1.0 WS-I Basic Profile 1.1 Attachments support WS-TX AT (Atomic Transactions) JAXR support UDDI v3 support Includes both the registry implementation and the client API library WS-BA (Business Activity) Compensation framework for loosely coupled transactions WS-I BSP (Basic Security Profile) Interoperability over the wire (i.e. WebSphere client with.net svr.) Tightening of specification WS-N (Notification) Publish/Subscribe model WS Security enhancements Performance Enhancements SAAJ changes (send XML docs. w/ attachments) SOAP/JMS New and faster parser (Banshee instead of B2B) SOAP/JMS Enhancements Caching enhancements Text message enhancements WS-RF (Resource Framework) Stateful web service resources WS-Addressing Endpoint ref. support for WS-Res Portlet support overview Installation enhancements 35 36

10 IBM HTTP Server Administration Allows complete configuration of IBM HTTP Server through the administrative console Provides operational management of IBM HTTP Server through the administrative console Security enhancements: overview Administrative security enabled out of the box Fine-grained administrative security capability Users can now be defined to administrative roles on a specific set of resources Cells, node groups, nodes, clusters, s and applications Security enhancements: overview (cont.) Simplified certificate and key management Federeted repositories feature Ability to use mutiple heterogeneous user repositories User identity, profile, and relationship management Simplified administrative console tasks and guided tasks SPNEGO support for single sign-on authentication through Windows desktop 39 40

11 App Server Federated repositories overview WAS v6 Extended Deployment Extended Deployment (XD) On demand operating environment Network Deployment Application Server Express Full J2EE 1.4 Web-based Admin Messaging Web Container EJB Container JDK PMEs Like Express with no limitation up to 2 CPUs Clustering Failover Workload Management Distributed Administration Web Services UDDI Registry Web Services Gateway WebSphere Process Server Single integrated web-based platform Process Choreography Business Rules Business State Machines Human Task Business Object SCA based With full ESB connectivity and Adapters WebSphere XD - Design Principles An add-on or extension to the WAS ND environment Prereqs WAS ND instead of bundling it Installation is a simple delta to an existing environment Does not require migration or restructuring of current installation Totally integrated into the WAS ND environment Extends the WAS Admin Console Extends the wsadmin scripting environment Meaningful without implementing full Autonomic concepts Manual and Supervised modes allow autonomics to be adopted gradually Goals-directed WLM can be implemented without placement features Extended Manageability features such as visualization and health monitoring have broad appeal WebSphere Extended Deployment (XD) Supporting On Demand - Mission Critical Applications Dynamic Operations Resource pooling and allocation in a WebSphere environment Application differentiation through operational policies Dynamic routing and workload management High Performance Computing Application partitioning High availability services J2EE development of high-end OLTP applications Extended Manageability Flexible modes of runtime operations: manual, supervised and on demand, HA Deployment Mgr, Application Edition Control Centre Runtime operations tree map, charting and event visualization tools App Server Extensions Deployment Manager - Admin -Clustering Node Agent App Server 43 44

12 Dynamic Operations Capabilities Help Increase Responsiveness and Flexibility Virtualized WebSphere Environment I want my IT resources to adjust on the fly to the demands of business critical applications Create pools of resources that can be shared among applications Scale for unpredictable application demand Scale beyond the defined application pool with Tivoli Intelligent Orchestrator (option) Scale on demand through dynamic allocation of WebSphere resources Breaks the tie between application clusters and machines which can now be shared amongst applications, optimizing resource utilization and simplifying overall deployment Dynamically adjusts application resources as needed depending on demand Dynamically expands and contracts resources by adding and removing machines into and out of resource pools when it is deemed necessary by monitoring logic Dynamic Operations Customer Scenario: Large Financial Company Conventional Distributed Environment Environment Multiple business critical applications Hundreds of application s Challenges Underutilized s Inability to share resources across 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 15% Utilized Servers 100% 0% 50% 100% 0% 50% 100% 20% 55% 75% Utilized Servers Portfolio Forecasting 10% Utilized Servers Dynamic Operations Customer Scenario: Large Financial Company Goals Directed Infrastructure WebSphere Extended Deployment Environment Virtualized Pooled resources Virtualized applications Stock Trading Customer Support I want to get the most out of my infrastructure while at the same time ensuring consistent and predictable performance of business-critical applications Deliver application availability and performance using policies based on defined business goals Goals based Results Operational policies are attached to Application to reflect operational goals and importance of application Autonomic managers monitor environment for maximum utilization using business goals Reduce total cost of ownership (doing more with same/less) Increase stability and repeatability of environment Account Management Risk Management Portfolio Forecasting 55% Utilized Servers 100% 0% 50% RESOURCE POOL Define required application service levels consistent with business goals Deliver enhanced quality of service for business critical applications Balance workload based on actual performance of s Application performance is optimized according to operational policies that reflect application service level goals and relative importance to the organization User requests are classified, prioritized, queued and routed to s based on application operational policies (which are tied to business goals) Server weights (and associated workload routing) are dynamically adjusted based on actual performance, resulting in optimal application throughput and response time 47 48

13 Policies Applying Business Goals to Applications Key components : On Demand Router Application Solutions Stock Trading Stock Trading Account Management Portfolio Forecasting Customer Support Risk Management Service Classes Goals Priorities Gold Gold Silver Bronze Bronze Silver Idle Idle RT < 1sec for < 10 TPS RT < 2sec for < 10 TPS RT < 5sec for < 10 TPS Best Effort Very High Medium Medium Low 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 compliant HTTP and SOAP proxy 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 WPF Partition Affinity Example Topology WebSphere Dynamic Operations Environment High Importance Stock Trading Classification Prioritization and Flow Control Routing and Load Balancing Node 1 Node 2 ST ST AM AM Placement Executions Medium Importance Account Mngmt Node 3 ST FA Stock Trading Low Importance Financial Advice WebSphere on demand Router Node 4 Node 5 FA FA AM AM Account Mngmt Financial Advice Application Demand Resource State WebSphere Cell Operational Policy WebSphere XD Decision Makers Placement Decisions 51 52

14 Macro Provisioning in XD using TIO ODOE Virtualization Policy Prioritization Provisioning Visualization Web Server WebSphere - Banking WebSphere - Trading Lotus - Enterprise Business Policies MAPE MAPE MAPE MAPE Tivoli Intelligent Orchestrator (TIO) WebSphere High Performance Computing: Partitioning Facility Conventional Distributed Environment Environment High application transaction volumes and database hits High growth rate Large number of distributed s, prefer to scale linearly for additional capacity Continuous availability Challenges: Transaction volumes are limited by database access Scaling to accommodate growth requires significant system reconfiguration to ensure high transaction speeds Transaction requests are spread evenly across s WebSphere Servers All s require real-time shared database access Database Database eventually becomes a bottleneck WebSphere High Performance Computing: Partitioning Facility WebSphere Extended Deployment Environment High Performance Computing Capabilities Dynamic data partitioning and re-partitioning High end caching Workload management Autonomic high availability management Results Consistently low response times % availability (Class 5) Linear scalability on commodity hardware High performance, availability and scalability WebSphere Servers Database WebSphere Extended Manageability Customer Scenario: Application Service Provider Conventional Distributed Environment Environment 50+ applications 500+ application instances across distributed locations Challenges No application-centric visualization of the entire running environment Operators must provide own mechanisms (scripts, user interface, etc.) for monitoring the runtime behavior and performance Runtime decisions must be manually made no events or WebSphere supervision to assist in maintaining an optimal runtime environment 55 56

15 WebSphere Extended Manageability Customer Scenario: Application Service Provider WebSphere Extended Deployment Environment Visualization & Monitoring of Operations Variety of runtime operational views Customized charting Real-time event reporting Results Operators can see what is going on at a glance Tasks from autonomic managers keep operators aware of how well the environment is running and suggests changes to optimize the environment Application performance is measured against business goals WebSphere XD: Visualization Runtime Topology Two Main Purposes: What is Running Where What Has Potential To Run Different Perspectives: Application Centric Node Group Centric Service Policy Centric Quick Glance Hover-overs Content Changes on Item Hovered Example - Server Instance: PID, dwlm Weight, Node Name HA Managed Item Running Locations Health Management Controller Application Placement Controller dwlm Controller Health Monitoring WebSphere XD Tasks XD Providing monitoring of certain aspects of the WebSphere system to detect and take action on potential problems Health monitoring is defined by a set of Health Policies of the following types Age-based Workload-based Excessive Memory Utilization Excessive Response Time Health policies can be applied to individual s, to clusters, or to an entire cell When a problem condition is detected, one of three action styles can be put into effect Monitor Simply notify the administrator Supervise Notify the administrator of the problem and provide an action (such as restart the ). The administrator has to approve the application of the action Automatic Notify the administrator and automatically take action (such as restart the ) Notifications are provided in the Admin UI and optionally via

16 Notification XD Supports sending health monitoring event to an administration via The notification configuration looks something like this: Health Controller The health monitoring is controlled by an HA-Managed service called the Health Controller The health controller determines how aggressively XD monitors for violations of the health policies The controller configuration also allows you to adjust how often restarts will be allows and it allows you to define blackout periods when restarts should be prohibited. The configuration of the health controller looks something like this: HA Deployment Manager Console Support System Administration > Deployment manager Application Edition Control Center Functional Objectives Provide interruption-free application update capability Explicit control through systems management interfaces Careful orchestration of moving parts by system management infrastructure to ensure requests are not sent to s undergoing transition Introduce systems management support for application versions in the WebSphere environment Allow for multiple deployments of same-named J2EE application Unique version identity for each instance Enable multiple activation patterns Simple activation Validation mode Rollout interruption-free replacement of one version with another 63 64

17 Console example Lazy Application Start Dynamic Clusters support a min and max number of instances Default is min 1 and max N, where N = the number of nodes in the node group A user can set limits to whatever they desire A user can also set the min size to zero. This means that the application may not be running in the pool anywhere. When a request is received an instance of the application is started When the application goes idle the instance is stopped This allows low volume applications to be available without consuming resources Dynamic Cluster Configuration Vertical Stacking Business Grid Description Multiple cluster members on a node Allows full utilization of resources. Stacking number Application instances that are active when the CPU reaches 100% utilization Can be defined at the node level, overriding the Cluster level definition Determine the number of instances to create by profiling the application Profiling phase must be performed on each node type Different number of instances might need to be created on each node Need exists for long-running, resource-intensive work that does not fit the transactional paradigm Traditional J2EE model is transactional, short lived, lightweight units of work Long-running work might take hours or even days to complete and consume large amounts of memory or processing power while it runs. WebSphere Extended Deployment accommodates applications that need to perform long-running work alongside transactional applications The functionality of running both transactional and long-running units of work is called the Business Grid 67 68

18 Business Grid Programming Models Based on J2EE Compute Intensive Applications A job that uses the CPU for an extended time to perform some computation Based on CommonJ WorkManager Work object (extended as CIWork) A free form model that is very flexible for Java-based Grid Applications Java Transactional Batch Implemented as a EJB CMP Entity Bean Container manages transactions, data streams, steps, checkpointing, and job lifecycle Customer provides logic to process one record in the data stream Data streams are an abstraction that supports data from any source, including database, network, files, etc. Applications are packaged and deployed as regular J2EE EAR files Scheduler Scheduler supports standard job control operations Submit Start, Stop Pause, Resume GetStatus Jobs can be submitted via Command line tool Web services EJB interface Scheduler and Jobs can be configured and monitored via the WebSphere admin infrastructure XD is a Quality of Service Extender for Middleware WebSphere Process Server WebSphere Extended Deployment XD as an Extension to a WebSphere Serve Environment WebSphere ESB (post v6.0.1) WebSphere Portal Server WebSphere Commerce Server WebSphere Application Server Network Deployment WebSphere Application Server J2EE (BEA, JBoss, Geronimo, WebSphere CE, Tomcat, Jetty, Oracle, etc.) LAMP/LEAP PHP Ruby.NET Static HTTP (Apache, IHS, IIS, etc) XD is constructed as an extension to an existing middleware environment XD provides QoS features to extend what types of applications you can run on your middleware and how you run them XD works across a heterogeneous environment that includes IBM WebSphere and non-websphere s 71 72

19 XD as an Extension to a Non-WebSphere Server Environment WAS ND License XD Full License Scale Out Non-WAS ODR Topology Network Cell ODR Tier Deployment Manager HTTP Servers (Apache, IHS, Sun, IIS) J2EE Servers (Tomcat, Jboss, Geronimo, BEA, Oracle, etc).net Servers Optional Monitoring Agent Optional Monitoring Agent Optional Monitoring Agent XD MSE Server License Steps to construct a mixed environment Do you have an ODR defined? We are providing workload shaping We are not providing application placement Configure Virtual hosts Service classes Transaction classes Optionally, install remote agent on all the external nodes Improved feedback loop for the ODR Data collected include Node capacity Node utilization Install characteristics Hard disk footprint ~80MB RAM footprint ~15MB Default port is 9980, configurable WAS ND License XD Full License Agenda: SOA: What is a Service Oriented Architecture (SOA) Benefits of an SOA SOA with IBM products ESB and SOA lifecycle WebSphere Application Server V6.1: Features Scalability and high availability Transaction management EIS integration Q & A 75