Starting and Managing Desktop Client (4.0)

Owned by Jenni Wallin
Last updated: Feb 13, 2024 by Jonas Thungren (Deactivated)
3 min read

The Desktop Client is started using the Desktop Launcher, which is started by running an executable file that can be downloaded from the Desktop Online User Settings menu, see User Settings (4.0). Open the Downloads dialog from the User Settings menu, and click on the file to download. There are two executable files available; one generic *.jar file and one Windows specific *.exe file.

Prerequisite

The Java version stated in System Requirements - Private Cloud(4.0) needs to be installed to be able to use the Desktop Launcher and Desktop Client.

Desktop via Launcher

Depending on how Global variable macro (Development) is installed, the method of connecting to the platform varies slightly. The basic functionality is described here, and the more advanced settings are described in Desktop Launcher Settings(4.0).

To install and run the Desktop Launcher:

  1. If LoadBalancer is 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/.

  2. For Private Cloud installations the Ports need to be adapted as described below.

  1. For AWS installations,  URLs are constructed like <function>.<domain> as shown below.

AWS - Accessing the Environment

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

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

  1. Install the Desktop Launcher double-click the *.exe file or use java -jar to install the *.jar file.

Example - Installing Desktop Launcher with java -jar

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

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

  2. In 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 as shown in the kubectl get services example above.