Welcome!

SOA & WOA Authors: Carmen Gonzalez, Lori MacVittie, Liz McMillan, Pat Romanski, Natalie Lerner

Related Topics: Java

Java: Article

Java Feature — What Is SCA?

A simple model for creating service-oriented applications

Service Component Architecture (SCA) is a simple model for creating service-oriented applications. This article highlights the benefits of SCA and introduces SCA concepts by walking through an example. The example has been developed using the Apache Tuscany open source project (http://incubator.apache.org/tuscany/). All the sample code in this article is licensed under the Apache License 2.0 (www.apache.org/licenses/LICENSE-2.0) and the resources with the article gives a link to the sample files. Both the Apache Tuscany and PHP SCA_SDO (http://pecl.php.net/package/sca_sdo) projects provide a free service oriented infrastructure for creating, packaging, deploying, and managing applications built with the SCA programming model.

The SCA programming model itself is described by a set of specifications that are being developed by many vendors and individuals contributing to the Open Service Oriented Architecture collaboration (www.osoa.org).

SCA
Service Oriented Architecture (SOA) is an architectural approach driven by the need to overcome the challenges of tightly coupled and department-specific applications. SOA promises benefits such as improved business agility, improved flexibility, cost reduction, and the easy sharing of information in heterogeneous and distributed environments.

SOA provides a blueprint but implementing an SOA remains a challenge. The choice of technology available to the implementer is bewildering and skills in a variety of technologies are required to be successful. Service Component Architecture (SCA) addresses the complexity of developing an SOA solution through its simple model for creating service-oriented applications for the whole enterprise - from the client to the back-end. Businesses using SCA can benefit from the following:

  • Rapid development and increase in productivity: SCA views an application as a set of connected components. It provides a simple language-neutral component model for implementing new components or reusing existing components. A component can be implemented in any language supported by an SCA runtime. SCA promotes true loose coupling by separating component implementation from the details of component composition. This bottom-up development style allows the developer to focus on developing business-related code with-out worrying about how this will fit into the overall solution.
  • Higher organizational agility and flexibility: SCA also supports a top-down development approach of creating business solutions with its flexible service assembly model. SCA components can be wired together in a composition. A component can be replaced with another component in the composition as long as they share the same contract. The composition can be adjusted to IT infrastructure requirements such as service connections, transport protocols, transactions, security, and reliable messaging. Selectable transport bindings make solutions available in the widest possible set of deployment situations.
  • Return on Investment through reuse: The SCA component model makes it very easy to leverage investments made in existing applications and services. Its standardized approach to encapsulation and interface abstraction enables service reuse through wiring and rewiring to construct new applications. SCA itself is technology-neutral and isn't intended to replace existing technology. It simply provides a component composition model that describes how new and existing services are assembled.
Figure 1 is taken from the SCA Assembly Model specification (www.osoa.org/display/Main/Service+Component+Architecture+Specifications) and shows the main artifacts of SCA.

The dark blue boxes (Component A and Component B) show components. Components are at the heart of SCA as they encapsulate business logic. Depending on runtime support, components implemented using any programming technique can be included. For example, Apache Tuscany currently supports the Java language, JavaScript, Ruby, Python, and C++ component types and provides an extension API for building new extensions.

SCA components can have properties (the yellow boxes shown at the top of components A and B). Properties control the behavior of the component and can be changed at deployment time. For example, a stock quote application might have a property that indicates the currency that stock values will be quoted in.

SCA components describe the interfaces that they expose for other components to call, shown as the green arrows on the left-hand side of the component boxes and called "services" in SCA. Components also describe the interfaces of other components that they expect to call as the business logic executes, shown as the pink arrows on the right-hand side of the component boxes and called "references" in SCA. These exposed services and references can be "wired" together to describe a working system.

The diagram shows two components, A and B, assembled together within the bounds of a larger "composite," called composite A. The SCA composite describes a collection of wired components and, as you can see, the composite also echoes those services and references that must be exposed beyond the bounds of the composite. Wiring together components within a composite is akin to building a tightly coupled application that may run in a single process. Wiring together the services and references exposed by a composite represents a more loosely coupled system where each composite may run in a separate process or processor and is connected over a network with various protocol/transport bindings. This way SCA provides a consistent model for describing standalone and distributed applications.

An Example Scenario
We'll use the fictional MostMortgage company's mortgage loan approval application to introduce SCA in more detail. The loan approval application accepts a mortgage request including the customer's details and the requested loan amount. It first checks the customer's credit to make sure the credit score meets the minimum requirement. The interest rate is determined based on the principal requested, the term of the loan, and the customer's home state. It then uses a mortgage calculator to calculate the ratio by dividing the potential monthly payment by the customer's income. The ratio and credit score are passed to do a risk assessment that makes the final decision (see Figure 2).

Using SCA To Implement the Mortgage Loan Approval Application
In the next sections we'll implement the loan approval application using SCA and walk through the creation of individual SCA artifacts. At a high level the loan approval application can be broken down into a number of SCA components that are assembled together into a composite. The components in this composite consist of Loan Approval, Credit Check, Interest Rate, Mortgage Calculator, and Risk Assessment components. The entire composite is deployed in a SCA system (see Figure 3).

SCA Components
An SCA component is the basic building block for creating SOA applications and is characterized by three distinct and yet related pieces of information: a) The program logic that provides the function of the building block (referred to as implementation), b) The definition of how this building block might interact with other components (referred to as component type) c) The concrete description of how this building block fits with all the other blocks to build a solution (referred to as assembly or composition). We'll explain each in more detail in the following sections and give examples but here's an overview.

  • Component Type: The component implementation is provided using any programming language that's supported by an SCA runtime. Component implementers are free to write in any style they're comfortable with but are bound by the services, references and properties, as defined by the component type, in the way that they interact with other SCA components. The SCA specifications describe how each programming language maps to SCA.
  • Component Type: Component type describes the shape of a component in terms of the services it exposes, the references it depends on and the properties that control the component's behavior. Component-type information can be found either in a file where, by convention, the name is ImplementationFileName.componentType and/or by introspection of the component implementation.
  • Component Composition/Assembly: Once a component's implementation and its component type are defined it's ready to be assembled into a network of services that together provide an SOA solution. The assembly is defined in an SCA composite file. The SCA runtime uses the information in this file to instantiate an SCA application.
