WebSphere Application Server v7.0

Transcription

1 IBM Software Group WebSphere Application Server v7.0 Technical Value Herve GRANGE WebSphere Technical Sales - IMT France Northwest Africa hgrange@fr.ibm.com Updated October 29, 2008

2 Important Disclaimer! "# 2 2

3 Agenda IBM Software Group WebSphere Application Server v7.0 Programming Model Currency Portlet support Systems Management Security WebSphere Runtime Performance 3

4 Nobody does it better WebSphere Application Server Version 7 brings Simplification for Developers High Performance SOA Environment Innovation that Matters Business Services Development Services Interaction Services Partner Services Process Services Enterprise Service Bus Business App Services Infrastructure Services Information Services Access Services Apps & Info Assets Management Services 4

5 IBM Software Group WebSphere Application Server v7.0 Programming Model Currency Updated October 29, 2008

6 Goal: Leverage Benefits of SOA Programming Model You want to Build and deploy new flexible, agile applications/services Reuse, extend existing applications Leverage programming standards to enable service composition Development Services Interaction Services Partner Services Business Services Process Services Information Services Enterprise Service Bus Business App Services Infrastructure Services Access Services Apps & Info Assets Management Services IBM Solution Core JEE 5 programming model Java Development Kit (JDK) 6.0 Support for latest Web services profiles Feature pack for Web 2.0 Support for Java portlets JSR 286 EJB 3.0, JPA standards for simplified programming Spring certification WebSphere Application Server Supporting the strongest, most comprehensive SOA programming model 6 6

7 WAS v7 Programming Model Currency Goals One word Simplify Simplify the programming model Simplify application coding Simplify application assembly / packaging Simplify testing Simplify Object Relational Mapping Simplify Web Services Development 7

