1. JBossWS beyond JAX-WS Heiko Braun Senior Software Engineer heiko.braun@jboss.com

2. Overview Common terminology –What are services? –What is SOA? Patterns of contemporary SOA –The 3000 feet view Challenges –For customers and vendors SOA as a technology branch –How does JBossWS fit into the picture? Recommendations / Next steps

3. What are services?

4. A simple service definition Service fulfills a purpose Basically it‘s a „worker“ Should achieve a specific goal The goal may be differently scoped: Retrieve data for a requestor or execute a business process This is referred to as „level of granularity“

5. Service is an abstract resource It performs a job A job is consists of several tasks A task corresponds to the physical assets of a service: object, components, legacy code, application API Each service has a name, contact information and associated policies For the requestor, the service is a black box

6. Purpose of a service Limited to a distinct purpose, function or concept Referred to as the bounds of a service A service may collaborate with other to perform it‘s job Can be used independently or in other collaborations

7. What is SOA?

8. SOA is an architectural concept Loosely coupling of a service and it‘s provider Concept not limited to the functional assets: Can network, platform or component It‘s an architectural strategy, enabled by products, not centered on them.

9. SOA is an environment An environment that allows services to be defined, developed and used by other services Allows business solution assembly Provides service discovery, policy definition and enforcement, QoS, TX compensation and usage metering

10. SOA is a journey The path to SOA varies based on the business and technology problems to be solved. Build on existing environments It‘s an incremental process

11. Patterns of contemporary SOA

12. Services are used for integration Bring back-end functionality to customer Offer access to legacy systems Most often leverages web services

13. Services extend applications Use services to add functionality to existing applications Services as the base for new applications Heterogenous landscape Coexistance of traditional and service oriented approaches

14. Services are combined with events „An event as something notable that happens inside or outside your business“ Event prompts and action, either human or automated Events trigger services Services may emit event themselves

15. Services are combined with events Example: Low stock event fired by an Order mgmt application

16. Services participate in business processes A service may invoke a business process Services may be included in or invoked by a business process The business process may change without touching the services

17. Services participate in business processes Example: Credit approval business process

18. Where is all of this heading? True SOA will combine services, events and business processes Customers will compose solutions that truely reflect their business demands Customers will mix and match concepts and technologies according to their business needs

19. The big picture Mix and match according to your business needs

20. Challenges for customers and vendors

21. SOA is not a product There is no „one size fit‘s all“ strategy An incremental investment with incremental gains Agility means applying solutions over time, growing with your business needs. Choose a technology branch not a single product

22. Transitioning costs Many technologies, concepts and vendors Almost no best practice knowledge Inital transition will cause a productivity decrease It takes time to build out a SOA environment and skills: Leverage existing tools and skills (i.e. JAX-WS, EE5)

23. The human factor Developers don‘t want to worry about the „framing and plumbing“ Developers rebel against restrictiveness of standards Service providers need to aim at abstracting complexity: JBossWS templates, architectural guidance Smart service stubs, „Service sense™“

24. SOA as a technology branch

25. Project awareness JBossWS as part of a technology branch Other members of that branch are ESB, Messaging, JBPM, JBossRules, EJB3, Seam To complete the „big pitcture“ these will be used in arbitrary combinations

26. Clear interconnection points The key is painless integration with likeminded technologies (ESB, Messaging, JBPM, JBossRules) Comprehensive development models that spans multiple technologies: i.e ESB and WS: service descriptions, policies, programming models Architectual guidance, tutorials

27. Ease of developement Strong client & server programming model: JAX-WS + EJB3 Smart service stubs: i.e. FastInfoSet, policy negotiation Environment aware (service publishing), extended annotations Architectural templates: Running as service gateway Integrated with ESB

28. Recommendations / Next steps

29. Bring the people together Create an umbrella project –Include ESB, WS, Messaging, Rules, JBPM, Seam –Project lead, road map, mailing list –Unified deliverables Will be the next big integration project similiar to AS –common technology (i.e. MC) –shared API, integration layers –plug and play capabililties Regular face 2 face meetings –create the sense of a common goal –sort things out, push things forward

30. Thanks