SCA defines an XML format called Service Component Description Language (SCDL). SCDL is the XML format of component-type files and composite files. For example, the loan approval application's MortgageCalculator component has both component-type and component-implementation files and the MortgageCalculator component is described and wired together with other components in a composite file (see Figure 4).

Component Type
The MortgageCalculator component-type file (MortgageCalculator.componentType) describes the single service that components of this type provide. The MortgageCalculator component doesn't reference other components and doesn't provide any settable properties so <reference> and <property> elements don't appear.

<componentType>
    <service name="MortgageCalculatorService">
       <interface.java interface="mortgage.MortgageCalculator"/>
    </service>
</componentType>

Component Implementation
The class "mortgage.MortgageCalculatorImpl" (MortgageCalculatorImpl.java) contains the business logic for this component.

public class MortgageCalculatorImpl implements MortgageCalculator {
    public double getMonthlyPayment(double principal, int years, float interestRate) {
       double monthlyRate = interestRate / 12.0 / 100.0;
       double p = Math.pow(1 + monthlyRate, years * 12);
       double q = p / (p - 1);
       double monthlyPayment = principal * monthlyRate * q;
       return monthlyPayment;
    }
}

In the next section (Component Services) we show that if we chose to use annotations, as we can in the Java language, the component-type information can be included in the implementation file. Most of the code snippets in this paper use annotations to provide component-type information instead of using a component-type file.

Component Services
Let's take a look at how a component offers a service to others. In the following example MortgageCalculator exposes a service that contains one method, called getMonthlyPayment, by using a @Service annotation. As the Java language runtime supports annotations our method can be exposed as a service interface by simply annotating the class.

@Service(MortgageCalculator.class)
public class MortageCalculatorImpl implements MortageCalculator {

    public double getMonthlyPayment(double principal, float interestRate) {
       ...
    }
}

The @Service annotation tells the SCA runtime that the MortgageCalculatorImpl class instances are exposed as services with an interface defined by the MortgageCalculator interface.

Component References
Now let's look at how a component references other components. We'll use the Loan Approval component that references other components as our example here. Loan Approval is implemented using the Java language and will use annotations. It uses @Reference to indicate its dependency on RiskAssessment, CreditCheck, InterestRateQuote, and MortgageCalculator. The referenced components can be local or remote and the SCA runtime will ensure that these references are correctly set at runtime based on the wiring found in the completed application's SCDL files (shown later in this article). See Listing 1.

Component Interfaces
The business functions provided by a service or required by a reference are described using interfaces in SCA. The interfaces represent the contract for a service or reference. Java and WSDL are two typical interface definition languages.

