Example - Converting an XML fileFile

$ mzsh topo convert --container main1 

Example - Comparing registry filesRegistry Files

Run the following command to view the differences between the active registry and the master registry.

$ mzsh topo diff

or

$ mzsh topo diff --from master

Run the following command to view the differences between the active registry and the backup registry.

$ mzsh topo diff --from backup

Example - Reading the environment variablesEnvironment Variables

$ mzsh topo env
export JAVA_HOME="/opt/Java/JavaVirtualMachines/jdk-17.0.2.jdk/Contents/Home"
export MZ_CONTAINER="main1"
export MZ_CONTAINER_TYPE="platform"
export MZ_PLATFORM="http://localhost:9000"
export MZ_HOME="/user/home/mz/main1"

Example - Setting the environment variable Environment Variable JAVA_HOME

$ mzsh topo env --update-java-home /opt/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home

Example - Viewing pico attributesPico Attributes

Run the following command to view a specific attribute in a pico configuration.

$ mzsh topo get topo://container:main1/pico:ec2/val:_name

You can retrieve the attributes of multiple pico processes by replacing the full path with a regular expression.

$ mzsh topo get --format data-only topo://container:main1/pico:.*/val:_name

Example - Using hash valuesHash Values

1. Application 1 retrieves a new hash value.

   Code Block
   language text
   $ mzsh topo hash  "3a2e373fa1653c7f0e757e2682c70317-2028777631"

2. Application 1 retrieves the properties of ec1.

   Code Block
   language text
   $ mzsh topo get -l pico:ec1/obj:config.properties

3. Application 1 updates a property but does not call topo activate. The hash is specified to ensure that changes by other users are not activated inadvertently later on.

   Code Block
   language text
   $ mzsh topo set -l --no-activation --hash 3a2e373fa1653c7f0e757e2682c70317-2028777631 \  topo://pico:ec1/val:config.properties.ec.httpd.port 9090

4. Application 2 updates the properties of ec1. The hash value is updated.

   Code Block
   language text
   $ mzsh topo set -l topo://pico:ec1/val:config.properties.ec.httpd.port 9090

5. Application 1 calls topo activate with hash value retrieved in step 1.

   Code Block
   language text
   $ mzsh topo activate --hash 3a2e373fa1653c7f0e757e2682c70317-2028777631

6. The activation fails since the hash values do not match.

   Code Block
   Specified hash does not match transaction id: d9cd38f3793647028bd7e5d64c354ad5-2055434210 != 3a2e373fa1653c7f0e757e2682c70317-2028777631) This may indicate concurrent modification of registry: Operation aborted!

7. Application 1 resets the master registry, retrieves a new hash and starts over.

   Code Block
   language text
   $ mzsh topo reset $ mzsh topo hash

Example - Opening a cell configurationCell Configuration

$ mzsh topo open cell:default

Example - Opening a container configurationContainer Configuration

$ mzsh topo open main1

Example - Opening a pico configurationPico Configuration

$ mzsh topo open ec1

or

$ mzsh topo open container:main1/pico:ec1

Example - Multiple pico configuration sharing the same namePico Configurations Sharing the Same Name

$ 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] :

Example - Opening a service configurationService Configuration

$ mzsh topo open services:custom

Example - Setting nano as the default editorDefault Editor

$ export EDITOR=nano

Example - Rebasing an EC configurationConfiguration

$ mzsh topo rebase-configs topo://container:main1/pico:ec1$ mzsh topo active --verbose

or

mzsh topo rebase-configs --actoivate topo://container:main1/pico:ec1

Example - Creating pico configurationPico Configuration

When you specify a pico configuration that consists of multiple attributes, it is recommended that you use multi-line strings.  

HOCON Format:

$ mzsh topo set --local pico:ec2 '
{
	template:mz.standard-ec
	config {
		properties {
			ec.httpd.port : 9092
		} 
		classpath {
			jars=["lib/picostart.jar"]
		}
	}
}'

JSON Format:

mzsh topo set -l --strict-json pico:ec2 '
{
	"template": "mz.standard-ec",
	"config": {
		"properties": {
			"ec": {
				"httpd": {
					"port": 9092
				}
			}
		},
		"classpath": {
			"jars": ["lib/picostart.jar"]
		}
	}
}'

Add the pico group setting by using the following topo command

mzsh topo set topo://container:main1/pico:ec1/val:config.properties.pico.groups "ec1, ec2"

This command makes the Execution context "EC1" a member of the "ec1" and "ec2" groups. 

This is the HOCON example format adding in ECs to a pico group. 

config {
    classpath {}
    jvmargs {
        args=[]
    }
    properties {
        mz.webserver.xframeoptions=DENY
        pico.groups="ec1, ec2"
        ec.backlog.dir="/home/davids/git/mz9/mediationzone/mz-dist/../mzhomes/mz9/tmp"
        ec.webserver.port=9137
    }
    vendor-jvmargs {
        hp {}
        sun {}
    }
}

Example - Updating a pico attributePico Attribute

$ mzsh topo set topo://container:main1/pico:ec2/val:ec_type ec

Example - Updating a pico objectPico Object

This command adds the properties value1 and value2:

$ mzsh topo set topo://container:main1/pico:ec2/obj:config.properties.example_object '{
 value1=1
 value2=2
}'

The following commands does not overwrite the properties value1 and value2 in example_object but adds value3:

$ mzsh topo set topo://container:main1/pico:ec2/obj:config.properties.example_object '{
 value3=3
}'

Example - Get current config Current Config

$ mzsh topo get -s --format data-only topo://container:platform1/pico:platform/obj:config.properties.mz.jdbc
	{
		"password": "DR-4-48851644227183C2041D838568E117EC",
		"oracle": {
		"ons": ""
		},
		"type": "oracle",
		"user": "mzadmin",
		"url": "jdbc:oracle:thin:@//127.0.0.1:1521/orcl"
	}