IBM WebSphere Application Server v6

Transcription

1 IBM WebSphere Application Server v6 What s New

2 2 Agenda Main themes Product packaging Architectural overview New features overview

3 3 Section Main Themes & Product Packaging

4 4 Main Themes Platform enablement Developing the e-business operating system for enterprise integration Foundation for other middleware products Ease of use Reduced complexity, and increased integration of roles Simplify development and deployment of applications with new WebSphere Rapid Deployment Improvement on the flexible and open Systems Management model from WebSphere v5, with many new enhancements

5 5 Main Themes (continued) Enterprise Class Deployment Building the "Next Generation" application server with the qualities of service required by enterprise class deployment Enterprise Service Bus (ESB) infrastructure integration in the Application Server Unifies Service Oriented Architecture synchronous and asynchronous messaging, message brokering and publish/subscribe, mediation and Web Services integration Unified Clustering Framework and High Availability services Standards-based architecture and programming model Builds on the latest Java standards and Web Services in an integrated development and deployment environment to reduce time to value J2EE 1.4, Web Services, Service Data Objects (SDO), etc.

6 6 Version 5 Packaging

7 7 Version 6 Packaging

8 8 Platform Support (32-bit) AIX 5.1, 5.2 and 5.3 HPUX 11iv1 OS/ and 5.3 RedFlag Advanced Server 4.1 Redhat Enterprise Linux 3.0 Solaris 8 and 9 SuSE Linux Enterprise Server 8 and 9 Windows 2000 Server SP4 and Windows Server 2003 z/os 1.4, 1.5 and 1.6

9 9 Platform Support (64-bit) HPUX 11iv2 (Itanium 2) Redhat Enterprise Linux 3.0 (IBM pseries, AMD and Intel) SuSE Linux Enterprise Server (IBM pseries, AMD and Intel)

10 10 Section New Features Overview

11 11 New Features Overview Programming models WebSphere Profiles System Management Enhanced EAR WebSphere Rapid Deployment Platform Messaging Workload Management High Availability Logging and Tracing Security

12 12 Section Programming Models

13 13 Application Programming Model Support New v6 Supported J2EE Application versions in v6 Application Server J2EE 1.4 J2EE 1.3 J2EE 1.2 Simplifies migration by allowing your existing J2EE 1.2 or 1.3 applications to run in v6 Application Server

14 14 Mixed Version Cells WebSphere Application Server 6.0 supports a cell composed of multiple WebSphere nodes at different version levels Server 1 Node 5.x J2EE 1.3 Capabilities Cell 6.x The cell can operate in this mode for indeterminate amounts of time Supported node versions include: WebSphere Application Server 5.0.x Distributed WebSphere Application Server 5.1.x Distributed WebSphere Application Server 6.x (Distributed and z/os) Server 2 Server 3 Node 6.x J2EE 1.4 Capabilities Server 4

15 15 J2EE 1.4 Overview 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 Pluggable 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 J2CA 1.5 In-bound connections (supporting pluggable JMS provider, generalized for other types) RA lifecycle support Work manager (threads for resource adapters) ISV Enablement JMX 1.2 / JSR-077 (J2EE Management) Notification emitters, and standard patterns Information model representing J2EE application server 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 JDBC 3.0 Meta data and cursor support JavaMail 1.3 updates

16 16 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)

17 17 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 Supported Mediators: Relational database EJB Data Store 2 Data Store 3 Future Web Services XML

18 18 JavaServer Faces (JSF) Provide an easier and visual way to build J2EE Web applications with rich set of UI for a variety of client devices WebSphere Application Server v6 runtime and IBM Rational Web/Application Developer tools Supports JSF v1.0 JSF jar files and tag libraries are included with the runtime environment Includes a number of IBM value-add JSF custom components, permitted by the specification

19 19 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

20 20 Section WebSphere Profiles

21 21 WebSphere Profiles: What is a Profile Enhanced in v6 WebSphere Application Server version 6 is split into 2 parts A set of shared read-only product files A second set of configurable files All the configurable WebSphere files are called a Profile and put under a Profile directory These configurable files include WebSphere configuration, applications, and properties files.

