Web Services In WebSphere Application Server V 7.0

makeshiftluteSoftware and s/w Development

Jul 14, 2012 (5 years and 3 months ago)

455 views

Web Services In WebSphere
Application Server V 7.0
Henry (Hyen-Vui) Chung
WebSphereWeb Services Architect
Greg Truty
WebSphereWeb Services and REST Architect
1655
Objectives
•This session will provide the user with an
understanding of the capabilities (both
value and technology) delivered for Web
Services in WebSpherev7.0
Web Services in 7.0 Update
•Continue to Drive Standards Adoption
–Full Java EE 5 Web Services support
–Extend and Uplift Standards Support
•Enhance to support dynamic behavior
–Client/service provider policy matching.
•Continue to Simplify
–Additional profiles and tooling validation of profile
non-compliance
Web Services Evolution
Web Services Evolution
•WebSphere6.0
•JAX-RPC (JSR-101)
1.1
•JSR-109 1.1 –WSEE
1.1
•SAAJ 1.2
•WS-Security 1.0
•WS-I Basic Profile 1.1
•UDDI 3.0
•JAXR
•WS-TX AT Support
•WebSphere6.1
•WS-TX BusinessActivity
•WS-I BSP 1.0
•WS-Notification
•WS-Security
(performance)
•SOAP/JMS performance
•WS-RF (Resource
Framework)
•WS-Addressing (SOAP /
Core)
•WebSphereFeature Pack
for Web Services
•JAXB 2.0
•JAX-WS 2.0
•StAX1.1
•SAAJ 1.3
•SOAP 1.2
•MTOM / XOP
•WS-SecureConversation
•WS-Trust
•WS-ReliableMessaging
•WS-DistributedManagement
(WSDM)
WebSphere5.1
•JAX-RPC (JSR-101)
1.0
•JSR-109 1.0
•SAAJ 1.1
•WS-Security (draft)
•WS-I Basic Profile 1.0
•UDDI4J version 2.0
(client)
•Apache Soap 2.3
enhancements
•WebSphere7.0
•JAXB 2.1
•JAX-WS 2.1
•JSR 109 1.2
•OASIS WS-TX (AT/BA)
•OASIS WS-SX
–WS-SecureConversation
–WS-Trust
–WS-SecurityPolicy
•OASIS Kerberos Token
Profile
•W3C WS-Policy
•W3C WS-Addressing
Metadata
•WS-MetadataExchange
•WS-I BP 1.2 / 2.0 / RSP
Web Services in 7.0 Summary
Web Services in 7.0 Summary
Features
JCP-based programming model –JEE 1.5
•JSR 109 1.2
•JAX-WS 2.1
•JAXB 2.1
•EJB 3.0
•StAX1.1
•SAAJ 1.3
Complete WS-* Roadmap (Wire format)
•W3C WS-Policy
•WS-MetadataExchange
•Updated OASIS versions of:
–WS-AT / WS-BA (WS-TX)
–WS-SecureConversation / WS-Trust / WS-SecurityPolicy(WS-SX)
•OASIS Kerberos Token Profile
•WS-Addressing Metadata
•WS-I Basic Profile 1.2 and 2.0, Reliable Secure Profile 1.0
*
Policy matching and intersection
Benefits
Maturity and Integration of multiple
technology stacks
Standardized (and portable) application
programming model for WS-Addressing
•WSRF, WS-Notification and WSDM are among
expanding group of standards to define
application-level protocols leveraging WS-
Addressing.
Fill out the WS-* roadmap for delivery of
functionality across all QoS(Quality of
Service) required for enterprise SOA.
Dynamic selection of endpoints QoSbased
on configured policy
JEE 5 Standards Support and
JEE 5 Standards Support and
Update
Update
Java EE 5 Web Services: JAX-WS
•Annotation-based Programming model
•Java <-> WSDL mapping
–Top down or bottom up
–Development time tools
•Progressive disclosure for complex
behaviors
–Asynchronous
–Extendable renderings
Master Rule:
-Make the Typical Case
Really Easy.
Really Easy.
-Make the Atypical Case
Possible
Possible
Java EE 5 Web Services: JAX-WS
Command-line tooling
–JAXB 2.1 XSD->Java generation (xjc)
–JAX-WS 2.1 WSDL->Java (wsimport)
–JAX-WS 2.1 Java->WSDL (wsgen)
WSDL
<service>
<binding>
<portType>
<message>
WSD
L
<service>
<binding>
<portType>
<message>
Service
(factory)
Service
(factory)
SEI
SEI
Java
Int
r
insics
Java
Int
r
insics
JAX-B
Classes
JAX-B
Classes
Creates
Uses
POJO
Implementation
POJO
Implementation
I
m
plem
ented
by
Uses
WSImport
WSGen
RAD tooling

