CloudTran Guide - Defining Applications In Eclipse


Contents

Chapter 5. Defining Applications In Eclipse

CloudTran supports use of the Eclipse hierarchical EMF modeller to model applications and deployed solutions.

The steps to do this are:

Create the Eclipse project for the application.
Model the application architecture, and the deployments to different platforms and configurations; this is all done in the same model.
Fill in the business logic in the implementation classes.
Generate using within-Eclipse build, or an external build
Run one of the generated deployments.

The Eclipse hierarchical EMF modeller stores the entered data in the '.osm' format - this is a GigaSpaces-specific modelling dialect. This is a very simple form of XML, and has element, attributes and nesting, just like XML written by hand. The advantage of using the OSM editor over using other XML-entry tools is that it provides a structured way of entering the data - at all points, it gives the available properties and nested elements - and guarantees the XML syntax is correct. It also allows you to specify references from one modelling element to another, that remain valid even if names change.

Even using the OSM editor, it is still possible to get semantic errors; these are picked up at build time.

There may be references in this chapter to GigaSystemBuilder, the precursor product for CloudTran, but the information is still correct - CloudTran is an upward-compatible upgrade of GigaSystemBuilder.

5.1 Creating the Project

5.2 How To Model

5.3 Modelling Concepts

5.4 Configuration

5.5 Default 'config.properties' File

5.6 Types