Upload the cloud app launcher and the runtime files

Table of Contents

About cloud app launcher

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. The app launcher and the runtime files will be used by all apps that are deployed to the same server and directory.

Note: 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.

To upload the app launcher and runtime files:

  1. Select Tools>Upload Cloud App Launcher from the menu bar. The Upload Cloud App Launcher and Runtime window appears.


  2. In the Upload Cloud App Launcher and Runtime window, select whether to directly upload the app launcher and runtime files to the server or only 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.

    • To create a zip package which will be manually uploaded later, specify where the zip package will be created.

    IMPORTANT: the app launcher and runtime files must be uploaded to the same server and directory where the application will be deployed. If you have not configured the server yet, follow instructions in Configure the Web server for deployment to configure the server first.

  3. Select the runtime files (32-bit and/or 64-bit) to upload.

    The version of runtime files is determined by the runtime version selected in the IDE > System Options. Multiple versions of runtime files can co-exist on the same server and directory.

  4. Select or create an app launcher to upload.

    You can select an existing app launcher from the Launcher profile list:

    • Default_WithoutService -- This profile specifies the launcher without the background service. It contains the following default settings:

      • Launcher without background service is selected.

    • Default_WithServiceSingle -- This profile specifies the launcher with the background service which supports single Windows user by default. It contains the following default settings:

      • Launcher with background service is selected.

      • Single user is selected.

    • Default_WithServiceMulti -- This profile specifies the launcher with the background service which supports multiple Windows users by default. It contains the following default settings:

      • Launcher with background service is selected.

      • Multiple users is selected.

    • Default_Both_WithServiceSingle -- This profile specifies the launcher with the background service and the launcher without the background service; and the launcher with the background service supports single Windows user by default. This profile contains the following default settings:

      • Launcher without background service is selected.

      • Launcher with background service is selected.

      • Single user is selected.

    • Default_Both_WithServiceMulti -- This profile specifies the launcher with the background service and the launcher without the background service; and the launcher with the background service supports multiple Windows users by default. This profile contains the following default settings:

      • Launcher without background service is selected.

      • Launcher with background service is selected.

      • Multiple users is selected.

    Or you can create your own launcher by clicking the Create button, if you want to customize the launcher settings.

    • Specify a profile name for your new launcher.

    • Specify where to save your new launcher on the local machine.

    • On the General tab, specify the title and the logo (ICO format) that will be shown in the launcher.

    • 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".

      IMPORTANT: If you want to set a different path as the default path instead of %AppData%\PBApps, you should NOT include the system variable (such as %windir%, %temp% etc.) other than %AppData%, because currently only the %AppData% variable is supported.

    • On the Advanced Options tab, specify which app launcher will be uploaded and installed: launcher without background service, or launcher with background service, or both. When Launcher with background service is selected, you can specify the launcher with background service supports single Windows user by default or supports multiple Windows users by default, and/or if you want to allow the user to select which user option to support during the installation process, you can select "Allow the user to change the option".

    • On the Signing tab, select whether to digitally sign the launcher executable file (CloudAppLauncher_Installer.exe).

      If you want to digitally sign the launcher executable file, you can specify the settings required for signing under the "Use the SignTool utility from the Windows SDK" option, for example, SignTool location, signing certificate, certificate password, signature algorithm, and URL of the time stamp server. And make sure Microsoft’s SignTool has been installed on the current machine.

      Or you can place the signing scripts in a file (with file extension as .cmd) and then select the file for the "Use your own signing script" option. For example, to sign the executable file (CloudAppLauncher_Installer.exe) using Microsoft’s SignTool, you may create a cmd file that includes the following scripts:

      signtool.exe sign /f mycert.pfx /p password /d "My app launcher" /du http://www.mytest.com /fd sha256 /tr "http://timestamp.digicert.com" /td sha256 CloudAppLauncher_Installer.exe

      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.


    Tip

    To remove a launcher profile, go to the path where the launcher is saved (by default, C:\Users\appeon\AppData\Roaming\CloudAppLauncher), go into the folder which corresponds to the launcher version and then delete the sub-folder that is named after the profile.