• Overview
• Features
• Development
• Application Modeling
• Configuration
• Importing Components
• AMTP Tree
• Templates
• Message Passing API
• QoS API
• Tools
• JPACT
• JPVAC
• JPVTC
• QoS GUI
• Applications
• Mandelbrot
• Resource Monitoring
• Fault Tolerance
• Load Balancing
• Publications
• Presentations
• Theses
• Documentation
• Notable
• People
• Work in Progress
• Resources
• Contact us

The AMTP Tree

The JPACT is used to compile the application's configuration file and store information into a tree-like object that represents the task graph and is used by JavaPorts to achieve port configuration in a manner transparent to the user. The Machine-Task-Port triplets are organized as nodes at different levels of the application tree (hence the name A-M-T-P). Each tree node stores information related to certain application characteristics. The AMTP tree shown below represents the task graph we have been using as a running example.

The root node carries the name of the application and the number of machines to be used for its distributed execution.

A 2nd level, machine representing node carries:

• a machine variable name
• the actual machine domain name
• the MASTER flag value (i.e. true if the application will be launched from that machine)
• the number of user-defined tasks allocated to that machine
• the x-y coordinates used by the JPVAC to display the machine (or the default values (0,0) if the JPVAC was not used).

Similarly, a 3rd level, task representing node stores:

• the task variable name
• the name of the Javaor Matlab code template implementing the task
• the string used to name the task when displayed using the JPVAC
• the number of Ports defined for this task
• the x-y JPVAC assigned coordinates

A Port representing leaf node stores connection related information i.e. the T-P pairs of the two connected peer ports.