@Remotable
public interface CreditCheck {
    int getCreditScore(String ssn);
}

Interfaces can be local or remotable. Local interfaces are the most optimized for local interactions between components in the same composite. In contrast, remotable interfaces can be used for loosely coupled remote interactions.

Some business services have peer-to-peer relationships that require a two-way dependency at the service level. In these cases, the business service represents both a consumer of a service provided by a partner business service and a provider of a service to the partner business service. This is especially the case when the interactions are based on asynchronous messaging rather than on remote procedure calls. SCA uses bi-directional interfaces to directly model peer-to-peer bi-directional business service relationships.

For some services a sequence of operations must be called to achieve some higher-level goal. The sequence of operations is referred to as conversation. If the service uses a bi-directional interface, the conversation may include both operations and callbacks. SCA allows interfaces to be marked as conversational to bracket the series of operations in the same conversation.

Component Properties
Component properties can be used to alter the behavior of a component at runtime without making code changes. Let's assume that the LoanApproval component has a component property called "minimumCreditScore," which can be set to different values based on company policy. Below is a code snippet from the LoanApproval component implementation that uses an @Property annotation to identify a property called minimumCreditScore. The property has a default value of 650:

private int minimumCreditScore = 650;

// Property declaration using a setter method
@Property(name = "minimumCreditScore", override = "may")
public void setMinimumCreditScore(int minimumCreditScore) {
    this.minimumCreditScore = minimumCreditScore;
}

