Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The Desktop Client is started using the Desktop Launcher. 

Desktop via Launcher

Depending on how Usage Engine is installed, the method of connecting them to the platform varies slightly. The basic functionality is described here, and the more advanced settings are described in Desktop Launcher Settings(3.3).

To install and run the Desktop Launcher:

  1. Prerequisite: Download and install Java 17 on the PC that you will use the Desktop on. Both JRE and JDK work.

  2. If LoadBalancer going to be used, special considerations concerning ports are needed, for more information see: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/

  3. Only for Private Cloud installations, adaption of the Ports are needed.

  1. Only for AWS installations,  URLs are constructed like <function>.<domain>. See below

AWS - Accessing the Environment

If you use AWS you must always define the type of interface directly in the URL as shown below:

  • Web interface: https://mzonline.<domain>/

  • Platform: https://platform.<domain>:9000/

  1. To download the Desktop Launcher, enter this URL in a web browser: http://<host>:<mz.webserver.port>/launch/desktop . The port is default 9000.

    Example - Desktop Launcher URL

    Examples. Enter the URL in a web browser. Use https if security is defined:

  2. A page with different files to install or start the Launcher will be available in the web browser.

  3. To install the Desktop Launcher, for Windows, download the exe file and double-click to install it. Alternatively download the OS independent  jar file and use java -jar to install it.

    Example - Desktop Launcher via java -jar

    $ java -jar standard standard-mzx-launcher-1.1.4.jar

  4. The Launcher interface will be visible, and you can add the Instances you want to use.
      

    - Add the instance, by defining the Host, Port and a Name. Select Secured Connection if the platform's web interface is defined to use https.
    - For Private Cloud, set Port to the NodePort number substitute for 9000 and Host to the cluster node. Example below.
    - For AWS, define platform.<domain> For the Host.

  5. In the case you are using Private Cloud or pico.rcp.platform.port different from 6790, the Platform RCP port needs to be changed. Click settings    on the Desktop instance and update the pico.rcp.platform.port. For Private Cloud Use the NodePort number substitute for 6790. It is 32481 in the "kubectl get services" example above.

  • No labels