GUI Wizards to d
r
ive c
o
mma
n
d-li
n
e
too
lin
g

Annotati
on vali
dation

WSDL
/ XS
D validat
ors

JA
X-WS v
a
lid
at
o
r
s
What JAX-WS Means for Developers
1.1 Code
public interface StockQuoteextends Remote {
public float getQuote(Stringsym) throws
RemoteException;
}
public class QuoteBeanimplements
SessionBean{
public float getQuote(Stringsym) { …}
public void ejbActivate() { }
public void ejbPassivate() { }
}
On the client
Service svc =
Context.lookup(“java:comp/env/service/StockQuot
eService”);
StockQuotesq =
(StockQuote)svc.getPort(StockQuote.class);
float price = sq.getQuote(“IBM”);
2.0 Code
@WebService
public interface StockQuote{
public float getQuote(Stringsym);
}
@Stateless
public class QuoteBeanimplements
StockQuote{
public float getQuote(Stringsym) { ... }
}
On the client
@WebServiceRef(StockQuote.class)
private StockQuotesq;
float price = sq.getQuote(“IBM”);
JAX
JAX
-
-
WS 2.1 Upgrade
WS 2.1 Upgrade
•Overall focus is based on WS-Addressing and maturing the
technology
•Customer Pain Points Addressed
–WebSpherehas IBMAPI/SPIsfor programming to WS-Addressing since
WebSphere6.1
–Answer: Standard JCP-based APIs are introduced to allow users to code WS-
Addressing headers directly (via an Addressing Feature).
•Maturing of technology
–Feature Extensibility
Enable/Disable MTOM feature
Limits on when to enable MTOM
Respect Bindings Feature
Requires respecting all WSDL Binding information (including
extensions)
•@WebService
@MTOM(enabled="true", threshold="2000")
public class MyServiceImpl{
...
}
JAXB 2.1 Upgrade
JAXB 2.1 Upgrade
•Overall focus represents features typical with maturing the
technology
•Customer Pain Points Addressed
–Make type substitution easier
–Answer: Introduce @XMLSeeAlsoto help define the subtypes
–Customers desired to develop stand-alone schemas as separate modules
–Answer: Provide annotations to define existing generated classesand schema
locations
–Customer doing bottom-up mapping don’t necessarily want to expose all
metadata about the class
–Answer: Provide XMLTransientannotation to ignore the mapped class
–JAXB Global Binding files had hard-coded dependency to the XSDsthey were
modifying
–Answer: Remove the hard-coded reference (and allow them to be re-used)
JSR 109 1.2 Upgrade
JSR 109 1.2 Upgrade
•Focus is to upgrade to support JAX-WS along with JAX-RPC
•Customer Benefit is consistency with other declarative models.
–Declarative model to define and/or override JAX-WS annotations
Examples include:
Handlers
MTOM enablement
Java EE environment entries
EJB 3.0 Support for Web Services
EJB 3.0 Support for Web Services
•Integration with the rest of Java EE native capabilities
•Customer Pain Points Addressed
–The WebSphereFeature Pack for Web Services only addressed POJOs
deployed within the web container for hosting services.
–Answer: Extend current JAX-WS implementations providing EJB-specific
capabilities:
Method-level authorization
Transactionalityof individual requests
Compensation routines for WS-Business Activity
–Answer: Allow for other transports to be introduced
SOAP / JMS leverages EJB-based implementations
WS
WS
-
-
* Standards Support and
* Standards Support and
Update
Update
Complete the Web Service Standards Roadmap
Complete the Web Service Standards Roadmap
Web Services Standard
Introduced inStandards Completionv7.0
WS-Atomic Transaction6.0OASIS approved –6/2007

