© 2002 IBM Corporation WebSphere Application Server Update and Futures A brief overview of...

© 2002 IBM Corporation

WebSphere Application Server Update and Futures

A brief overview of WebSphere Application Server 5.x and the roadmap for the future

© 2003 IBM Corporation2

Enterprise Service Bus

Enterprise applications Enterprise data

Data Access ServicesApplication Access Services

Services to Solve Complex Business Requirements

Monitoring Services

ProcessServices

Application Services

Information Services

Model, design, development, test tools

Common Runtime Infrastructure

Community Integration Services

User Interaction Services

IBM Business Integration Reference Architecture


WebSphere Application Server 5.1


WebSphere App Server - Version 5.1Key Features and Functions

• Third generation web services support Current standards/specification support

JSR101, JSR109, WSDL1.1, UDDI, 2.0, SOAP1.1, SAAJ 1.1 Security

WS-Security, XML Signature, XML Encryption Reliable transport

SOAP over JMS Interoperability

WS-I Basic Profile 1.0

• Additional platform support Complete support for zSeries with addition of Native Deployment Manager Linux on iSeries and pSeries Linux Client (United Linux 1.0) Solaris 9 Windows 2003 (.NET) server 32-bit Windows XP Professional (Client support) Windows XP (Dev and Test only)



• Expanded database connectivity Improved serviceability and debugging with DB2

DB2 Correlator and WebSphere Trace JDBC type 2 driver support for DB2 V8 Sybase 12.5 Oracle 9iR2 on Linux for zSeries Support for database stored procedures from methods on a CMP Bean

• Additional steps toward J2EE 1.4 SDK 1.4.1 support

• More functional replacement of Application Assembly Tool Assembly Toolkit component of the WebSphere Application Server Toolkit Eclipse based Improved useability

• Improved Performance Advanced performance advisors Web services, EJB, and JVM improvements


WebSphere Enterprise Business Integration Server Foundation - Version 5.1Key Features and Functions

• Enhanced Monitoring Request metrics admin functions

• Simplified fail-over support Back-up clusters

• First steps toward autonomic/grid support Dynamic workload management IBM Server Allocation for WebSphere Application Server

• Enhanced business process support Native Business Process Execution Language for Web Services (BPEL4WS) Support for FDML based business processes with support for optional migration Common Event Infrastructure to enable extended process monitoring WBI Modeler and WBI Monitor support

• Enterprise support on zOS


Technology for Developers (Released 12/03)

Early access to J2EE 1.4 functionality Exploring J2EE 1.4 Evaluating new J2EE 1.4 standards and specifications Planning exploitation of J2EE 1.4 Design and implementation prototyping

Available initially to WAS V5.1 customers

Windows 2000 support

WebSphere Application Server - Technology for Developers V6.0


WebSphere supports the Industry Trends

Application Server technologies

Messaging technologies

WebSphere Platform

Evolution and convergence of technology- Integration for on demand solutions- Service Oriented Architecture- Open Standards

Evolution and convergence of technology- Integration for on demand solutions- Service Oriented Architecture- Open Standards


WebSphere Application Server 6.0



• Continuing support of open standards J2EE 1.4, JDK 1.4

Continued enhancements for the latest web services standards EJB 2.1 Servlet 2.4 JSP 2.0 Java Authorization Contract for Containers J2EE Management 1.0 J2EE Deployment 1.1 J2EE Connectors 1.5Java Server FacesJSR 168 (Portlet)

• Extending support for the e-business on demand operating environment Enhanced autonomic/grid support

OGSA standards support Emerging OS support – 64 bit

AIX, HP-UX, Linux, Solaris


WebSphere Express

Full Programming Model– J2EE 1.4 Certified Runtime

– Web Services

– Programming Model Extensions Single Server Model (no clustering, no multi-server management) Includes Tooling (WSSD)


WebSphere for Network Deployment This is the clustered, multi-machine solution Deployment Manager

– Includes optional samples and applications that can be installed into servers in the cell

– Contains a set of production optimized templates for new server creation ND Runtime

– Optimized for production environments

– Only contains the content needed on the production machine

– No Samples– No Javadoc– No Admin Console

– Can be federated to the Deployment Mgr during product install

– Contains no default configuration (other than the definition of the node itself)


J2EE 1.4 Many changes, primarily focused on Web Services

Added several new APIs– JAX-RPC– SAAJ– WSEE (JSR 109)– JAXR– JMX– J2EE Management (JSR 77) & Deployment (JSR 88)– J2EE Authorization Contract (JSR 115)

Many updated APIs as well– EJB 2.1– Servlet 2.4– JSP 2.0

– Added Expression Language (JSP-EL)– .tag/.tagx File support– Improved XML Syntax (.jspx/.tagx)– API for EL

– JCA 1.5– In bound connector support

– JMS 1.1XSD-based Deployment Descriptors


Web Services - Other

