...

The file default.conf contains the installed default values for Desktop properties and JVM arguments. Though it is possible to edit this file, it is recommended that you add set custom default in in client.conf, since the contents may be overwritten by at by Image Added at any time. 

config {
    jvmargs {
     . . .
    }
    properties {
     . . .
    }
}

...

The file cell.conf contains properties that are common to the Platform , EC/ECSAs and SCsECs. 

common {
    config {
        name=common
    }
	#properties
}

custom.conf

...

standard.conf

...

...

language	text
theme	Eclipse

...

<service> {
 config {
  #properties...
 }
 start-after=[service1,...,service n]
 template="1/standard/basic"
}

standard.conf

The file standard.conf contains predefined service definitions that are required by the system. You can override the properties in this file by updating custom.conf.

...

The files in the templates directory contains pico configuration templates. The subfolder mz contains preconfigured templates that should not be edited: 

• standard-ecstandard-ecsa
• standard-sc standard-platform
• standard (base template for all pico types)

...

Though it is possible to edit these files, it is recommended that you add custom templates in separate files and subdirectories, since the contents in mz may be overwritten by at by Image Added at any time. 

config {
    properties {
        ec {
            backlog {
                dir=${mz.home}"/tmp"
            }
            httpd {
                password="DR_DEFAULT_KEY-1D2E6A059AF8120841E62C87CFDB3FF4"
                port=9090
                user=mzadmin
            }
            shutdown {
                time=60000
            }
        }
        pico {
            bootstrapclass="com.digitalroute.wf.pico.ECSAHTTPDECHTTPD"
            type=ec
        }
    }
}
template="mz.standard"
template-only=true
type=ec

...

{
	template=<template name space>.<template file name>
	settings {
		pico-groups=[]
		state=enabled
	    tags=[]
	}
 	config {
  		classpath {
			#classpaths...
  		}
  		jvmargs {
			#jvmargs...
		}
		properties {
			#properties... {
			pico
				#picos.. {
				groups {
					#groups...
				}
			}
		}
 	}
}

You can set the attributes of the pico process directly and/or inherit the attributes of a template. Attributes that are set directly will override those that are inherited from a template.

...

{
	template="example-ec"
	settings {	
		pico-.groups=[group1]
		state=enabled
	    tags=[tag1,tag2] 
	}
	config {
		properties {
    		ec.httpd.port: 9090
   		}
  	}
}

...

$ mzsh topo register -u --address <IP address or hostname> 

If you want to prevent EC/ECSAs or SCs ECs from starting in a container, set the attribute disabled to true. The default value is false.

...