Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
JBoss / Red Hat: bridging the gap between web services technologies and real world needs
1. TITLE SLIDE: HEADLINE
Bridging the gap between web services
technologies and real world needs
Presenter
name Soldano
Alessio
Title, Red Hat
Web Services Lead
Date
September 16, 2011
1
2. From application requirements to WS offer
Application / design requirements: Web Services offer:
● Integration of heterogeneous ● Interoperability
systems
● Standards
● Vendor neutral communication
● Security
● Loosely coupled components
design ● Reliability
● QoS ● Transactions
● ... ● ...
2
3. Understanding webservices offer
● SOAP ● How do I use them?
● WSDL ● Which of them do I really need?
● UDDI ● Will my customers/partners
● WS-* support them?
● ...
? ... and also... (!)
● How to match these technologies
with my architecture design?
● What about SOA ?
● ... and REST?
● ... and clouds?
● ...
Web Services Standars Overview poster – 2007 innoQ
3
4. JBoss / Red Hat roles
Provide tools / products Consulting & support
Drive / participate in Iteroperability tests
standards definition
Participate in defining Community fostering
APIs for using standards and evangelization
4
6. Standards and specifications involvement
... and in the way vendors and implementors are to leverage standards...
●
JSR-224 JavaTM API for XML-based Web Services (JAX-WS) 2.0
●
JSR-181 Web Services Metadata for the JavaTM platform
● JSR-109 Enterprise Web Services
●
JSR-101 JavaTM APIs for XML-based RPC
● ...
6
7. Interoperability efforts
● Ensuring compliance against WS-I profiles
● Taking part in W3C standards' testing
● Joining thirdparty independent testing
groups
● Performing internal interop tests as part of
platforms productization
7
12. Examples & solutions
● JBoss ESB: Web Services functionalities as part of the ESB approach to enterprise
application integration
● SOAP Client - Wise
● SOAP Processor
● SOAP Proxy
● More loose coupling
● Modified contract
● Versioning
● Added features
● Complex routing
12
13. JBoss Community and JBoss Enterprise Middleware
● Focus “release early, ● Use case driven
release often” platforms that integrate
multiple projects into a
● 40+ projects with single distribution
different release
schedules, versions, ● Focus on long- term
dependencies, etc. stability, supportability,
& sustainability
● 100,000+ registered
developers ● Includes patches &
updates for up to 5
● Community support years
with forums, project
developers, wiki, issue ● Up to 24x7 enterprise
trackers, etc. support for mission
critical applications
13