Revision as of 17:20, 23 February 2013 by German Valero (talk | contribs) (copied doc from Moodlle 2.3 doc branch (updated 21 dec 2012))

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Note: You are currently viewing documentation for Moodle 3.2. Up-to-date documentation for the latest stable version of Moodle is probably available here: Super-administration.

Back to index

General principles for MNET super-administration

MNET super-administration is a feature allowing to massively play some administration commands on a set of virtualized Moodle platforms. The commands are transmitted to each nodes using a dedicated MNET function attached to the VMoodle block scope. The emitting platform should subscribe to the super-administration service, receiving nodes should publish the super-administration service.

The MNET super-administration will provide a unique process for executing any network administration command :

  1. Building the command : Mostly SQL orders, build manually or through some command preset.
  2. Choosing targets.
  3. Command execution and getting results.

Tip !! : command and targets are stored in session, thus it will be easy to play the same command on another target set, or keeping the target set and making a new command on it.

Super-administration main screen provides several command sets. As super-administration is a fully extensible architeture, developpers and integrators may easily add command blocks and define new command templates.

Advanced mode

The advanced mode will allow an administator to write a full SQL query to be played on all target moodles. Note that the SQL must be independant of local context to have chancs to proceed with success.