The topology of the cluster is handled differently in the two deployment options (Classical and Containerized). The classical relies on a DigitalRoute developed application called System Topology Registry, while the containerized relies on Kubernetes (or other cluster management tool if ported). Note that classical deployments need a third party product in case high availability is a requirement, while containerized has this feature as part of Kubernetes.

Containerized MediationZone Deployments

Kubernetes (or other cluster management tool if ported), handles all aspects of cluster management of MediationZone:

• Creating, removing, starting, and stopping pico instances.
• Updating attributes of pico instances.
• Making all pico instances of the cluster highly available.
• Viewing cluster details.

For detailed user guides, please visit https://kubernetes.io/docs/home/.

managed by the System Topology Registry.

Classical MediationZone Deployments

The System Topology Registry (STR) provides a central interface for managing the topologythe MediationZone topology, through manual configuration or scripting.

...

The well-defined interface for managing the system topology and controlling processes, in combination with scripted installations of containers, facilitate deployment of in of MediationZone in highly automated environments.

Managing Processes

 processes MediationZone processes can be managed from a central point via text editors, a web GUI, or from the command line. The data format used is HOCON (Human-Optimized Config Notation), a relaxed variant of JSON. Compared to JSON, this format is more oriented for human/manual editing and supports comments.

The figure below illustrates configuration of an Execution Context in the System Administration GUI.

Image RemovedImage Added

Creating Execution Context (EC) in System Administration GUI

...

$ mzsh topo set container:exec1/pico:ec2 '
{
	template:mz.standard-ec
	config {
		properties {
			httpd.port : 9092
		} 
	}
}'

Viewing Runtime Information

The System Administration Interface can be used to view the complete system topology in a graph, or information about specific processes.

Image RemovedImage Added

System Administration GUI - System Overview

The runtime information in the System Administration includes e g running status, JVM statistics, uptime, ports, etc.

Image RemovedImage Added

System Administration GUI - Runtime

...

$ mzsh topo get --format data-only container:main1/pico:platform
{
    "_execution" : {
        "service-members" : [],
        "workflows" : []
    },
    "_loc" : "topo://container:main1/pico:platform",
    "_name" : "platform",
    "_ref" : "topo://container:main1/pico:platform",
    "_ref-parts" : {
        "cell" : "default",
        "container" : "main1",
        "group" : "default",
        "pico" : "platform"
    },
    "_status" : {
        "config" : {
            "hash" : "21449f8e619f18030012f448419bab46",
            "state" : "in-sync"
        },
        "jvm" : {
            "stats" : {
                "cpu" : {
                    "percent" : 0.7685199975967407,
                    "time" : 60870025000
                },
                "gc" : {
                    "count" : 25,
                    "time" : 1535
                },
                "memory" : {
                    "committed" : 634912768,
                    "max" : 954728448,
                    "used" : 135749504
                },
                "system" : {
                    "open-files" : 414
                }
            }
        },
	...}

STR Replication

Changes to the STR are instantly replicated by the Platform process, ensuring that all containers have consistent and valid information.

Image RemovedImage Added

STR Replication