Tool Mentor: Configure and Run the UML-to-SCA Transform
Use a SoaML services model as the input that is used to generate OpenSCA component specifications, WSDLs, XSDs, and related Java implementations.
Tool: Rational Software Architect
Relationships
Main Description

Introduction

Rational Software Architect for WebSphere Software Version 7.5.4 and later (henceforth "RSA") provides an extensible UML-to-SCA transform.  The productized implementation accepts service models or packages with components as input, and it generates XSDs, WSDLs, SCA composite definitions, and Java implementations for interfaces and components.  Output conforms to the SCA 1.0 specification.  The specific output depends upon what model elements are present in the source, how they are marked up, and how the transformation has been configured.  

  • See  Transforming UML models into Service Component Architecture artifacts for full information on the UML-to-SCA transform.
  • See  UML-to-SCA transforms for essential information regarding:
    • Valid transformation sources and targets. 
    • Transformation output
  • See   Configuring UML-to-SCA Transformations for instruction as to how to create and configure a new UML-to-SCA transformation.
  • See  Running UML-to-SCA transformations for guidance regarding how to run a UML-to-SCA transformation.

Tuning the Results Achieved Using the UML-to-SCA Transform

Output from the UML-to-SCA transform depends upon several factors, including the following:

  • Whether the service model is being created using "raw" UML or using the SoaML stereotypes 
  • Whether service model elements have been adorned with SCA stereotypes
  • What configuration options have been set in the transformation configuration
  • The intent of the designer, as reflected in how specific elements, such as components and component internal elements, are modeled.

See    Stereotypes of the SCA transformation profile for a discussion of the stereotypes and the impact they have on artifact generation.  Most specifically, observe that either the <<Remote>> or <<WSDL>> stereotypes must be applied to an Interface, if WSDL generation is desired.

See   Interpretation of UML model elements by UML-to-SCA transformations to read about all the modeling choices that can impact UML-to-SCA artifact generation.  There is a comprehensive -- and complex -- set of options. 

Recommended Modeling Practices to Support the UML-to-SCA transform

The following simple rules for service modeling help yield consistent, good results using the UML-to-SCA transform:

  • Always model service-oriented concepts using the SoaML stereotypes
    • Always specify service providers and consumers as Participants
    • Always specify Participant ports as ServicePoints or RequestPoints
    • Always specify ServicePoint and RequestPoint types as ServiceInterfaces
  • Remember to apply either the WSDL or the Remote stereotype to ServiceInterfaces from which you intend to generate WSDL.
More Information
Concepts