Versions Compared

Key

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

...

The figure below illustrates how you can edit a particular system property, either using a command or a text editor. 

Image Removed

Updating a system property in STR

...

Manual Configuration

There are three methods of manually editing configurations in STR.

Method 1

  1. Open a configuration file under MZ_HOME/common/config/cell/default/master.

  2. Edit the file and save.

  3. Run the mzsh command topo activate. This is required in order the for changes to become effective. 

    Code Block
    $ mzsh topo activate

Method 2

  1. Open a configuration by running the mzsh command topo open. The configuration opens in vi or the editor specified by the environment variable EDITOR.

Info

...

Example - Opening a cell configuration

Code Block

...

$ mzsh topo open cell:default
Info

...

Example - Opening a container configuration

Code Block

...

languagetext
$ mzsh topo open main1
Info

...

Example - Opening a pico configuration

Code Block

...

$ mzsh topo open ec1

or

Code Block

...

languagetext
$ mzsh topo open container:main1/pico:ec1

If the pico name is not unique in the system, you will be prompted to specify the container.

Info

...

Example - Multiple pico

...

configurations sharing the same name

Code Block

...

...

$ mzsh topo open ec2 (/home/main1/common/config/cell/default/master/containers/main1/picos/ec2.conf,ec2,topo://container:main1/pico:ec2)
(/home/main1/common/config/cell/default/master/containers/exec1/picos/ec2.conf,ec2,topo://container:exec1/pico:ec2)

Multiple entries, select one:
 (1) topo://container:main1/pico:ec2
 (2) topo://container:exec1/pico:ec2
 [1] :
  1. Edit the configuration and save. The mzsh

...

  1. command topo activate will be called with the --verbose option and the saved changes are displayed in a scripted syntax.

Method 3

As an alternative to the command line  tool, you can manage pico configurations and start/stop pico instances from the System Administration GUI. For further information, see 2.5 System Administration UI.Managing Picos in Desktop.

Activation and Validation

When you use the mzsh commands  topo set or topo open, changes are automatically validated before they are copied to the active registry. If the command and its arguments can be parsed but fails the validation, you can update the configuration or use a reset command to undo the changes.  

You can disable the validation by using the option --no-activation. Changes performed by the mzsh topo will then remain in the master registry until you submit a separate activate command. 

Code Block
languagetext
themeEclipse
 $ mzsh topo set --no-activation
Excerpt
Tip

Hint!

The options --dry-run and --verbose are useful to learn the mzsh topo syntax. When you have edited the configuration manually, use the following command, to view the corresponding edits in a scripted syntax:

title
Code Block
languagetextthemeEclipse
$ mzsh topo activate --dry-run --verbose
Info

Example

- Output

output from

activate

activation with verbose option:

Code Block
$ mzsh topo activate -v --dry-run
mzsh topo set topo://container:main1/pico:ec1/val:config.properties.ec.httpd.port 9096  # (was: 9092)
Dry-run: Validation successful
Dry-run: Stopping without performing activation
Dry-run: Active registry not changed

You can then restore the master registry with the the command mzsh topo reset.

Info
title

Restart the picos to apply the changes.

Note

Caution!

Changes to the STR are not applied on running pico instances or services. For instance, if you have updated the properties of the Platform and an EC, both must be restarted after activation.

Note
title

Example

, after an mzsh topo activate of ec5,

of how to use mzsh shutdown and startup

needs to be

is done to apply

the changes.

changes after an mzsh topo activate of ec5:

language
$ mzsh shutdown ec5
$ mzsh startup ec5
Code Block
text
Note
title

Note!

Note that the

The sorting and layout of the configuration files may change when it is updated both using manual editing and the commands. That means that the exact ordering of keys, and layout of the file could change. However: this will not affect how

interprets

the system interprets the configuration at runtime. It is not supported to edit the configuration files using command line utilities (such as sed or awk), all scripted changes must be done via the mzsh topo command, to minimize the risk of invalid assumptions regarding the exact layout of the configuration files.

For further information about the various sub-commands that are available in the mzsh topo command, see /wiki/spaces/MD82/pages/3786575 in /wiki/spaces/MD82/pages/3778935see topo.

For further information about how to manage pico- and service configurations, see Managing Pico ConfigurationsPicos with Topo and Managing Service Configurations.

Insert excerpt
MD82:2.1.15 topoMD82:2.1.15
topo
nopaneltrue

Scroll pagebreak