This article will walk you through two samples of how to get started with SCA. First we'll write a small SCA application that uses the services provided by an SCA composite to do something useful. Having covered that, we'll show you how to take some code and package it as a composite so it can be used in SCA applications. »

With the SCA feature pack for IBM WebSphere, you can quickly start building component applications using the Service Component Architecture specification. Get your free feature pack today! »

IBM's new SCA Feature Pack for WebSphere Application Server lets you build applications using Service Component Architecture (SCA), a simple, powerful new standard for building composite applications. In this Webcast you'll learn about the SCA support provided by the feature pack and take a quick look at how to build more flexible applications in your Service-Oriented Architecture. »

Not sure if a JavaBean is fine-grained or coarse-grained? Don't know where SCA fits in on the granularity scale? Learn about different software technologies and how they fit into the SOA continum in this detailed article on software granularity. »

With more and more Java programmers utilizing the Java API for XML-Based Web Services (JAX-WS) it is a natural for composite application develoeprs to want to utilize this in a SCA model. Learn more about the current thinking behind SCA-enabling a JAX-WS runtime in this whitepaper. »

With the release of IBM WebSphere Integration Developer and IBM WebSphere Process Server, comes a new programming paradigm for building service-oriented architectures (SOA) called the Service Component Architecture (SCA), a new programming model designed specifically for building and assembling business solutions in an SOA, and targeted for integrating and composing services. »

This second in a series of articles describes how SCA components are implemented using the Java programming language, and how a component implementation can act as a client to other services. It explains the implementation of remotable and local services, and their configuration properties, as well as different ways to get access to a service--reference injection and module context. »

The Service Component Architecture (SCA) is an effort by a number of major software vendors to simplify building Service-Oriented Architectures (SOAs). The companies have founded the Open Service Oriented Architecture organization (osoa.org) to host the specifications for SCA. This article focuses on three aspects of an SOA--composition, assembly, and policy. »

Service Component Architecture (SCA) is a specification, or rather, a collection of specifications designed to describe a model for building applications and systems using a Service Oriented Architecture. SCA provides a model for how to create applications which are a composition of services and business functions. See how SCA can help you build systems that are easy to fit with existing infrastructure and extend in the future. »

This article from IBM developerWorks offers an overview of Java usage within the Service Component Architecture's (SCA) Plain Old Java Object (POJO) component and the data flow in and out of POJO components. You will see the effects of different invocation styles when they are used within a POJO component. »

The PHP SCA extension is a Web service implementation for PHP that allows developers to easily create SCA (Service Component Architecture) components through PHP annotations on a PHP class. Data can also be represented using Service Data Objects (SDO). This article shows developers how to create a Web service using the PHP SCA extension, and how the Web service data is represented using SDOs. »

Service Component Architecture (SCA) provides a state-of-the-art technique for building composite applications. Learn how this important technology delivers a modern, service-oriented approach to creating applicationsand how you'll benefit by incorporating these technologies as part of your development strategy. »

If you use the Spring Framework to construct your Java applications, there is now a component implementation specification for SCA on Spring. Find out how the Spring Framework can be used as a component implementation technology in SCA. »

If you've found the SCA service assembly model too complex, nesting assemblies inside other "higher-level" assemblies further promotes the reuse of an assembly. Discover the new SCA recursive assembly model to simplify SCA service assembly. »

Enterprise Java programmers can greatly benefit from building composite applications. In this whitepaper you'll learn about the current thinking behind what it will take to SCA-enable your Java EE applications to better fit into your SOA strategy. »

This first in a series of articles on Service Component Architecture (SCA) introduces SCA and shows how it can simplify the design and integration of business applications built using Service-Oriented Architecture (SOA). »

Learn how you can use HTTP bindings supported by IBM WebSphere Integration Developer Version 6.1 in many common real-life integration scenarios involving Service Component Architecture (SCA) applications. »

Executable WS-BPEL is a first class implementation language in SCA. It allows a component to be written in WS-BPEL and then deployed and assembled with other components written in WS-BPEL or written in other SCA implementation languages. WS-BPEL, much like SCA, is built around the Web Services concept of separating implementation code from service interfaces. SCA and WS-BPEL, although based on similar concepts of connecting services together, do so in different ways. Fortunately, it is easy to map between the two. »

In the enterprise application world, lightweight containers such as Spring and OSGi have recently gained in popularity amongst developers and Service Component Architecture (SCA) seems likely to become a significant standard for the development of enterprise applications using a Service Oriented Architecture (SOA). Learn why SCA, OSGi and Spring should be considered as complementary technologies. »

SCA encourages the organization of business application code based on components that implement business logic and offer their capabilities through service-oriented interfaces called services, which consume functions offered by other components through service-oriented interfaces, called references. Learn now SCA divides up the steps in building a service-oriented application into two major parts: implementation and assembly. »

The initial scope of SCA for PHP is to provide a means for a PHP programmer to write reusable components, which can be called either locally, or remotely, via Web services, with an identical interface and with a minimum of fuss. Learn how developing a Web service is made simple by automatically generating WSDL as needed from annotations within the component script, making deploying a Web service like deploying any other script. »