Chapter 2. Getting Started

Contents

Obtaining Jamda

System and software requirements

Installation

Testing the installation

Building Jamda from source

Running Jamda

Obtaining Jamda

Jamda can be downloaded from www.jamda.net

System and software requirements

Recommended minimum system requirements

Pentium III 500Mhz or better
256Mb main memory
50Mb free disk space for model and generated files

Software required to use Jamda

Java™ 2 SDK, Standard Edition, v 1.4
Apache Ant build tool version 1.5.1 or greater.
A UML modelling tool which can export the model in the XMI format. Jamda has been developed using models created with MagicDraw UML Standard Edition version 6.0, and although XMI should be a standard format, models from this tool are most likely to be compatible with Jamda.

Other third-party software required by Jamda is included in the distribution lib directory.

Installation

Unpack the binary distribution file in a suitable directory. This will create a new directory jamda-<version> below the directory where the distribution is unpacked.

Ensure that Ant is installed and the ANT_HOME environment variable is set.

Testing the installation

Set the JAMDA_HOME environment variable to the top-level Jamda installation directory eg C:\mystuff\jamda. Run the JUnit.bat script in the bin directory.

Building Jamda from source

Unpack the full distribution file in a suitable directory. This will create a new directory jamda-<version> below the directory where the distribution is unpacked.

Ensure that Ant is installed and the ANT_HOME environment variable is set.

Ensure that DocBook XSL is installed and the DOCBOOK_HOME environment variable is set.

Run the ant command in the jamda directory.

Running Jamda

As Jamda is a framework for you to create your own model compilers, it does not run "out of the box". You have to do some configuration and/or creation of new Java classes based on the framework in order to use it. This process is described in the remainder of this document. However, you may wish to try running the supplied samples which run a simple Jamda configuration on a demonstration UML model.