TITLE SLIDE: HEADLINE    Bridging the gap between web services    technologies and real world needs      Presenter      na...
From application requirements to WS offerApplication / design requirements:     Web Services offer:    ●   Integration of ...
Understanding webservices offer      ●   SOAP                                           ●   How do I use them?      ●   WS...
JBoss / Red Hat roles                             Provide tools / products   Consulting & support    Drive / participate i...
Standards and specifications involvement                    ...taking part in defining the webservices world...      ●   W...
Standards and specifications involvement    ... and in the way vendors and implementors are to leverage standards...      ...
Interoperability efforts    ●   Ensuring compliance against WS-I profiles    ●   Taking part in W3C standards testing    ●...
JBoss webservices projects    ●   JBossWS: JSR-224 (JAX-WS), JSR-109, JSR-181, JSR-101, WS-        Addressing, WS-Reliable...
Integration for solving real world issues    ●   JBoss Application Server as target container    ●   Thirdparty OS project...
Tools ●   Tools for code-first / contract-fist development       ●   IDE       ●   Command line       ●   Maven plugins   ...
Examples & solutions ●   WS-Security EJB3 endpoint w/ authentication & authorization     based on policy relying on userna...
Examples & solutions ●   JBoss ESB: Web Services functionalities as part of the ESB approach to enterprise     application...
JBoss Community and JBoss Enterprise Middleware●    Focus “release early,         ●   Use case driven     release often”  ...
Upcoming SlideShare
Loading in …5
×

JBoss / Red Hat: bridging the gap between web services technologies and real world needs

1,895 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,895
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
27
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

JBoss / Red Hat: bridging the gap between web services technologies and real world needs

  1. 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, 20111
  2. 2. From application requirements to WS offerApplication / design requirements: Web Services offer: ● Integration of heterogeneous ● Interoperability systems ● Standards ● Vendor neutral communication ● Security ● Loosely coupled components design ● Reliability ● QoS ● Transactions ● ... ● ...2
  3. 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. 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 evangelization4
  5. 5. Standards and specifications involvement ...taking part in defining the webservices world... ● WS-RA ● WS-TX ● WS-Transfer ● WS-Coordination ● WS-Fragment ● WS-AtomicTransaction ● WS-Eventing ● WS-BusinessActivity ● WS-Enumeration ● WS-RX ● WS-MetadataExchange ● WS-ReliableMessaging ● WS-Addressing ● WS-SX ● WS-Policy ● WS-Trust ● ... ● WS-SecureConversation ● WS-SecurityPolicy ● SAML5 ● ...
  6. 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. 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 productization7
  8. 8. JBoss webservices projects ● JBossWS: JSR-224 (JAX-WS), JSR-109, JSR-181, JSR-101, WS- Addressing, WS-ReliableMessaging, WS-Security, WS-Policy* ● RestEASY: JSR-311 (JAX-RS) JBossWS RESTEasy JBossTools SwitchYard RiftSaw Savara PicketLink JBoss Transactions ... WS-Trust, WS-TX Design validation/verification: SAML tooling WS-CDL, WS-BPEL Develop, deploy, manage BPEL processes orchestration: IDE tooling including WS service-oriented applications: WS-BPEL 2.0 features ESB8
  9. 9. Integration for solving real world issues ● JBoss Application Server as target container ● Thirdparty OS projects integration ● Apache CXF ● Apache jUDDI ● Apache Camel ● ... ● Added value ● Tooling ● New features ● Simplified APIs for non-standard stuff ● Pre-built solutions for common needs ● WS-Security UsernameToken Profile JAAS integration ● STS provider ● ...9
  10. 10. Tools ● Tools for code-first / contract-fist development ● IDE ● Command line ● Maven plugins ● Ant tasks ● Management10
  11. 11. Examples & solutions ● WS-Security EJB3 endpoint w/ authentication & authorization based on policy relying on username token profile... package org.jboss.test.ws.jaxws.samples.wsse.policy.jaas; import javax.*; import org.apache.cxf.interceptor.InInterceptors; import org.jboss.ws.api.annotation.EndpointConfig; @WebService ( portName = "SecurityServicePort", serviceName = "SecurityService", wsdlLocation = "META-INF/wsdl/SecurityService.wsdl", targetNamespace = "http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy", endpointInterface = "org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.ServiceIface") @Stateless(name=”EjbEndpoint”) @EndpointConfig(configFile = "META-INF/jaxws-ep-cfg.xml", configName = "Custom wsse ep") @InInterceptors(interceptors = { "org.jboss.wsf.stack.cxf.security.authentication.SubjectCreatingPolicyInterceptor"}) @SecurityDomain(“JBossWS”) public class ServiceImpl { @RolesAllowed(“friend”) public String sayHello() { return "Secure Hello World!"; } }11
  12. 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 routing12
  13. 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 applications13

×