Page History

...

This is a high level architecture document for Tuscany Java implementation of Service Component Architecture (SCA) which is defined in the specifications located at (http://wwww.osoa.org^{Image Removed}).

This is a live document and is more focused on what is implemented rather than the end vision.
Goal of this document is to help users/developers better understand what Tuscany SCA offers and enable them to help with the development if interested.

...

Anchor
Modules Modules

Module Structure

\[Note: Do we want to link to [Kernel-Structure|Java SCA Modulization Design Discussions]\]?

As illustrated below, the Tuscany runtime consists of the following key modules/packages:

...

• This is similar to the local deployer, however registers
  itself with the discovery service for receiving physical model updates
• The federated deployer doesn't use the loader framework
• The federated deployer accepts serialized physical model
  information in XML, rather than raw SCDL as with local deployer
• It uses the current builder framework to build, prepare
  and start the components

  Note
  title A note from Jeremy on federated deployment Feb. 9, 2007.
  The design is that there is a "master" node that is working out which"physical" nodes components are going to run on. It then passes PhysicalComponentDefinition's to the worker nodes to get them tocreate the component and any transport bindings it needs to talk toother nodes. The PCDs are portable, independent of the type ofruntime, instead tied to the type of component.Picking on Ruby as an example as we know we can run that on Java andNative runtimes, there could be one common PCD for a Ruby componentthat was supported by all container implementations. The master couldsend that to any node to have it run a Ruby component. A runtimecould also offer "enhanced" Ruby support with additional featuresthat required additional configuration. If would offer support for adifferent PCD with that additional metadata. Which one is selected bythe master would be part of its component allocation algorithm.So basically, any runtime that can connect to the federated fabricand handle a PCD can join the SCA domain. We picked JXTA and XML forthe fabric and PCD encoding as there is support for those in bothJava and C++. Adding support for that to the Native runtime wouldalso be good if you were skeptical of all the Java stuff.

Work outstanding

• Define the physical model in Java
• Define the corresponding XML infoset

...