Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attributes, i e properties, that that are set on container level (in container.conf) or cell level (cell.conf) are inherited by pico configurations. 

Pico Level Attributes

Run the following commands to add or update an attribute of a pico configuration in a container.

...

Info
titleExample - Updating a general pico attribute
Code Block
languagetext
themeEclipse
$ mzsh topo set topo://container:main1/pico:ec2/val:ec_type ecsa
Info
titleExample - Updating a system property


Code Block
languagetext
themeEclipse
$ mzsh topo set topo://container:main1/pico:platform/val:config.properties.mz.subfolder.enabled true


...

Info
titleExample - Updating a pico object


Code Block
languagetext
themeEclipse
$ mzsh topo set topo://container:main1/pico:ec2 '{
    template:mz.standard-ec
    config {
        properties {
            httpdec.webserver.port :=9092
        } 
        classpath {
            jars=["lib/picostart.jar"]
		}
    }
}'


Container Level Attributes

Run the following command to add or update an attribute on container level.

...

Note

You cannot add JVM arguments or classpaths on the container level. If you need to add JVM arguments that are applied to all pico processes, it is recommended that you do so by using templates.

Cell Level Attributes

Run the following commands to add or update an attribute on cell level.

...

Note

You cannot add JVM arguments or classpaths on the cell level. If you need to add JVM arguments or classpaths that are applied to all pico processes, it is recommended that you do so by using templates.

Desktop Attributes

Run the following commands to add or update a custom default attribute for Desktop instances.

...