Versions Compared

Old Version 3

changes.mady.by.user Kevin Wu

Saved on

compared with

New Version 4

changes.mady.by.user Yeok Hong Ng

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can manage pico instances in one container from another by enabling remote access, using the mzsh command topo setupremote. SSH is used by the pico instances for remote access and the default port used by this protocol is 22. For further information about setting up remote access and how to configure the SSH port, see Remote Access to Containers.

...

Inter Workflow Communication

...

For information on how to setup the Audit Profile, refer to Audit Profile in the Desktop user's guide.

...

  • To allow mzsh, Desktops and ECs to communicate with the Platform, incoming data to, and outgoing data from port 6790 in the Platform Container must be allowed.

  • To allow the Platform Web Interface to be accessed from outside the firewall and for STR synchronization, incoming data to, and outgoing data from the Platform's port 9000 must be allowed.

  • To allow the EC Web Interface to be accessed from outside the firewall, incoming data to, and outgoing data from the EC's port 9090 must be allowed.

  • To enable external access to services on the Platform and the SC, ensure that incoming and outgoing data for the following port ranges are allowed through the firewall:

    • Platform default port range: 5451-5500 (configurable)

    • SC port range: xxxx-xxxx (configurable)

    To allow remote access to Execution Containers, outgoing data must be allowed on port 22.

Type

Port(s)

Open Internally

Open Externally

Platform

6790

9000

Refer to Additional Platform Properties in install.xml for more information.

Default scenario where MediationZone is only used within an internal network.

If it is required to provide platform ports to external scenarios, such as legacy desktop (Java Swing) running on an external network.

Web UI

9001

Refer to Desktop UI Properties for more information.

If all browser users are on an internal network.

Default scenario where Web UI is running on browsers on external network.

Execution Context(s)

9090

Refer to Execution Context Properties for more information.

Default scenario where services depending on EC is used within an internal network.

If it is required to provide access to ECs from an external network.

Example
Prometheus server is deployed on remote network and needs to work with EC in an internal network.

Service Contexts (optional)

Depends on required services.

Refer to Service Context Properties for more information.

Default scenario where services depending on SC is used within an internal network.

If it is required to provide access to SCs from an external network.

Legacy Java Swing Desktop

6790
9000

Default scenario when the legacy desktop is used within an internal network.

If the legacy desktop requires to run from an external network.

Operations REST Interface

9000

Refer to Operations REST Interface for more information.

Default scenario where services depending on Operations REST Interface is used within an internal network.

If it is required to provide access to Operations REST Interface from an external network.

Info

Info!

  • It is recommended to enable the client authentication for security. For more information, refer to Enabling Client Authentication.

  • Consider to provide VPN access for services that require access to 6790 and 9000.
    For example, the access the legacy desktop (Java Swing) remotely.