Versions Compared

Old Version 2

changes.mady.by.user Jenni Wallin

Saved on

compared with

New Version Current

changes.mady.by.user Jonas Thungren (Deactivated)

Saved on

Key

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

...

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 Usage Engine is

We don't have a way to export this inline extension.

...

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. Only for For Private Cloud installations , adaption of the Ports are neededneed to be adapted as described below.

Rw ui textbox macro
typewarning

Private Cloud - Handling of Ports

If you are running in Private Cloud, you cannot use the ports defined in the values.yaml file. You must use the NodePort number substitutes. You can see the port number substitutes but running the command:

kubectl get services.

In the example below, 9000 is substituted with 30707.

Code Block
$ kubectl get services -n <namespace>

NAME                                              TYPE            CLUSTER-IP        EXTERNAL-IP   PORT(S)                       AGE
mzuepe-operator-controller-manager-metrics-service  ClusterIP       10.102.178.52     <none>        8443/TCP                      154m
mzonline                                        NodePort        10.100.195.106    <none>        80:31270/TCP            platform      154m platform                                        NodePort        10.111.174.222    <none>        9000:30707/TCP,6790:32481/TCP 154m

# Note that in case you use TLS, the web interface port iwll be 443.

...

  1. For AWS installations,  URLs are constructed like <function>.<domain> as shown below.
...
 Note
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/
...
 Info
titleExample - Desktop Launcher URL
Examples. Enter the URL in a web browser. Use https if security is defined:
...
A page with different files to install or start the Launcher will be available in the web browser.
Image Removed 
...
  1. Install the Desktop Launcher double-click the *.exe file or use java -jar to install 
...
  1. the *.jar file.
 Info
...
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 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 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 as shown in the "kubectl get services" example above.