Starting and Stopping the System

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

Starting the System

  1. Login as mzadmin on the host where the Platform Container is installed.

  2. Ensure that the environment variables are set correctly:

Variable

Description

Variable

Description

MZ_CONTAINER

Example value: container0

This environment variable specifies an identifier for the installed container. Each container in your MediationZone system must have a unique identifier.

MZ_HOME

Example value: /opt/mz

This environment variable specifies where the MediationZone software is installed.

JAVA_HOME

Example value: /opt/jdk/jdk-17.0.2

This environment variable specifies where the JDK is installed.

PATH

This environment variable specifies the search path.

The search path must contain the following directories: $JAVA_HOME/bin:$MZ_HOME/bin

  1. Start the Platform by entering the mzsh startup command:

    $ mzsh startup platform 

    If you have configured SCs or ECs in the Platform container, you can add the names of these pico instances to the startup command. The Platform must be started before any ECs or SCs.

Example - How to Start the System

Enter the following command to start the Platform and an EC (ec1) in the Platform Container:

$ mzsh startup platform ec1

  1. Start other pico instances  that are required for execution, i e ECs or SCs.

    If you have enabled remote access to the containers in your system, you can start pico instances on other containers with the the mzsh system start command:

    $ mzsh system start container:<container regexp>/pico:<pico name regexp>

Hint!

The Platform will be started if it is not already running.

Note!

Set your desired environment variables in $MZ_HOME/bin/mzshr.env as this file will be loaded with local variables. Add the desired profiles, such as ". /home/mzadmin/.profile_mz".

If you have not enabled remote access, you must login to each container host and start the pico instances with the mzsh startup command.

Stopping the System

  1. Log in as mzadmin on the host where the Platform Container is installed.

  2. Make sure that the environment variables are set correctly:

Variable

Description

Variable

Description

MZ_CONTAINER

Example value: container0

This environment variable specifies an identifier for the installed container. Each container in your MediationZone system must have a unique identifier.

MZ_HOME

Example value: /opt/mz

This environment variable specifies where the MediationZone software is installed.

JAVA_HOME

Example value: /opt/jdk/jdk-17.0.2

This environment variable specifies where the JDK is installed.

PATH

This environment variable specifies the search path.

The search path must contain the following directories: $JAVA_HOME/bin:$MZ_HOME/bin

  1. Stop all ECs, and SCs.

If you have enabled remote access to the containers in your system, you can stop pico instances on other containers with the the mzsh system stop command:

If you have not enabled remote access, you must login to each container and stop the pico instances with the mzsh shutdown command.

  1. Stop the Platform by entering the mzsh shutdown command:

    The Platform must be the last of the pico instances to shut down. The reason for this is that the mzsh shutdown and mzsh system stop commands are issued through the Platform.