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.
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/uninstalled
The installable cloud launcher is available in two versions: the standard version and the public version.
The standard version of the cloud app launcher will be automatically downloaded when the user runs the application for the first time by accessing the application URL in the Web browser. 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.
The public version of the cloud app launcher is provided separately so that the administrator can get the setup file of the public version and install it to the client. The administrator must have the administrator rights to install the public version so that it can be used by all users on that client machine. The setup file can be obtained from the Web server after it was uploaded, for example, C:\inetpub\wwwroot\CloudAppPublisher\CloudAppInstall [version]\CloudAppLauncherPublic_Installer.exe (or CloudAppLauncherPublic_Installer.msi).
The administrator can directly run the setup file to install or run the following command to silently install the cloud app launcher.
For EXE file:
CloudAppLauncherPublic_Installer.exe /s /AppInstallPath=""c:\appeon_dir\App1"" /CalInstallPath=""%localappdata%\cal_v22""
CloudAppLauncher_Installer.exe /s /AppInstallPath=""c:\appeon_dir\App1"" /CalInstallPath=""%localappdata%\cal_v22""
-
/s - starts the silent installation mode.
-
/AppInstallPath -- (optional) specifies the installation path for the application.
-
/CalInstallPath -- (optional) specifies the installation path for the cloud app launcher.
For MSI file:
CloudAppLauncherPublic_Installer.msi /qn APPINSTALLPATH=""c:\appeon_dir\App1"" CALINSTALLPATH=""%localappdata%\cal_v22""
CloudAppLauncher_Installer.msi /qn APPINSTALLPATH=""c:\appeon_dir\App1"" CALINSTALLPATH=""%localappdata%\cal_v22""
-
/qn - starts the silent installation mode.
-
/APPINSTALLPATH -- (optional) specifies the installation path for the application.
-
/CALINSTALLPATH -- (optional) specifies the installation path for the cloud app launcher.
The administrator can directly run the SilentUninstall.bat file under the installation path to silently uninstall the cloud app launcher.
Note
If the MSI file for the installation is used, you will need to make sure the installation path for the application and the cloud app launcher can be accessed and executed by the end user, otherwise, the application or the cloud app launcher may fail to run. The end user will not be prompted for the permission issue (this is a limitation with MSI file).
If the EXE file for the installation is used, the end user will be prompted to select a different path if s/he has no sufficient rights to install to the specified path for the application or the cloud app launcher; they cannot proceed with the installation process until they select an appropriate path.
|
Standard version |
Public version |
|
|---|---|---|
|
Whether uploaded to the server |
Yes |
Yes |
|
How to download and install |
The setup file is automatically downloaded from the Web server when the user enters the application URL in the browser; and then installed when the user runs the setup file. |
The administrator gets the setup file from the Web server and then installs it to the client machine. |
|
Where to install |
The launcher (as well as the app files and runtime files) will be installed to the local user folder. |
The launcher will be installed to the %programfiles% folder and the app files and runtime files will be installed to the local user folder. |
|
How to run |
The launcher will be installed and run by each user. The launcher starts when the user starts an application, and will stay active all the time (unless manually ended). |
The launcher must be installed by the administrator, and then shared by all users. The launcher will start at the computer start-up, and will stay active all the time (unless manually ended). |
|
Precedence |
If both standard version and public version are installed on the same computer, the public version is always used (even if the user has installed the standard version under his own account). |
|
|
How to upgrade |
Will automatically upgrade. |
Will rely on the administrator to upgrade. If the administrator does not promptly upgrade it to the latest version, when the user runs the application, s/he will be prompted to contact the administrator to upgrade the launcher. |
|
How to uninstall |
Uninstalled by each user. |
Uninstalled by the administrator. |
Are administrator rights required
The standard version of cloud app launcher requires no administrator rights to install and use.
The public version of cloud app launcher requires administrator rights to install. And after that, it can be used by all users without administrator rights.
How multiple versions coexist
The launcher has been re-factored since version 2022, so the 2022 (or later) launcher will not work for 2019 R3/2021 apps, and vice versa. Therefore: (1) The 2022/2022 R2/2022 R3 launcher can co-exist with 2019 R3/2021 launcher on the server and the client; (2) The 2022 launcher will work for 2022 apps only; 3) The 2022 R2 launcher will work for 2022 and 2022 R2 apps; 4) The 2022 R3 launcher will work for 2022/2022 R2/2022 R3 apps.
As to the launchers of version 2019 R3 and 2021, these two launchers 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. View here for more information.
Instead of uploading the default app launcher, you can create your own launcher and upload it.
To create and customize the launcher:
-
Click the Cloud App Launcher Profile button on the PowerClient Toolkit toolbar, or select PowerClient > Cloud App Launcher Profile from the menu bar. The Cloud App Launcher Profiles window appears.
-
In the Cloud App Launcher Profiles window, select an existing profile on the left, and then modify the settings on the right (you can also delete, import, or export a profile).
The Default profile cannot be modified, exported, or deleted.
To create a new launcher profile, you can click the New button.
In the New Launcher Profile window, create the profile with the following settings:
-
Specify a profile name for the new launcher.
-
Select the version of the launcher: standard version or public version. If you are not sure which version to select, refer to the previous section About cloud app launcher for their differences.
-
Specify where to save the launcher profile on the local machine.
-
On the General tab, specify the following settings:
-
the description and product name that will be shown in the Properties page of the launcher EXE file
-
the title, titlebar logo (ICO format), main image (background), update image, and loading image that will be shown during the launcher installation and startup progress
The titlebar logo can be in the ICO format only.
The main image can be in the following formats: JPG, JPEG, PNG, and BMP.
The update image can be in the following formats: JPG, JPEG, PNG, and BMP.
The loading image can be in the GIF format only.
Make sure the path and file name are correct. You can specify an absolute path or relative path of the image. If it is a relative path, it is relative to the path of launcher template, for example, the full path of ".\pcas.ico" is "C:\Program Files (x86)\Appeon\PowerBuilder [version]\Pstools\CloudAppInstall\pcas.ico. The file name is not necessarily the same as the default, for example, you can specify "D:\custom\launcher.ico" as the titlebar logo.
The specified images will be packaged with the launcher. However, if the path or file name is incorrect, then the default image will be packaged.
-
-
On the Advanced Options tab, specify where to install the application on the client. The path in the App path field will be used as the default installation path. If you want to allow the user to select where to install the application during the installation process, you can select "Allow the user to change the path".
-
On the Advanced Options tab, specify where to install the cloud app launcher on the client. The path in the Install path field will be used as the default installation path. If you want to allow the user to select where to install the cloud app launcher during the installation process, you can select "Allow the user to change the install path".
-
If "standard version" is selected, you can specify whether to allow the user to change the installation path of launcher, but the standard version should not be installed to the same location where the public version is installed.
-
If "public version" is selected, you should not allow the user to change the installation path of launcher.
If the end user has no sufficient rights to install to the default or specified path for the application or the cloud app launcher, they will be prompted to select an appropriate path before they can proceed with the installation process.
-
-
On the Signing tab, select whether to digitally sign the launcher executable file (CloudAppLauncher_Installer.exe).
For more information, refer to Signing.
After the executable file is generated and before it is uploaded to the server, PowerBuilder will sign the executable file using your own signing scripts or using the SignTool settings you specified.
Note
If you want to sign your customized Cloud App Launcher using the SignTool utility, ensure that the current Windows OS account that runs the PowerBuilder IDE has permission to access the specified URL of the timestamp server. Otherwise, the signing may fail.
-
The app launcher and the runtime files must be uploaded to the Web server, and then installed to the client when the application is run for the first time. Apps deployed to the same server and directory will use the same app launcher and the same runtime files. There will be only one app launcher in the specified server and directory, although there can be multiple versions of runtime files. The app launcher will be overwritten without notice by the one uploaded later to the same server and directory.
-
In the Upload Cloud App Launcher and Runtime window, select whether to directly upload the app launcher and runtime files to the server or create a zip package and manually upload it to the server later.
-
To directly upload the app launcher and runtime files to the server, select a local server or a remote server where the app launcher and the runtime files will be uploaded.
IMPORTANT: the app launcher and runtime files must be uploaded to the same web root where the application will be deployed. If you have not configured the server yet, follow instructions in Configuring a deployment server to configure the server first.
-
To create a zip package which will be manually uploaded later, specify where the zip package will be created.
-
-
Select a launcher profile from the Launcher profile list box.
You can select the default or customized app launcher.
-
Select the check boxes to upload the runtime files, 32-bit Runtime file, and/or 64-bit Runtime files.
The version of runtime files is determined by the runtime version selected in the IDE > System Options dialog. Multiple versions of runtime files can co-exist on the same server and directory.
-
Click Upload.
Note
When uploading Cloud App Launcher to the server directly, if you receive the "Error code: 6" error, it means that you have no right to write in the server folder. The solution is to run PowerBuilder IDE as administrator.
