Working with STR

Owned by Former user (Deleted)
Last updated: Oct 09, 2024 by Jenni Wallin
3 min read

A principle behind the configuration representation used in the STR, is to support both manual configuration, i e editing configuration files in a text editor, and scripted configuration using the mzsh topo command. Most changes to the files can be done in either way. 

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

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 for the changes to become effective. 

    $ 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.

Example - Opening a Cell Configuration

$ mzsh topo open cell:default

Example - Opening a Container Configuration

$ mzsh topo open main1

Example - Opening a Pico Configuration

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

  1. Edit the configuration and save. The mzsh 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 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. 

 

For further information about the various sub-commands that are available in the mzsh topo command, see topo.

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