Instead of uploading the default app launcher, you can create your own launcher and upload it.
To create and customize the launcher:
-
In the PowerServer project painter, select the Deploy > Advanced tab. Click the Configuration button. The Cloud App Launcher Profiles window appears.
-
Click the New button to add a new launcher profile. (You can also click the Delete icon after the profile to remove it.)
In the New Launcher Profile window, create the profile with the following settings:
-
The name for the new launcher profile.
-
The location to save the launcher profile on the local machine.
-
The version of the launcher (Standard or Public). If you are not sure which version to select, refer to the previous section About cloud app launcher for their differences.
-
On the General tab:
-
On the Advanced Options tab:
-
The install location of 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".
-
The install location of 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. However, the standard version should not be installed to the same location as the public version.
-
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).
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.
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.
-
To modify the launcher profile:
-
In the Cloud App Launcher Profiles window, select an existing profile on the left, and then modify its settings on the right.
-
Click Apply to save the settings.
-
Click Re-Create to generate the launcher again with the changed settings.
If you have made any change to the launcher settings, you must create the launcher again before uploading it to the server.
