You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 58 Next »

Welcome to the Apache Tuscany SCA User guide. Here you will find information aimed to help you develop SCA components and applications using Tuscany's Java SCA implementation.

This is a work in progress, so please contribute and comment so we can make this valuable to you


Apache Tuscany SCA User Guide

Getting Started

  1. Introduction
  2. Why SCA?
  3. Downloading Java SCA

Example Application

Using Tuscany SCA

Introduction">Introduction

Service Component Architecture (SCA) defines technologies for creating services and assembling them into higher-order service networks. SCA provides a language-independent way to compose and deploy service networks. SCA also defines language-specific client programming models for service authoring including Java, Spring, C++, and PHP. This user guide is for Java SCA implementation in Tuscany.

This user guide will help you build a simple application called calculator sample and extend it to more complicated use the Calculator Sample to demonstrate the concepts in SCA and helps you build a simple application using Tuscany Java SCA.

[NOTE: We should focus the user guide on end users. They should not need to download source code]

Why SCA? ">Why 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.

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 in a distributed or simple environment.

SCA programming model frees developers from polluting business logic with protocol handling and instead enables them to focus on the business logic through clear component interfaces and binding extensions.

DownLoading SCA "> DownLoading SCA

Point to download page. (http://incubator.apache.org/tuscany/sca_downloads.html)
Decide which release this calculator sample will be tested with and guide user to download that release.

Example Overview "> Example Overview

Paste a picture of calculator application here and explain what we are trying to achieve. cut/paste from Mario's slides.

Running the Calculator Sample">Running the Calculator Sample

These are preliminary steps...details such as from where to download are forthcoming

  1.  Download the sample file.
  2.  Unzip it to a local folder such as C:\Temp
  3.  In Eclipse, select File -> Import -> General -> Existing Projects into Workspace
  4.  Click Next.
  5.  Select the Select root directory option and click the "Browse" button to point to C:\Temp.
  6.  Select CalcultorSample directory and click Finish. The project is created.
  7.  Expand the CalcultorSample. Expand "src/main/java/calculator", right-click CalculatorClient.java and select Run as ... --> Java Application. You will see   the following output in the console view:

3 + 2=5.0
3 - 2=1.0
3 * 2=6.0
3 / 2=1.5

Building your own Calculator Application">Building your own Calculator Application

Topics to include?

Creating Java SCA Components
Creating the implementation for the Java SCA components
Creating the composite file
Creatomg a client to invoke the service
Packaging a Standalone Tuscany Application?
Building a Tuscany Web Application?

Components">Components

Compents are the building blocks for creating SOA Applications. They contain the information that defines the program logic or implementation (component implementation), how the component interacts with other components (component type) and defines how it fits in with the other parts of the soluion (composition/assembly).

  • A service header file that defines the operations that can be invoked on the component
  • An implementation header file that defines the implementation and extends the service header file
  • A C++ implementation of the service that implements the operations defined in the service header file
  • Proxy and wrapper header and implementation files generated by the Tuscany C++ SCAGEN tool
  • A service definition in a .componentType file
  • An SCDL component definition within an SCDL composite file. Usually this composite file will contain multiple components configured and assembled together.

Service Component Descritpion Language (SCDL)">Service Component Descritpion Language (SCDL)

Create a client to invoke the service.">Create a client to invoke the service.

  1. Create a file and name it CalculatorClient.java 

Your component, composite and subsystem are now ready to be invoked. Create a client that will call the service. E.g. the Calculator client (in the CalculatorClient.cpp file) contains code similar to the following:

package calculator;

import org.apache.tuscany.api.SCAContainer;
import org.osoa.sca.CompositeContext;
import org.osoa.sca.CurrentCompositeContext;

/**
* This client program shows how to create an SCA runtime, start it,
* locate the Calculator service and invoke it.
**/
public class CalculatorClient {
public static void main(String[] args) throws Exception { 
  SCAContainer.start("Calculator.composite"); 
  CompositeContext context = CurrentCompositeContext.getContext(); 
  CalculatorService calculatorService = 
  context.locateService(CalculatorService.class, "CalculatorServiceComponent"); 
  // Calculate 
  System.out.println("3 + 2=" + calculatorService.add(3, 2)); 
  System.out.println("3 - 2=" + calculatorService.subtract(3, 2)); 
  System.out.println("3 * 2=" + calculatorService.multiply(3, 2)); 
  System.out.println("3 / 2=" + calculatorService.divide(3, 2)); 
  SCAContainer.stop(); 
 }
}

Building a Tuscany Web Application">Building a Tuscany Web Application

You can run Tuscany inside of a Web application running in any standard Web container such as Apache Tomcat. Once configured, the application is portable across container implementations.

Unknown macro: {HTMLcomment}
  • No labels