Simplified configuration and maintenance of GT.m for developers is a key objective of easyM.

Developers do not need highly optimised GT.m instances, vanilla instances will do.

Developers want to develop code NOT configure environments.

The goal of easyM is to abstract the low level configuration of GT.m with high level vanilla instances.

easyM will achieve this in a number of ways...

• A core instance will provide a central repository of knowledge and functionality for managing instances
• A mumps routine will provide an abstracted API to configuration and maintenance scripts
• A web based tool will provide a simple GUI interface to this API

The functionality of this will include the following functions

• Create a new developer (vanilla) instance
• Update a developer instance
• Copy a developer instance
• Delete a developer instance
• Backup a developer instance
• Set journal purge period for an instance
• Repair a developer instance
• Register a start up function for an instance

easyM will come with a boot up script that will repair the easyM core instance and start up a core easyM process. This process will repair and purge instances registered in the core database. An optional startup function can be registered with an instance, this can be used to clear down temp globals etc.