22 22 WebSphere Profiles: Value Add Enhanced in v6 A Profile allows multiple WebSphere runtime environments share the same product binaries. WebSphere runtime environments being: Stand-alone Node Managed Node Deployment Manager Less disk space is used (exponential savings the more servers added). Product update is simplified (update single set of binaries, instead for every server and server configuration)

23 23 Section System Management

24 24 System Management Features New v6 New v6 New v6 New v6 Extends v5 System Management Model Reduces learning curve for managing v6 environments Support for J2EE 1.4 specification JMX 1.2 J2EE Management (JSR-077) J2EE Deployment (JSR-088) features Fine-grained Application Update Ability to introduce small delta-changes to installed applications Ability to add, update or remove parts of the installed application and restart the changed part Support for extensible Server types Web Server Generic Server Introduction of Node Groups z/os and Distributed Nodes within same cell

25 25 System Management Features (continued) New v6 Improved Administrative Console look and feel New v6 New v6 Provides consistent cross-ibm product look and feel Changes console views based on context Version Platform Installed Capabilities Integration of Tivoli Performance Viewer Integration of IBM HTTP Server v6 management System applications : Administrative Console, File Synchronization

26 26 WebSphere Configuration Archive Basically the same as a regular WebSphere configuration, with two main differences: It may be a subset of a full configuration Configuration information is virtualized to make it portable Removes any specific information, like the host name WebSphere Configuration Archives are used to import/export configurations Allows simple creation of many servers with the same configuration

27 27 New Admin Console Look and Feel

28 28 New Admin Console Look and Feel

29 29 Integrated Performance Viewer

30 30 Integrated Performance Viewer - Summary Report Integrated Into Console

31 31 Section Enhanced EAR

32 32 Enhanced EAR: Overview An Enhanced EAR is a zip file that contains a J2EE application (regular EAR) along with deployment information, some application resources (JDBC), and properties (like a class loader), and configuration variables. Enhanced EAR Enhanced EAR Resources Properties J2EE App. EAR Enhanced EAR support integrated with Rational Tooling WebSphere Application Server v6 Benefits: Application resource definitions/properties are brought in with the application Application install process automatically creates the necessary resource definitions within the server or cluster Moving application from one server to another also moves the resource definitions

33 33 Enhanced Ear: Deployment Enhanced EAR contains the J2EE (1.2, 1.3 or 1.4) application and its resources/properties (automatically added to the server) Admin Console IBM Rational Web/Application Developer Configure J2EE App. EAR Deploy/Install V6 Node V6 Node ND Installation Resources Properties v6.0 Test Environment v6.0 Application Server Separate Install (Local or Remote)

34 34 Section WebSphere Rapid Deployment

35 35 The Goal - WebSphere Rapid Deployment To simplify the development experience for WebSphere applications by: Reducing the number of artifacts Reducing the number of concepts and technologies Supporting the development model and tools To simplify the deployment experience for WebSphere applications by: Automating the process of installing an application on WebSphere Reducing the amount of information that must be collected by the installer Automating the process of activating incremental changes to an application on a running server

36 36 Focus Areas WebSphere Rapid Deployment Annotation-based Programming Allow the developer to create and maintain a single artifact Allow the developer to insert metadata into the source code of the application Use the metadata to generate the additional artifacts required by the runtime that the developer does not need to be confronted with Change Triggered Processing Drive processing operations based on the detection of change in artifacts of the application Used to generate new application artifacts from existing artifacts Used to drive deployment operations Enables a Hot Directory concept for file copy and Notepad development and deployment Deployment Automation Enable automatic installation of applications and modules onto a running WebSphere Server Support both local and remote servers Support fine-grained application changes Support the concept of minimal application impact (affect the application in the minimum way possible to reflect the detected change)

