The Cloud App Launcher is a launcher program that must be first installed to the user’s machine. It facilitates the initial installation and subsequent updates of your PowerBuilder applications over HTTP/HTTPS.
There are two launcher types. You can determine which type of cloud app launcher you want to upload to the server:
-
Launcher without background service: This launcher program does NOT use a background service. As such, it should be easier to install and use and does not require administrator rights. However, it has certain dependency on the browser, which may result in different installation experience depending on the browser used and its configuration. If there are multiple users on the client machine, the launcher will need to be installed for each user.
-
Launcher with background service: The launcher program uses a background service. If there are multiple users on the client machine, the launcher will need to be installed for each user, and only the first installation requires administrator rights to install and start the service. If the launcher is installed on the machine for the first time by a user without administrator rights, a window will pop up for inputting the administrator user name and password; after that, the other users also need to install the launcher but they do not need to have administrator rights, and all users will use the service started by the first installation. This launcher type does NOT have dependency on the browser.
Why cloud app launcher is needed
The cloud app launcher works as a "helper" application that installs, starts, and updates the installable cloud app over HTTP/HTTPS, besides that the cloud app launcher can be opened by the Web browser, therefore it enables the installable cloud app to be started through a Web browser (the Web browser launches the cloud app launcher; and then the cloud app launcher launches the installable cloud app).
How cloud app launcher is installed
When the user runs the application for the first time in the Web browser, the setup file of the cloud app launcher (CloudAppLauncher_Installer.exe) will be automatically downloaded from the Web server (if download does not start automatically, the user will need to click the Download the Launcher button to download the setup file). After that, the user will need to run the setup file to install the cloud app launcher. Some users may not be able to install software on their computers without the assistance of an administrator. In such case, their administrator can get the setup file of the cloud app launcher from the Web server Web root (for example, C:\inetpub\wwwroot\CloudAppPublisher\CloudAppInstall\CloudAppLauncher_Installer.exe) and install the cloud app launcher to the machine before the user runs the application.
The administrator can run the following command to silently install the cloud app launcher.
CloudAppLauncher_Installer.msi /qn
CloudAppLauncher_Installer.exe /s
When and why administrator rights are required?
When the cloud app launcher is first installed on the client, it needs to add the following entries to the registry:
-
A registry entry for the protocol
-
A registry entry for starting the launcher
-
A registry entry for information that will be used by uninstall
Adding entries to the registry does not need administrator rights, unless the launcher with the background service which supports multiple Windows users (that is, the Default_WithServiceMulti or Default_Both_WithServiceMulti launcher) is installed, in such case, the launcher must be registered using administrator rights, so that the launcher can be started as a system-level service and used by all Windows users.
How multiple versions coexist
Currently, the two versions of cloud app launcher: 2019 R3 and 2021 will not coexist on the Web server and the client; only one of them will exist (either 2019 R3 or 2021). And the application deployed in 2019 R3 or 2021 can work with either of them.
-
If the client already has the 2019 R3 launcher, when running an app from a Web server that contains the 2021 launcher, the 2019 R3 launcher at the client will be upgraded to 2021.
-
If the client already has the 2021 launcher, when running an app from a Web server that contains the 2019 R3 launcher, because the launcher at the server is of lower version, the client will still use the 2021 launcher.
-
No matter the client has the 2019 R3 or 2021 launcher, the launcher can support the running of applications deployed from either 2019 R3 or 2021.
|
The IDE version used to deploy PowerClient or PowerServer projects |
The Launcher that must exist at the web server |
The Launcher that shall run at the client |
|---|---|---|
|
2019 R3 (PowerClient only) |
Either 2019 R3 or 2021 (only one version will exist) |
Either 2019 R3 or 2021 (only one version will exist) |
|
2021 |
Either 2019 R3 or 2021 (only one version will exist) |
Either 2019 R3 or 2021 (only one version will exist) |
Note: the launcher for version 2022 will be refactored, so the 2022 launcher will not work for 2019 R3 and 2021 apps, and vice versa. Therefore: (1) The 2022 launcher can co-exist with 2019 R3 or 2021 launcher at the Web server and also at the client side; (2) The 2022 launcher will work for 2022 apps only.