The following illustrates customization of the component by setting the "minimumCreditScore" property to 600 in the composite SCDL file to override the default value (650) defined in the component type (remember that we're using Java language annotations to define the component type):

<component name="LoanApprovalComponent">
    <implementation.java class="mortgage.LoanApprovalImpl" />
    <property name="minimumCreditScore">600</property>
    ...
</component>

Composites - Composing Components
So far we've concentrated on developing individual components, making them available as services and defining their dependencies on other services. Now let's look at how the components can be assembled to provide a business solution. This is referred to as a composite, which is a logical concept. A composite contains one or more components (see Figure 5).

If we look at the composite file (default.scdl) for MortgageComposite we can see how this draws all of the components together.

The SCA runtime uses the information in this SCDL file to instantiate, assemble, and configure the components. As can be seen from the example each component is identified by a <component> element in the file and can have references to other components. In this example, LoanApprovalComponent has four <reference> elements that are wired to four other components in the composite. The wiring is depicted through arrows in the diagram. The interfaces on both sides of the wire have to be compatible.

A composite can be reused as a component in the assembly but we don't show an example in this article.

Local Services
The composite file we've just seen shows how component references are "wired" to other components. There's no information included in this composite file to describe what techniques should be used to pass messages between the components. In this case SCA assumes that the components will be local to one another, i.e., they'll be instantiated and run in the same process address space. As we're using the Java language in this example the component instances will run in the same Java VM. SCA is free in this case to use the most efficient mechanism for moving a message from one component to another. This is likely to be a direct component-to-component call with little or no mediation.

On the face of it composition of components using local wiring may not appear to be very useful. Why not simply code these components as normal Java classes and have them interact in the normal way? In the case of coarse-grain components SCA has a number of advantages.

  • Components can easily be reused and reconfigured in other compositions
  • Components that are local today can be made remote tomorrow
  • Components implemented using different supported programming languages can easily be assembled

More Stories By Haleh Mahbod

Haleh Mahbod is a program director with IBM, managing the team contributing to the Apache Tuscany as well as SOA for PHP open source. She has extensive development experience with database technologies and integration servers.

More Stories By Raymond Feng

Raymond Feng is a senior software engineer with IBM. He is now working on the Service Component Architecture (SCA) runtime implementation in Apache Tuscany project as a committer. Raymond has been developing SOA for more than 4 years and he was a key developer and team lead for WebSphere Process Server products since 2002.

More Stories By Simon Laws

Simon Laws is a member of the IBM Open Source SOA project team working with the open source Apache and PHP communities to build Java, C++, and PHP implementations of the Service Component Architecture (SCA) and Service Data Object (SDO) specifications. Prior to this role he was working in the distributed computing space building service-oriented solutions for customers with a particular interest in grid computing and virtualization.

Comments (1) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Stephan 01/23/07 05:11:58 PM EST

For people interested... you can find an SCA presentation (audio + sync'ed slides) by Michael Rowley (BEA) on Parleys.com ! Enjoy.

@ThingsExpo Stories
The Internet of Things (IoT) is making everything it touches smarter – smart devices, smart cars and smart cities. And lucky us, we’re just beginning to reap the benefits as we work toward a networked society. However, this technology-driven innovation is impacting more than just individuals. The IoT has an environmental impact as well, which brings us to the theme of this month’s #IoTuesday Twitter chat. The ability to remove inefficiencies through connected objects is driving change throughout every sector, including waste management. BigBelly Solar, located just outside of Boston, is trans...
SYS-CON Events announced today that Matrix.org has been named “Silver Sponsor” of Internet of @ThingsExpo, which will take place on November 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA. Matrix is an ambitious new open standard for open, distributed, real-time communication over IP. It defines a new approach for interoperable Instant Messaging and VoIP based on pragmatic HTTP APIs and WebRTC, and provides open source reference implementations to showcase and bootstrap the new standard. Our focus is on simplicity, security, and supporting the fullest feature set.
Predicted by Gartner to add $1.9 trillion to the global economy by 2020, the Internet of Everything (IoE) is based on the idea that devices, systems and services will connect in simple, transparent ways, enabling seamless interactions among devices across brands and sectors. As this vision unfolds, it is clear that no single company can accomplish the level of interoperability required to support the horizontal aspects of the IoE. The AllSeen Alliance, announced in December 2013, was formed with the goal to advance IoE adoption and innovation in the connected home, healthcare, education, aut...
SYS-CON Events announced today that Red Hat, the world's leading provider of open source solutions, will exhibit at Internet of @ThingsExpo, which will take place on November 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA. Red Hat is the world's leading provider of open source software solutions, using a community-powered approach to reliable and high-performing cloud, Linux, middleware, storage and virtualization technologies. Red Hat also offers award-winning support, training, and consulting services. As the connective hub in a global network of enterprises, partners, a...

SUNNYVALE, Calif., Oct. 20, 2014 /PRNewswire/ -- Spansion Inc. (NYSE: CODE), a global leader in embedded systems, today added 96 new products to the Spansion® FM4 Family of flexible microcontrollers (MCUs). Based on the ARM® Cortex®-M4F core, the new MCUs boast a 200 MHz operating frequency and support a diverse set of on-chip peripherals for enhanced human machine interfaces (HMIs) and machine-to-machine (M2M) communications. The rich set of periphera...

The only place to be June 9-11 is Cloud Expo & @ThingsExpo 2015 East at the Javits Center in New York City. Join us there as delegates from all over the world come to listen to and engage with speakers & sponsors from the leading Cloud Computing, IoT & Big Data companies. Cloud Expo & @ThingsExpo are the leading events covering the booming market of Cloud Computing, IoT & Big Data for the enterprise. Speakers from all over the world will be hand-picked for their ability to explore the economic strategies that utility/cloud computing provides. Whether public, private, or in a hybrid form, clo...
Software AG helps organizations transform into Digital Enterprises, so they can differentiate from competitors and better engage customers, partners and employees. Using the Software AG Suite, companies can close the gap between business and IT to create digital systems of differentiation that drive front-line agility. We offer four on-ramps to the Digital Enterprise: alignment through collaborative process analysis; transformation through portfolio management; agility through process automation and integration; and visibility through intelligent business operations and big data.
The Transparent Cloud-computing Consortium (abbreviation: T-Cloud Consortium) will conduct research activities into changes in the computing model as a result of collaboration between "device" and "cloud" and the creation of new value and markets through organic data processing High speed and high quality networks, and dramatic improvements in computer processing capabilities, have greatly changed the nature of applications and made the storing and processing of data on the network commonplace.
Be Among the First 100 to Attend & Receive a Smart Beacon. The Physical Web is an open web project within the Chrome team at Google. Scott Jenson leads a team that is working to leverage the scalability and openness of the web to talk to smart devices. The Physical Web uses bluetooth low energy beacons to broadcast an URL wirelessly using an open protocol. Nearby devices can find all URLs in the room, rank them and let the user pick one from a list. Each device is, in effect, a gateway to a web page. This unlocks entirely new use cases so devices can offer tiny bits of information or simple i...
Things are being built upon cloud foundations to transform organizations. This CEO Power Panel at 15th Cloud Expo, moderated by Roger Strukhoff, Cloud Expo and @ThingsExpo conference chair, will address the big issues involving these technologies and, more important, the results they will achieve. How important are public, private, and hybrid cloud to the enterprise? How does one define Big Data? And how is the IoT tying all this together?
The Internet of Things (IoT) is going to require a new way of thinking and of developing software for speed, security and innovation. This requires IT leaders to balance business as usual while anticipating for the next market and technology trends. Cloud provides the right IT asset portfolio to help today’s IT leaders manage the old and prepare for the new. Today the cloud conversation is evolving from private and public to hybrid. This session will provide use cases and insights to reinforce the value of the network in helping organizations to maximize their company’s cloud experience.
TechCrunch reported that "Berlin-based relayr, maker of the WunderBar, an Internet of Things (IoT) hardware dev kit which resembles a chunky chocolate bar, has closed a $2.3 million seed round, from unnamed U.S. and Switzerland-based investors. The startup had previously raised a €250,000 friend and family round, and had been on track to close a €500,000 seed earlier this year — but received a higher funding offer from a different set of investors, which is the $2.3M round it’s reporting."
The Industrial Internet revolution is now underway, enabled by connected machines and billions of devices that communicate and collaborate. The massive amounts of Big Data requiring real-time analysis is flooding legacy IT systems and giving way to cloud environments that can handle the unpredictable workloads. Yet many barriers remain until we can fully realize the opportunities and benefits from the convergence of machines and devices with Big Data and the cloud, including interoperability, data security and privacy.
All major researchers estimate there will be tens of billions devices - computers, smartphones, tablets, and sensors - connected to the Internet by 2020. This number will continue to grow at a rapid pace for the next several decades. Over the summer Gartner released its much anticipated annual Hype Cycle report and the big news is that Internet of Things has now replaced Big Data as the most hyped technology. Indeed, we're hearing more and more about this fascinating new technological paradigm. Every other IT news item seems to be about IoT and its implications on the future of digital busines...
Cultural, regulatory, environmental, political and economic (CREPE) conditions over the past decade are creating cross-industry solution spaces that require processes and technologies from both the Internet of Things (IoT), and Data Management and Analytics (DMA). These solution spaces are evolving into Sensor Analytics Ecosystems (SAE) that represent significant new opportunities for organizations of all types. Public Utilities throughout the world, providing electricity, natural gas and water, are pursuing SmartGrid initiatives that represent one of the more mature examples of SAE. We have s...
The Internet of Things needs an entirely new security model, or does it? Can we save some old and tested controls for the latest emerging and different technology environments? In his session at Internet of @ThingsExpo, Davi Ottenheimer, EMC Senior Director of Trust, will review hands-on lessons with IoT devices and reveal privacy options and a new risk balance you might not expect.
IoT is still a vague buzzword for many people. In his session at Internet of @ThingsExpo, Mike Kavis, Vice President & Principal Cloud Architect at Cloud Technology Partners, will discuss the business value of IoT that goes far beyond the general public's perception that IoT is all about wearables and home consumer services. The presentation will also discuss how IoT is perceived by investors and how venture capitalist access this space. Other topics to discuss are barriers to success, what is new, what is old, and what the future may hold.
Swiss innovators dizmo Inc. launches its ground-breaking software, which turns any digital surface into an immersive platform. The dizmo platform seamlessly connects digital and physical objects in the home and at the workplace. Dizmo breaks down traditional boundaries between device, operating systems, apps and software, transforming the way users work, play and live. It supports orchestration and collaboration in an unparalleled way enabling any data to instantaneously be accessed on any surface, anywhere and made interactive. Dizmo brings fantasies as seen in Sci-fi movies such as Iro...
There’s Big Data, then there’s really Big Data from the Internet of Things. IoT is evolving to include many data possibilities like new types of event, log and network data. The volumes are enormous, generating tens of billions of logs per day, which raise data challenges. Early IoT deployments are relying heavily on both the cloud and managed service providers to navigate these challenges. In her session at 6th Big Data Expo®, Hannah Smalltree, Director at Treasure Data, to discuss how IoT, Big Data and deployments are processing massive data volumes from wearables, utilities and other mach...
This Internet of Nouns trend is still in the early stages and many of our already connected gadgets do provide human benefits over the typical infotainment. Internet of Things or IoT. You know, where everyday objects have software, chips, and sensors to capture data and report back. Household items like refrigerators, toilets and thermostats along with clothing, cars and soon, the entire home will be connected. Many of these devices provide actionable data - or just fun entertainment - so people can make decisions about whatever is being monitored. It can also help save lives.