Specifications

AVIDdirector-M2M™ Technical Reference Guide

currently not implemented via the existing M2MApp. A developer needs to program in Java and will

need a basic understanding of the M2MApp APIs in order to write an M2Mlet.

M2MApp is the main program running on the device. It controls the execution of the IODevices, the

communication devices (Radios), any user written application (M2Mlet), parsing and generation of M2MXML

messages to and from the M2MXML server / portal. This is an extensible framework that can be easily adapted

to each customer’s unique device and control application without having to make changes to the framework’s

infrastructure. Since M2MApp handles all the communications, input and output control, message passing and

error control, users can develop M2Mapplications in a fraction of the time it would take them if they had to

design and implement the protocols, communications mechanisms, M2MXML parsing and device drivers.

M2MApp is written in Java and uses the Java concepts of dynamical class loading, inheritance, interfaces and

method overriding to implement its functionality.

The M2MApp is designed as follows:

Key concepts and features of the M2M Application Framework are:

M2Mlet

If a custom user application is required, the developer writes a “M2Mlet”, similar to a Midlet in J2ME

or an Applet in J2SE. An M2Mlet has start() and stop() methods that must be implemented in the

user application. If the program requires background processing it must start a Thread to perform

the processing until the stop() method is called. M2Mapp loads the user written M2Mlet specified in

the M2MApp.ini

configuration file.

See Appendix 6 “Sample M2MApp.ini Configuration File”