8 Simplifying Object Relational Mapping WAS v7 uses annotations and dependancy injection to simplify JPA as well EJB 2.1 EJB 3.0 public abstract class CustomerBean implements public abstract class CustomerBean implements Customer, Customer, EntityBean EntityBean { { public public CustomerBean() CustomerBean() { { } } public abstract String getname(); public abstract String getname(); public abstract void setname(string n); public abstract void setname(string n); public abstract int getamountspent(); public abstract int getamountspent(); public public abstract abstract void void setamountspent(int setamountspent(int amount); amount); private EntityContext ctx; private EntityContext ctx; public public String String ejbcreatebyname(string) ejbcreatebyname(string) throws throws EJBException { } EJBException { } public void setentitycontext (EntityContext public void setentitycontext (EntityContext thectx) throws EJBException { thectx) throws EJBException { ctx ctx = = thectx; thectx; } } public public void void unsetentitycontext() unsetentitycontext() throws throws EJBException { EJBException { ctx ctx = = null; null; } } (name= (name= CUSTS ) public class Customer implements Serializable { public class Customer implements Serializable { public Customer() { } public Customer() public String getname() { return name; } public String getname() { return name; } public public void void setname(string setname(string n) n) { { name name = = n; n; } } public public int int getamountspent() getamountspent() { { return return amountspent; } amountspent; } public void setamountspent(int a) { public void setamountspent(int a) { amountspent = a; } amountspent = a; } private private String String name; name; private int amountspent; private int amountspent; } } 8

9 Simplifying Web Services Development With JAX-WS WAS v7 simplifies Web Services code using annotations JAX-RPC 1.1 Code public interface StockQuote extends Remote { } public float getquote(string sym) throws RemoteException; public class QuoteBean implements { } public float getquote(string sym) { } JAX-WS 2.0 public interface StockQuote { } public float getquote(string public class QuoteBean implements StockQuote { public float getquote(string sym) {... } 9

10 Using Technology Innovation to Meet Evolving Needs WAS v7 Expands Support through Business Level Applications Expanding the notion of Application beyond J2EE Extensible deployment logic framework Supports more than Application Server deployment target runtimes for example: Proxy Server, Web Server, CE, files, etc. Composition Configuration EJB Module Web Module BLA1 DB2 Database BLA3 JAX-WS Web Service Module Portlet Module BLA2 J2EE Enterprise App CICS Transaction Full lifecycle management of applications Install, distribute, activate, monitor, update, remove Business Logic JAR WAR Axis2 PAR EAR 10

11 Goal: Simplify Web Services Development You want to Interoperable, Reliable Web services Easy-to-implement Consumable and Extensible WS-I Reliable Secure Profile (RAMP Profile) WS-I Basic Security Profile WS-Addressing WS-SecureConversation WS-ReliableMessaging Token Profiles WS-Security IBM Solution JCP-based programming model JAX-WS 2.1, JAXB 2.1 SAAJ 1.3 StAX 1.0 WS-I Basic Profile WS-I Attachments Profile WS-I Simple SOAP Profile Web Services Standards WS-I Policy Reliable Sets allow Secure these Profile WS-ReliableMessaging to be specified WS-SecureConversation administratively WS-Addressing WS-I Basic Security Profile WS-I Basic Profile

12 WebSphere Application Server Function Evolution J5EE support J2EE 1.2 support Configuration data in database Support for Web Services J2EE 1.2, 1.3 support JDK 1.3 support Web Services based on Apache engine Configuration data in XML files Packaging simplification Network Deployment Cell for clustering and scalability Built-in messaging engine based on WebSphere MQ Merging of z/os and distributed code base J2EE 1.2, 1.3 support JDK 1.4 support Web Services based on JSR 101/109 on IBM engine Support for JSF J2EE 1.2, 1.3, 1.4 support Web Services based on J2EE 1.4 WS-Security and Basic profile support Common data model, SDO Inclusion of PME for all packaging High Availability Manager Java-based Messaging engine Mixed version cell support for V5.0.X and V6 J2EE 1.2, 1.3, 1.4 support JDK 5.0 support Portlet support Session Initiation Protocol (SIP) support WS-Notification, WS-Business Activity and WS-Resource Framework, WS-I BSP support Virtual Member Manager OSGi based architecture Consumability and ease of use enhancements Serviceability enhancements Optional Functions: WS-* EJB3.0 Web 2.0, Ajax Additional FEP or Product Extensions V4.0.X 2001 V5.0 4Q2003 V5.1 2Q2004 V6.0.X 4Q2004 V6.1 2Q2006 V6.1 FEP 2007 V

13 IBM Software Group IBM WebSphere Application Server V7 Portlet support Updated October 29, 2008

14 WebSphere Application Server v7 portlet support overview WebSphere Application Server V7 provides support for JSR 286 based portlets JSR 286 provides key improvements in the portlet programming model Events and shared parameters between portlets Improved coordination with frameworks Better serving of resources 14

15 IBM Software Group Leveraging Benefits of SOA Programming Model WAS v7 Strengthens the Portlet Programming Model Remote WSRP 2.0 Portlets participate in Context Portal Users P SR W Optionally use multiple JVMs for running your Portal Isolate untrusted Portlets from Portal Execute Portlets in their own JVM Enhanced scalability for heavy Portlets P SR W Portlet Container Portlet Container Portal Server (User Access) 2. 0 WAS (Portlet Server) P SR W Portlet Container Portal Server (Portlet Server) 15

16 IBM Software Group WebSphere Application Server v7.0 Systems Management Value Updated October 29, 2008

17 Goal: Capitalize on Intelligent App Server Management You want to Reduce SOA infrastructure administrative overhead Provide remote management for expanded topologies Cell config Node A configuration Admin Agent IBM Solution Flexible, loosely coupled application server management Introduction of administrative agents enabling asynchronous agent execution Expanded multi-node remote management Improved support of development/unit testing/qa environments Server configuration App Server Node A Admin scripts Admin console Intelligent management features ease admin. open new opportunities 17 17

18 Capitalizing on Intelligent App Server Management WAS v7 Overcomes Challenges of Existing WAS (Base) Management Current WAS (Base) Management Cell config Node A configuration Server configuration Application Server AdminService/JMX Mbeans Config Service Applcation Management Adminconsole Application Applications Administrative runtime hosted in Application Server Adminconsole runs in Application Server Scripts run against Application Server Cannot start/stop app server dynamically) Application server process has administrative overhead Can not manage multiple servers in a base profile Node Admin console Admin scripts 18

19 Capitalizing on Intelligent App Server Management WAS v7 Overcomes Challenges of Existing WAS (Base) Management New Flexible Management Option Separate admin from application request processing Application server no longer central point of management Cell config Node A configuration Application Server AdminService/JMX Mbeans Applications Reduce server footprint Transparency for base vs. ND configuration Server configuration Admin Agent Node AdminService/JMX Mbeans Config Service Applcation Management Adminconsole Application Adminconsole Admin scripts 19

20 Capitalizing on Intelligent App Server Management WAS v7 Overcomes Challenges of Existing WAS (Base) Management New Flexible Management Option Application Server AdminService/JMX Mbeans Applications Admin Agent can manage multiple base profiles All profiles created from same WebSphere installation Cell config Node A configuration Server configuration Application Server AdminService/JMX Mbeans Applications Admin Agent Unique admin ports in admin agent for each managed profile Administrative console provides choice of profiles to be managed Node AdminService/JMX Mbeans Config Service Applcation Management Adminconsole Application Adminconsole Admin scripts Job Manager 20

21 Capitalizing on Intelligent App Server Management WAS v7 Extends Existing WAS-ND Management Current WAS-ND Management Tight Coupling Between Node Application Server AdminService/JMX Mbeans Applications Application Server(s) and Node Agent(s) Node Agent(s) and Deployment Manager Server configuration Node Agent AdminService/JMX Mbeans Node A configuration Config Service Cell config Node Deployment Manager Node A configuration Server configuration AdminService/JMX Mbeans Config Service Applcation Management Adminconsole Application Adminconsole Admin scripts 21

22 Capitalizing on Intelligent App Server Management WAS v7 Extends Existing WAS-ND Management New Flexible Management Option Node Application Server AdminService/JMX Mbeans Applications Loose Management Coupling Coordinates management across a group of endpoints E.g. one job to install application across a number of nodes Server configuration Node A configuration Node Agent AdminService/JMX Mbeans Config Service Can manage via admin agent or ND deployment manager Node Job Manager AdminService/JMX Mbeans Cell config Node Deployment Manager Adminconsole Application Node A configuration Server configuration AdminService/JMX Mbeans Config Service Applcation Management Adminconsole Application Adminconsole Admin scripts 22

23 Capitalizing on Intelligent App Server Management WAS v7 Sets the Stage for More Flexible Management Topologies Admin Agent Admin Agent Job Manager Control multiple endpoints Remote management Loose Coupling Deployment Mgr Admin Agent WebSphere Application Server Base Application Server Programming Model QoS Security Administration Deployment Mgr Network Deployment Cell Administration Clustering 23

24 Capitalizing on Intelligent App Server Management WAS v7 Allows Flexible Management of Branch Organizations Supports high latency remote branch servers Supports geographically separated data centers Dmgr Job Manager Dmgr Dmgr Dmgr Admin Agent Dmgr Job Manager Admin Agent 24

25 Easing Application Serving Management Burden WAS v7 Integrates with DataPower to Expand SOA Mgt Support A next step in the evolution of broader administration integration across WebSphere Single Admin interface for managing both WAS and DataPower Tighter integration for management Admin interface for managing multiple DataPower boxes Multi-box management (existing DataPower requirement) Single point of administration for solutions that combine WebSphere Application Server applications with the DataPower 25

26 Using Centralized Mgt to Install App Servers WAS v7 Brings Centralized Installation Manager to IT Management Challenge: I ve got a lot of WAS-ND servers that I have to install and maintain! Patch management of my WebSphere application servers (WAS, ND) is challenging, takes too long, and I don t want to create my own way of doing it! Solution Centralized Installation Manager Simplifying Installation & Deployment Supports centralized installation from the Deployment Manager to Nodes in the cell Single install to the Deployment Manager which allows Push install package from DMGR to endpoints Select a set of hosts and push to those endpoints Installs appropriate endpoint code based on type of endpoint Agent-less Centralization of patch management 26

27 Goal: Rapid Infrastructure Provisioning You want to Achieve maximum flexibility and high productivity for SOA initiatives Leverage server virtualization technologies Consolidate servers Quickly provision WebSphere Application Server infrastructures Faster change management with fewer resources IBM Solution Extremely fast, highly productive infrastructure provisioning Reduce error in infrastructure provisioning Repeatable process Post-GA 27 27

28 Providing Rapid Infrastructure Provisioning WebSphere Virtual Appliance Open Beta Base SLES 10.1 Installation Multiple Disk Design OS Disk: SLES10SP1 WebSphere Binary Disk WebSphere IHS Disk WebSphere Profiles Disk Activation engine provides user level customizations (all automatable) Operating System: Network and Passwords WebSphere Configuration: choosing profile and constructing topology WebSphere is pre-installed WebSphere Application Server ND IBM HTTP Server 6 Profile types pre-created Attended customization via SuSE YaST panels Preliminary Open Virtual Format (OVF) support Logical Disk D Logical Disk C Logical Disk B Logical Disk A 6 profiles WAS Binaries IHS SUSE 10.1 Virtual Image 28

29 Providing Rapid Infrastructure Provisioning WebSphere Process Server Example Creation Steps (1,2,3) Activation Steps (4) 1. Install SLES Install WAS v6.1 without profiles 3. Install Process server v6.1 with a standalone Process server profile 4. Install activation engine with WAS scripts 5. Halt the virtual machine as template 1. Configure network --<10sec 2. Configure root security --<3sec 3. Configure Process server (1) Localize Process Server -- run changehostname (2) Start Process Server 29

30 30

31 IBM Software Group WebSphere Application Server v7.0 Security Value Updated October 29, 2008

32 Goal: Use Technology Innovation to Meet Security Needs You want to Strengthened security and security management across domains Increase flexibility in security configuration Improved security visibility through admin consoles IBM Solution Multiple security domains under central management Expanded security auditability Configuration utilities and console management to reduce manual effort Enhanced Kerberos support Evolving WebSphere technology addresses security mgt challenges 32 32

33 Using Technology Innovation to Meet Security Needs New WebSphere Security Domains Offers Greater Granularity, Flexibility, Control over Users and Infrastructure Applications can have own application security domain, own user population Application Application Application Realm Application Application Application Realm Application Application Application Realm Application Application Application App Server App Server App Server App Server Admin Subsystem Security Config Admin Subsystem Security Config Admin Subsystem Security Config Admin Subsystem Cluster Deployment Manager Realm Security Configuration Applications in a cluster share a common application security domain. Deployment Manager, Node Agent, and the Admin Subsystem common administrative security domain. 33

34 Using Technology Innovation to Meet Security Needs WAS v7 Provides Granular Security Admin thru Security Roles First Administrative User AdminSecurityManager Administrator Auditor Security Configuration iscadmins Partial Configurator Deployer Operator Monitor IBM Corporation

35 Using Technology Innovation to Meet Security Needs WAS v7 Offers Expanded Security Auditability (continued) Leveraging Auditability IBM Corporation

36 Using Technology Innovation to Meet Security Needs WAS v7 Enhances Kerberos Authentication and Single Sign-on (cont.) WAS v7 Kerberos (SPNEGO) Flow 1. The client sends an HTTP/Post/Get/Web-Service request to WAS. 2. WAS returns HTTP 401 Authenticate/Negotiate. 3. The client obtains a Ticket Granting Ticket (TGT). 4. The client requests a Service Ticket (TGS_REQ). 5. The client obtains a Service Ticket (TGS_REP). 6. The client sends HTTP/Post/Get/Web-Service and an authorization SPNEGO token to WAS. 7. WAS validates the SPNEGO token. If the validation is successful, it retrieves the user ID, the client Kerberos ticket and the GSS delegation credential from the SPNEGO token. 8. WAS validates the user ID with the WebSphere user registry and creates an LTPA token. 9. WAS returns HTTP 200, content and the LTPA token to the client IBM Corporation

37 IBM Software Group WebSphere Application Server v7.0 The Value of WebSphere Runtime Performance Updated October 29, 2008

38 WAS v7 Runtime Performance Achievement Optimized runtime performance that decreases footprint, saves energy and cuts costs IBM Java SE Version 6 enhancements add scalability and performance Runtime provisioning selects only the needed function for memory and space improvements Benchmark results lead the industry 38

39 Goal: Leverage Benefits of Java SE 6 Support You want Continued application startup time improvements Continued memory footprint reduction 64-bit memory and performance equivalent to 32-bit IBM Solution Broad Java SE 6 platform coverage Java SE 6 leading implementation Compressed references allow applications to access a larger heap space without using 64-bit objects Shared data cache and Ahead-of-time compilation for improved startup time Support for persistent shared data cache 39 39

40 Easing Application Serving Management Burden WAS v7 Provides Key Runtime Provisioning Capabilities Dynamic start of app server components based on application needs Reduces the runtime footprint less memory required Can significantly reduce startup times V6.1 Server V7 Server Web Container EJB Container Web Services SIP Container Security HA Manager Infrastructure All Activated HA Manager Security SIP Container Web Services EJB Container Web Container Infrastructure Dynamically Activated!! 40

41 Important Disclaimer! "# 41 41

42 IBM Software Group Maximizing Application Performance/Throughput WAS v7 Scalability Leverage Multicore Platforms to Your Advantage WAS v7.0 DayTrader 2.0 Processor Scaling Improvements v6.1 v7.0 Preliminary 1-w ay 2-w ay 4-w ay 8-w ay 16-w ay WAS V7 Multicore scalability with JEE 5.0 Significant scalability improvements in V7.0 over previous releases ~20% scalability improvement at 16-way (4 x Quadcore multicore) Vertical clustering provides near linear scalability WAS v7 can achieve near linear scalability of a single-instance by adding multiple instances in vertical clustering 42

43 Performance Benchmark Plans SpecJAppServer 2004 Planned Benchmark Submission Oct 2008 SpecJAppServer 2008 Planned Benchmark Submission Dec

44 Maximizing Application Performance/Throughput WAS v7 Supports Server Consolidation Using Virtualization Technology WAS v7 virtualization technology support Supported on key virtualization technologies (IBM Power VM, VMWare ESX Server, Xen, Solaris Zones, etc.) WAS v7 introduces virtual appliance download images for VMWare and Xen using SLES 10.1 Initial performance analysis/best practices developed and presented for WAS on Xen and VMWare Requests per second Number of 1G virtual machines Response time (secs) Throughput Response time Example from best practices documentation: Dangers of over-provisioning VM Memory 44