WS-BusinessActivity6.1OASIS approved –6/2007

WS-SecureConversation6.1 WS FePOASIS approved –3/2007

WS-Trust6.1 WS FePOASIS approved –3/2007

WS-SecurityPolicyOASIS approved -7/2007

Kerberos Token ProfileOASIS approved –2/2006

WS-PolicyW3C recommend –9/2007

WS-Addressing MetadataW3C recommend –9/2007

WS-MetadataExchange

WS-DistributedManagement1.16.1 WS FePOASIS approved –8/2006

WS-I Basic Profile 1.2Targeted 2H of 2009

WS-I Basic Profile 2.0Targeted 2H of 2009

WS-I Basic Profile RSPTargeted 2H of 2009

W3C WS
W3C WS
-
-
Policy Support
Policy Support
•Focus of support is enable movement towards:
–Declaration of service constraints
–Dynamic configuration of runtime
•Customer Pain Points Addressed
–Static Configuration of Services is time-consuming and costly
–Answer: Support WS-Policy and WS-MetadataExchange(and varying domain-
specific policies such as WS-SecurityPolicy, WS-ReliableMessagingPolicy
•Administratively define which attached policy should be applied for policy
intersection
–Capabilities supported include
Expose WebSpherePolicySetin interoperable WS-Policy form, in context of provider
WSDL
Provider WSDL available via:
HTTP Get of provider-url?wsdl
WS-Metadata GetMetadatarequest
Client retrieval of Policy and Dynamic calculation of Policy Usage
More WS-Policy later…
•But first…
Policy Sets
•Focus is to simplify web services configuration by allowing qualities of services to
be reused (and managed as a single configuration)
•Customer Pain Points Addressed
–JAX-RPC security configuration is based on deployment descriptors and bindings
•Not shareable, no reuse (per Web Service port)
•Difficult to managed
–Scattered in multiple places
•Hard to manage the interdependency relationship
–Change of deployment descriptor requires redeploy of application
•e.g.,SecurityConstraints –changing what to sign or encrypt
–Scripting support is incomplete
•Policy Sets:
–Introduced in WS FePon v6.1
–Managed via the WebSphere Admin Console
–Attached to service components (client / provider) external fromthe application
–Grouping of policies of quality of service into a “unit”
Policy Set Collection View
Services

Policy sets

Application policy sets
Shipped def
ault and not
editable
User defi
ned
Policy Set Detail View
Services Providers
Service Provider Policy Sets and Bindings Panel
WS-Policy (continued)
•Back to WS-Policy…
Configure Exposing Server
Configure Exposing Server


Policy
Policy


Options for Exposing Server
Options for Exposing Server


Policy
Policy


Applying Policy to a Client
Applying Policy to a Client
•No policy
•Client policy
–Policy calculated based on staticclient policy configuration (i.e. policy set). This is
implicitly supported in the Web Services Feature Pack.
•Provider Policy –New
–Policy calculated based on dynamicallyacquired provider policy. Administrator
says “be guided by the provider’s policy requirements”
•Client and Provider Policy –New
–Policy calculated based on dynamically acquired provider policy andstatic client
policy configuration. Administrator says “be guided by the provider’s policy
requirements…but I also want to statically configure some restrictions to what’s
acceptable”
Configure Usage of Client
Configure Usage of Client


Policy
Policy


Client WS
Client WS
-
-
Policy / WS
Policy / WS
-
-
MEX Settings
MEX Settings
•Selections restricted to
“None”(the default) and
“Provider Only”since
there is no client PS
•Disabled unless the
option to use the
provider policy is
selected
Example Client using Provider-Only Policy
HTTP GET
or
WS-MetadataExchange GetMetadata request
WSDL document containing
configuration in ws-policy
format
Dynamic
Configuration
Web service request
Client
WebSphere
or
Non-WebSphere
Service
Po
licy Set or
Configuration
Policy Set Binding
•Support for WS-Notification 1.3
–7.0 implements the final versions of the specs
•WS-BaseNotificationsupport for XPath1.0 selectors
–A subscribing application can filter the set of messages it receives to those that
match a specific property
–Applications do not need to do their own filtering
–The stream of messages for a given topic can be filtered by a Boolean
expression evaluated over the (XML message) content of the message body.
•WS-Notification supports our JAX-WS-based infrastructure
–In 6.1 WS-N uses the our JAX-RPC-based infrastructure
–In 7.0 WS-N has been updated to also support JAX-WS, so it’s composablewith
WS-RM
•Ability to configure and utilize Policy Sets in 7.0
–Improves qualities of service with WS-Notification
WS
WS
-
-
Notification
Notification
WS
WS
-
-
Notification and Policy Sets
Notification and Policy Sets
•Allow Policy Sets to compose with WS-Notification
–Value obtained is reused of quality of service
WS-Reliable Messaging
Thin
client
Client
container
Web
container
EJB
container
Additional comments
Unmanaged Non-persistent non-transactional and provides resend for network failure

-provider not supported in
cluster or zOS
-lost messages if process fails
Managed Non-persistent transactional, state managed by messaging engine and protects
against network loss

-lost messages if messaging
engine fails (or
stopped/restarted)
Managed Persistentrecoverable, transactional, state managed by messaging engine
and protects against network loss, server, and messaging engine
failure

-Used in asynchronous
communication only
Sender
App
RM
Message
Store
Provider
App
SOAP / WS-
RM flows
Support for
Feb 2005 WS-RM 1.0
OASIS WS-RX WS-RM1.1
Message
Store
RM
•7.0 specific enhancements include improved performance and recovery
•Automatic recovery for 1-way requests on server start up
•Send on execution thread
•For unmanaged endpoints, this allows for standard programming model usage (no WebSphere-specific API usage)
WS-Reliable Messaging Topologies
•Unmanaged
Non-Persistent
RM
In-Memory
Message Store
Provider
App
SOAP
WS-RM
flows
RM
Provider
App
SOAP
WS-RM
flows
Messaging
Engine
Data
Store
RM
Provider
App
SOAP
WS-RM
flows
Messaging
Engine
Data
Store
Messaging
Engine
Messaging
Engine
•Managed
Non-Persistent
•Managed
Persistent
Secure Conversation (WS-SC) and
WS-Trust
•Secure Conversation
–Issue, Renew and Cancel WS-Trust protocol
–Establishing Security Context Token between requestor and provider
–Derived Key from SCT can be used to sign and encrypt the message
•WS-Trust
–Embedded within Application Server
–Issue, Renew, Validate and Cancel
–Leveraging Policy Set for trust policy
•Securing reliable message exchange (WS-RM)
–Forms basis of WS-I Reliable Secure Profile
SOAP /
WS-Trust
Flows
WS-Security
Runtime
Web Services
Client
JAX-WS
Client
WS-Security
Runtime
Web Services
Server
JAX-WS
Impl.
WS-Trust
Module
Secure Conversation (WS-SC) and
WS-Trust 7.0 Enhancement
•Focus is on keeping pace with Standards for Interoperability
•Customer Benefit is to allow for increased interoperability withother
vendors using the latest standards
•Capabilities include:
–OASIS WS-Trust 1.3 support
Addresses obtaining Authentication tokens such as SecureConversation, SAML, etc…
OASIS submission & recommendation supported
–WS-SecurityPolicy
Exposing Security Policy 1.2 for MEX and ?WSDL
Forms the basis of declarative model for Security (Transport andMessage Level)
Assertion to specify caller identity (which token should be usedfor the caller)
LTPA v2 (TFIM integration –more secure)
–WS-SecureConversation
OASIS WS-SecureConversation1.3 support
OASIS submission and recommendation supported
Allows Message Level Security processing to use symmetric cryptography (faster!)
Improved clustering support
Kerberos Token Profile
Kerberos Token Profile
•Focus is to support multiple scenarios using a Kerberos Token for
WS-Security processing
•Customer Business value is to provide Single Sign-on (especially
when using Microsoft Infrastructure such as WSE and WCF)
•Support of OASIS WS-SecurityKerberos1.1 Token Profile
–AP_REQ and GSS token
•Sign and encrypt SOAP Message with session key as secret key
•Improves Performance and Security
•Delegation
–Web Service Programming model
•JAX-WS (Primary focus and IBM Strategic direction)
•JAX-RPC (Usage of Custom Token support in JAX-RPC)
•Integrates with Multiple Security Domain (MSD) in WebSphere
Kerberos at High Level
Kerberos at High Level
Kerberos Realm
Active
Directory
Microsoft KDC
(Key Distribution
Center)
Policy
Krb5
cache
Request/Response
Keytab
Keytab
DB2
•RACF
Message
signed/encrypted by
Kerberos token
JGSS
Kerberos token
WS-Security
runtime
Policy
WS-Security
runtime
WebSphere
Security
Subject
JGSS
WebSphere
Domain B
WS-Security
runtime
WebSphere
Security
Policy
WebSphere
Domain A
•Benefits include:
–Consistency with Kerberos support in base security
–Interoperability with Microsoft .Net and other products
–Integration with RACF
OASIS WS
OASIS WS
-
-
Transaction
Transaction
•Focus is on keeping pace with Standards for Interoperability
•Customer Benefit is to allow for increased interoperability withother
vendors using the latest standards
•OASIS WS-TX 1.1 upgrade
–WS-TX 1.1 only supported for JAX-WS-based applications
–WS-TX 1.0 supported for JAX-RPC and JAX-WS-based applications
•Transaction-specific WS-Policy assertions
–Require, Supports, Never
–WS-AtomicTransaction(WS-AT), WS-BusinessActivity(WS-BA)
WS
WS
-
-
Transaction
Transaction
•Choose between supporting WS-Transaction 1.0 or 1.1 (as default)
•Interoperability is maintained with WebSphere6.x using WS-TX 1.0
–(default as shipped)
WS
WS
-
-
Transaction Policy Configuration
Transaction Policy Configuration
•<wsdl:definitionstargetNamespace="bank.example.com"
xmlns:tns="bank.example.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
•xmlns:wsat11="http://docs.oasis-open.org/ws-tx/wsat/2006/06"
•xmlns:wsat10="http://schemas.xmlsoap.org/ws/2004/10/wsat">
•<wsp:Policywsu:Id="ATPolicy">
•<wsp:ExactlyOne>
•<wsat11:ATAssertion />
•<wsat10:ATAssertion />
•</wsp:ExactlyOne/>
•</wsp:Policy>
•<!--omitted elements -->
•<wsdl:bindingname="BankBinding" type="tns:BankPortType" >
WS
WS
-
-
Addressing Metadata
Addressing Metadata
•Focus is to complete the WS-Addressing standards
•Customer Benefit is declarative way to describe additional
constraints on a service
•W3C WS-Addressing Metadata
–Rounds out 3
rd
WS-Addressing Specification
–Defines WS-Addressing Policy Assertions
Defines Mandatory or Supports
Defines Synchronous or Asynchronous behavior
WS
WS
-
-
Addressing Policy Configuration
Addressing Policy Configuration
•<wsdl:definitionstargetNamespace="bank.example.com"
xmlns:tns="bank.example.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy”
xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-
utility-1.0.xsd" >
•<wsp:Policywsu:Id="WSAPolicy">
•<wsam:Addressingwsp:Optional=”true”>
•<wsp:Policy>
•<wsp:ExactlyOne>
•<wsam:AnonymousResponseswsp:Optional=”true”/>
•<wsam:NonAnonymousResponses/>
•</wsp:ExactlyOne>
•</wsp:Policy>
•</wsam:Addressing>
•</wsp:Policy>
•<!--omitted elements -->
•<wsdl:bindingname="BankBinding" type="tns:BankPortType" >
•<wsp:PolicyReferenceURI="#WSAPolicy" wsdl:required="true" />
SOAP/JMS support
SOAP/JMS support
•Focus is to add additional reliable transport support
•Customer benefit allows for
–Reusing existing skill for to achieve “reliable messaging”
–Leveraging JAXB for full mapping
–Standardized SOAP/JMS specification
submitted to W3C
Continue to Simplify
Continue to Simplify
Policy Set Enhancements
Policy Set Enhancements
•Focus on maturity and continued ease-of-use
•Customer Benefits include
–Extending for WS-Notification Service / Client endpoints
–Multiple General cell-level bindings (allows greater flexibility and reuse)
–Import / Export (both policy set and bindings)
Policy Set Import and Export
Policy Set Import and Export
•Support to move Policy Sets from
Development -> Test -> Production
Policy Set Bindings
Policy Set Bindings
•Flexibility achieved through
–Multiple General cell-level bindings
–Import/export of bindings
Integration with Multiple Security Domain
Integration with Multiple Security Domain
Admin Console Enhancements
Admin Console Enhancements
•Focus is to continue to simplify and provide maturity
•Customer value includes
–Start and Stop listening endpoints(e.g. to control throughput into the system)
–Migration/install mixed cell
–Consumabilityre-factoring updates of names (to provide simplicity and consistency)
Web Services Performance Through the Years
152
304
486
676
945
1133
1618
1873
1.0
2.0
3.2
6.2
7.5
12.3
4.2
10.6
0
200
400
600
800
1000
1200
1400
1600
1800
2000
2001 - WAS4.02002 - WAS 5.0
TP
2003 - WAS
5.0.2
2004 - WAS 5.12005 - WAS
6.0.2
2006 - WAS 6.12007 - WS-FEP2008 - WAS 7.0
Throughput (req/sec)
0.0
2.0
4.0
6.0
8.0
10.0
12.0
14.0
Web Services X Factor Improvements
•Web Services Performance
has been consistently
improved with each release
•Highlights
–WS-FP
•JAX-WS with JAXB, StAX
parser
–7.0
•JAX-WS with tighter JAXB
integration
–Compared to 6.1 JAX-RPC,
7.0 JAX-WS is up to 3.2
times faster*
–Compared to Web Services
Feature Pack JAX-WS, 7.0
JAX-WS is up to 40% faster*
* for some message sizes
** Based on IBM metrics, 2008.
7.0 Performance Improvements
7.0 Performance Improvements
•Techniques include building up “golden paths”
•Customer benefit is increased performance and reduced instructions
•Areas of focus include:
–JAXB Fastpath
–MTOM attachments
–Reliable Messaging (in-memory persistent)
–WS-Security Processing improvements
•Focus on interoperability involves multiple approaches
–WS-I Profiles
–Common Component within IBM
–Apache Componentry
•Axis2 and Sandesha2
–Web Services Test Forum (WSTF)
Interoperability
Interoperability
Web Services Test Forum (WSTF)
Web Services Test Forum (WSTF)
•Objective
“Provide an environment in which members of the Web Services community can
develop and test interoperability scenarios that go beyond the specification
testing done elsewhere, which is typically limited to a single Web Services
specification.”
•All activities are private (unless voted to turn public)
•Participation is open to any individual/company
•Anyone can create a scenario
•Long-lived endpoints are encouraged
•Customer benefits include earlier testing (by various vendors) to
showcase and build best practices and resolve issues
New R.A.D. v7.5 Web Services Functionality
New R.A.D. v7.5 Web Services Functionality
-
-
Common to v6.1 WS
Common to v6.1 WS
FeP
FeP
and v7
and v7
•Functionality
–New Services views to replace JSR-109 and JAX-WS nodes
•View Web services and clients by project and by workspace
–Annotations Autocompletions
•Templatizedwith implied run time attributes
•JAX-WS not needed on the project classpath
–Quickfixes
•Convert a plain Java project into a dynamic Web project to host a Web service
•JAX-WS Annotations Processor problems (e.g. Auto-implement SEI methods)
–Web Service Wizards
•Customized Schema Library to improve reuse of schema code
•Portable JAX-WS clients (embedded WSDLswith relative URL references)
–Qualities of Service
•Consolidated preferences for Policy Sets and WS-I profile compliance
•Extended WSDL validation for WebSpherespecific issues
–Ant tasks
•wsant.bat(.sh) script improvements. No more copying/editing required
New R.A.D. v7.5 Web Services Functionality
New R.A.D. v7.5 Web Services Functionality
-
-
WebSphere
WebSphere
v7
v7
•Functionality
–JSR-109 1.2 support
Generation of Deployment Descriptors from the Services views
New webservices.xmland client side deployment descriptor editors
–Web Service Wizards
Bottom up and Top Down JAX-RPC EJB3 support
Top down JAX-WS EJB3 support
Standardized and IBM proprietary SOAP/JMS support
JAX-WS 2.1 code generation option
–Qualities of Service
Integration of Named Bindings into preferences
WS-MEX support for WS-Policy
Kerberos Token Support for JAX-RPC and JAX-WS
Summary
Summary
•WebSphere v7.0 Web Services delivers
–The latest level of W3C and OASIS standards
–An initial delivery of WS-Policy Support
–The latest JAX-WS and JAXB updates for
Java EE 5 (including JSR 109 support)
–Improved performance and consumability
We love your Feedback!
•Don’t forget to submit your Impact session and
speaker feedback! Your feedback is very
important to us, we use it to improve our
conference for you next year.
•Go to
www.impact09guide.com
on a smartphone
device or a loaner device
•From the Impact 2009 Online Conference Guide;
–Select Agenda
–Navigate to the session you want to give feedback on
–Select the session or speaker feedback links
–Submit your feedback
©IBM Corporation 2009. All Rights Reserved.
The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for
informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While
efforts were made to verify the completeness and accuracy of theinformation contained in this presentation, it is provided AS IS without warranty of any
kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other
materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its
suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.
References in this presentation to IBM products, programs, or services do not imply that they will be available in all countriesin which IBM operates.
Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or
other factors, and are not intended to be a commitment to futureproduct or feature availability in any way. Nothing contained in these materials is
intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specificsales, revenue growth or other
results.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or
performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in
the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an
individual user will achieve results similar to those stated here.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved.
Actual environmental costs and performance characteristics may vary by customer.
The following are trademarks of the International Business Machines Corporation in the United States and/or other countries:
ibm.com/legal/copytrade.shtmlAIX, CICS, CICSPlex, DataPower, DB2, DB2 Universal Database, i5/OS, IBM, the IBM logo, IMS/ESA, Power Systems, Lotus,
OMEGAMON, OS/390, Parallel Sysplex, pureXML, Rational, Redbooks, Sametime, SMART SOA, System z , Tivoli, WebSphere, and z/OS.
A current list of IBM trademarks is available on the Web at “Copyright and trademark information”at ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United
States, and/or other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government
Commerce
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in theUnited States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation inthe United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and
Trademark Office
Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of LinusTorvaldsin the United States, other countries, or both.