Service Component Architecture provides a single interface to many different kinds of services and access methods. If a service is (for example) a Web service, a BPEL process, a C++ class or a POJO, you write the same code to access all of them. If that service is accessed via SOAP, a messaging system such as JMS, or as a local object, you write the same code to access all of them. If that service requires authentication, encryption or some other policy, your code doesn't change. SCA gives your applications more flexibility than you've ever had before.

Service Data Objects provides a similarly elegant solution to data access. With SDO, you have a single interface to your data source, whether it's a relational database, an XML file, a Web service or something else (an LDAP directory, for example). SDO lets you use a single API, regardless of the underlying technology.

In these workshops, we'll look at the theory behind the technology, and we'll also use a sample application to illustrate the concepts behind SCA and SDO. The running code is based on the Apache Tuscany project, an open-source implementation of SCA and SDO. The underlying middleware is also open-source.

Attendees will leave with an understanding of what these new technologies are, how they work and how they can make your organization more nimble and responsive than ever.

Workshop Outline:

• A brief history of SOAs
• Why SCA makes life simpler
• SCA application diagrams
• Customer scenario
• Code and other details
• The SCA Composite Diagram Editor
• Service Data Objects
• Building data-driven user interfaces with XForms
• Exploring BPEL
• The big picture
• Resources & next steps