For such a platform, the MA configuration file could be:
| # file MA_example.cfg, configuration file for an MA | |||
| agentType | = | DIET_MASTER_AGENT | |
| name | = | MA_example | |
| #traceLevel | = | 1 | # default |
| #dietPort | = | <port> | # not needed |
| #dietHostname | = | <hostname|IP> | # not needed |
| fastUse | = | 1 | |
| #ldapUse | = | 0 | # default |
| nwsUse | = | 1 | |
| nwsNameserver | = | nwshost:9001 | |
| #useLogService | = | 0 | # default |
| #lsOutbuffersize | = | 0 | # default |
| #lsFlushinterval | = | 10000 | # default |
This configuration file is the only argument to the executable dietAgent, which is installed in install_dir/bin. Provided install_dir/bin is in your PATH environment variable, run
~ > dietAgent MA_example.cfg Master Agent MA_example started.