37 37 WRD: Annotation-based Programming Developer adds metadata tags into application source code Uses XDoclet tag syntax, where defined WRD uses the metadata to generate additional artifacts needed to run the application on the Application Server Minimizes number of artifacts a developer needs to create and understand user maintains the single artifact Single Java Source File with Annotation-based programming Multiple Java Source Files and application artifacts package com.ibm.wrd; /** name="hello" type="stateless" * view-type=both jndi-name="hellobean" */ public class Hello { /** view-type=both */ public String hello(string name) { return "Hello: " + name; } } Generates HelloSSB HelloHomeSSB HelloLocalSSB EJB Deployment Code Hello.java HelloLocalHomeSSB HelloBeanSSB

38 38 Section Platform Messaging

39 39 Platform Messaging WebSphere Application Server Platform Messaging is a fully-integrated pure-java messaging environment Its allows WebSphere Application Server to participate in an implementation of an Enterprise Service Bus ESB is a conceptual model for SOA SIBus is the WebSphere implementation of a single ESB component JMS support is built on top of platform messaging

40 40 WebSphere Platform Messaging in v6 Platform messaging fully integrated within WebSphere Application Server Integrated with WebSphere Security Common install process Fully Integrated with WebSphere System Management Admin Console provides MQ-Explorer type management All Java implementation within the server process - No external processes Co-exist with WebSphere MQ Performance monitoring, Trace and Problem Determination

41 41 Section Workload Management High Availability

42 42 Unified Clustering Management consistency for clustering of different resources Operational ease of use - The view and use of clusters will be administered in a unified and consistent manner for all protocols (HTTP, EJB, JMS, JCA, etc) Consistency - New WLM functions (weighted distribution, ewlm integration, SLA, hardware provisioning, etc.) are implemented once for all protocols High Availability - Makes WLM a highly available service which make cluster and routing information always available

43 TransportChannel Service WebContainer 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 WebContainer Channel Messaging HTTP Channel JFAP Channel TCP Channel Thread pools and other resources shared between WebContainer and Messaging 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 Requests Requests Requests Requests Requests Requests Requests Requests Requests Requests Requests Requests 43

44 44 Enhanced Data Replication Services (DRS) DRS is a mechanism for moving data among WebSphere processes for replication purposes DRS is used by multiple WebSphere components: New v6 New v6 HTTP Session memory-to-memory replication Dynamic cache replication Stateful session EJB state replication EJB Persistence manager Talks to WLM coordinator to align WLM routing with data location

45 45 Data Replication Service Enhancements Integrated with High Availability Manager Improved performance and scalability Provides a more optimized communication stack Allows for use of both unicast and multicast IP Improves in the range of 4x to 8x Improves high availability and failure recovery: Leverages the failure detection provided by high availability services Along with the WLM / Unified Clustering integration, this allows for "active failure recovery" For example, with HttpSession replication, if the affinity server for a HttpSession goes down, WLM can route to another server 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

46 46 Section Logging And Tracing

47 47 Java Logging API (JSR 047): Architecture Application Code WebSphere Code JRas Logger Handler output device Filter Filter Formatter

48 48 Log Detail Levels v6 Log Level v5 Log Level v5 Trace Level Description Off Off Turn off logging and tracing Fatal Severe Warning Warning Potential error or impending error. Audit Fatal Error Audit Task cannot continue and component cannot function. Task cannot continue but component can still function. Significant event affecting server state or resources Info Config Detail Fine Info Event General information outlining overall task progress Configuration change or status Info detailing subtask progress General trace + method entry / exit / return values Finer Entry / Exit Detailed trace Finest Debug Most detailed trace All All=enabled Log all events

49 49 Section Security

50 50 Security Enhancements Java Authorization Contract with Containers (JACC) 1.0 support Allows plug-in of your Authorization servers JACC compliant TAM (Tivoli Authorization Module) shipped with v6 Will continue to support the non-jacc native authorization (similar to v5) Security Attribute Propagation from WebSphere Application Server v5.1.1 Implements WS-Security 1.0

51 51 Section Miscellaneous

52 52 Miscellaneous Java Web Start Support for the client container 64-bit Itanium Support Better documented and richer API and SPI support Distributed PM Cache Hang Detection Null-column support for EJBs IPv6 Support Kerberos Support

53 Q & A