Starting the System

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

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

    

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

    

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

   
   
   

   
   
   

   
   
   

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

   $ mzsh startup <pico-name-1> <pico-name-2> <...>

   
   
   

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:

   
   
   
   

3. 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:

   $ mzsh system stop container:<container regexp>/pico:<pico regexp>

   
   
   

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

   $ mzsh shutdown <pico-name-1> <pico-name-2> <...>

    

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

   $ mzsh shutdown platform  

   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.