...
The figure below illustrates how you can edit a particular system property, either using a command or a text editor.
...
Manual Configuration
There are three methods of manually editing configurations in STR.
Method 1
Open a configuration file under
MZ_HOME/common/config/cell/default/master.Edit the file and save.
Run the mzsh command
topo activate. This is required in order the for changes to become effective.Code Block $ mzsh topo activate
Method 2
Open a configuration by running the
mzsh commandtopo open. The configuration opens in vi or the editor specified by the environment variable EDITOR.
| Info |
|---|
...
Example - Opening a |
...
Cell Configuration
|
...
...
|
| Info |
|---|
...
Example - Opening a |
...
Container Configuration
|
...
...
|
| Info |
|---|
...
Example - Opening a |
...
Pico Configuration
|
...
...
or
|
...
...
|
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
|
...
...
|
Edit the configuration and save. The mzsh
...
command
topo activatewill be called with the--verboseoption 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.
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ mzsh topo set --no-activation |
| Excerpt | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Note | |
|---|---|
| title | Note!Note that theThe 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 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 https:/wiki/spaces/MD82/pages/3786575 in //infozone.atlassian.net/wiki/spaces/MD82MD91/pages/377893523277454/topo?atl_f=content-tree .
For further information about how to manage pico- and service configurations, see Managing Picos with Topo and Managing Service Configurations/wiki/spaces/MD91/pages/23148541.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Scroll pagebreak |
|---|