JAX-RPC Multi-protocol support– Including EJB Bindings for higher QOS

Optimized Parsing Support HTTP 1.1 Support

– Performance boost with keep-alives Systems Management Improvements Server startup optimizations including deferral of processing WebSphere Rapid Deployment Support Extended SOAP Element support

– Lazy parsing

– Optimized retrieval APIs to leverage lazy parsing Improved Support for existing EJBs JService support Enterprise Service Bus support Custom Serialization

– Support for overriding the serialization technology stack of the middleware for element types


Programming Model Extensions

Due to WAS-E becoming WBI Foundation, most of the PMEs that were in WAS-E are now moving into WAS Express or WAS ND.

Moving to WAS Express– Last Participant Support– Internationalization Service – WorkArea Service – ActivitySession Service– Extended JTA Support– Startup Beans– Asynchronous Beans (now called WorkManager)– Scheduler Service (now called Timer Service)– Object Pools– Dynamic Query – WSGW Filter Programming Model (with migration support)– Distributed Map– Application Profiling

Moving to WAS ND– Back-up Cluster Support


Service Data Objects

The Problem

– Many different models and APIs for Data retrieval, Data representations, Meta-data retrieval, Meta-data representations, logic components

– No reasonable API available for “typed” XML data

– Lack of support for standard application patterns– Optimistic concurrency, pagination of large data-sets, etc.

Client

Data Access APIs

Data Access APIs

Data APIsData APIsData APIsData APIs

Meta-Data APIs

Data Access APIs

Meta-Data Access APIsClient Mediator

Data Access APIs

Data APIsData APIsData APIsData APIs

Meta-Data APIs

Meta-Data Access APIs


Service Data Objects

SDO DataObject with XSD & EMF provide a single, standard API (& implementation) for data & meta-data that we can use in place of many other APIs

Data is stored in a disconnected, source-independent format defined by the DataObject– DataObjects are stored in a graph called a DataGraph

– Provides both dynamic loosely-typed and static strongly-typed interfaces to the data

– Remembers change history Data Mediator Service is responsible for filling graph of DataObjects from data source,

updating data source from DataObject changes

Data model (DataObject)

Meta-data model (ECore)

PluggableData Mediator

Client

Data Access APIs

Data APIs

Meta-Data APIs

Meta-Data Access APIs


WAS V6 will provide a pure Java JMS 1.1 provider that can be installed as part of the base server installation (not a silent install of another product with its owns prereqs) & run completely inside the application server JVM.

Supports embedded Cloudscape for persistent messages, in additional to DB2, Oracle, etc. No separate messaging server process (all contained in the app server) Fully integrated with the application server (Systems Management, RAS, Security,

PMI, Threads, IOManager, etc) Each server can have its own, interconnected messaging engine Interoperable with MQ

MQ

Event Broker

JMS (MA88)

App Server1 process

9 messaging processes

app server securityapp server security

Java code C & Java

code

app server cluster model

R5

1 process ...Base Server with J2EE, Integrated

messaging

all Java code

integrated security

Cloudscape or other RDBMS for persistence support

R6

JMS Support


WebSphere Rapid Deployment - The Goal To simplify the development experience for WebSphere applications by:

Reducing the number of artifacts the developer must produce and maintain

Reducing the number of concepts and technologies the developer must understand

Supporting the development model and tools the developer desires to use

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 to install the application

Automating the process of activating incremental changes to an application on a running server


WRD Focus Areas Annotation-based Programming

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

Allow the developer to create and maintain a single artifact Change Triggered Processing

Drive processing operations based on the change detection of application artifacts

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 AutomationEnable automatic install of applications & modules onto 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)


WRD Annotations Example

package com.example.wrd;

/**

* @ejb.bean name="Hello" type="Stateless" view-type=remote jndi-name="HelloBean"

*/

public class Hello {

/**

* @ejb.interface-method view-type=remote

*/

public String hello(String name) {

return "Hello: " + name;

}

}


Java Server Faces Emerging Standards based Web Application Framework

Plug-and-play other JSF components easily

Targeted for Web Application Developers with little Java background

Competitive technology against Visual Studio .Net WebForms, & WebLogic Workbench

Based on MVC design pattern UI components are decoupled from its rendering

Allows for other technology (e.g. WML, etc) to be used

Event driven architecture

Server-Side Rich UI components respond to client events

Simplifies development of Web Applications

Eliminates much of the hand-coding involved with integrating back-end systems

WebSphere Studio 5.1.1 is the first IDE to support JSF based web application development


Summary

WebSphere is evolving rapidly to track the latest industry specifications & standards

J2EE 1.4

Web Services

WebSphere is adapting to the latest industry trendsMerging of Application Servers and Messaging Technology

© 2002 IBM Corporation WebSphere Application Server Update and Futures A brief overview of...

Documents

Transcript of © 2002 IBM Corporation WebSphere Application Server Update and Futures A brief overview of...