MAE Daemon Architecture
The commhub daemon is the task master and communications hub for all the other daemons.
Daemon |
Description |
Communications hub, task manager. | |
Database broker, abstracting data storage for the system. | |
Message broker. Keeps track of who (daemon) is listening for messages; routes sent messages to correct listeners. | |
Remote Procedure broker. Keeps track of who (daemon) is servicing requests; routes requests to correct service daemon. | |
User console device driver. Users connect to usergw via web browser on port 8048; daemons send output instructions to usergw, which translates requests to HTML and manages all the user consoles | |
GUI manager that responds to inputs and updates appropriate users. The GUI broker is about user actions and processing output-related activity. |
For additional daemons, see MAE Daemons.
See either the Developing a New Daemon or Developing a New App page. Both are very similar, but a daemon provides services to other daemons and apps whereas an app interacts with user activity and consumes the various services.
Create a single row CSV file formatted like mgmttaskdb.csv, being careful to set each value appropriate for the column for your task. Register this task with commhub using the tadd command, like this
tadd filename.csv
To start the daemons, execute these two commands on the primary server ([[CommHub]] root node):
PATH=$PATH:/usr/mae/bin
tstart
Note: If commhub is not running, the first time using tstart it should be run the root user. After commhub is running, tstart does not require root user.