All servers, processes, and threads related to an executing MediationZone instance are controlled and monitored using the Pico Manager. The Pico Manager is used to restrict access rights to trusted hosts. It also enforces potential restrictions in regards to hardware configurations that might apply for workflows and applications. Using the Pico Manager, the system administrator can register new hosts, and disable/enable access to the MediationZone Platform for existing ones.
The Execution Context (EC) and Execution Context Standalone (ECSA) are types of pico processes that can be assigned to groups. These groups simplify transfer of configurations between systems by providing an added layer of abstraction. For instance, the execution settings of a workflow configuration can be setup for a group instead of several individual ECs. This is useful since the name and number of ECs may differ between systems.
The Pico Viewer provides the ability to monitor executing processes and threads, providing information such as category, start time, memory consumption and availability.
Example of Pico Management usage
In containerized solution, EC and ECSA is externally provision and dynamically register to platform. Each group will match the EC / ECSA based on their prefix. Static pico is not allow once Dynamic mode is selected.
Example of Pico Manager for dynamic EC group definition.
Example of Pico Viewer usage
To improve security, MediationZone can be configured to deny any new Desktop client access to the system until the system administrator has registered the IP address in the Pico Manager.