FlexApp One applications start out as traditional FlexApp packages which are then bundled with the FlexApp run-time engine to become distributable executable files. To bundle existing FlexApp packages into FlexApp One applications, without importing them into the inventory, complete the following steps:
- Before beginning, ensure that you have copied your FlexApp_One.lic file into the C:\Program Files (x86)\Liquidware Labs\FlexApp Packaging Console\FlexApp One Bundler folder on your FlexApp Packaging Console machine.
- Open the FlexApp Packaging Console and login or select Offline Packaging Mode.
- Click the Create dropdown menu and select Create FlexApp One.
- Click the magnifying glass button to browse for the folder containing the FlexApp Packages you want to create FlexApp One EXE’s from, leaving the Include Subfolders checked-on, and click OK.
- Review the list of FlexApp Packages from which FlexApp One EXE’s will be created and click Create FlexApp One.
- Once the process is complete, click OK and you can then find your FlexApp One EXE’s in each of the original FlexApp Package’s folder.
Sample Bundler Command Line Usage
Alternatively, you can run the Bundle.exe with command line options and specify the FlexApp application folder to bundle into an EXE.
bundler.exe bundle -p "\\Path\To\The\FlexApp\PackageFolder" -f "X:\FA1Bundler\Prod\flexapp.zip" -o "\\Path\To\The\FlexAppOne\OutputFolder" -t "X:\FA1Bundler\Prod\engine.exe" " --licfile ".\flexapp_one.lic" --accepteula --seticon
FlexApp One Bundler Command Line Options
This section covers two sets of command line arguments; one for bundling and another for migrating.
Command Line Arguments when Bundling
The following table shows the command line arguments that are available when bundling existing FlexApp packages into FlexApp One applications.
These arguments are for the Bundler.exe bundle command.
| Option | Description |
|---|---|
| -p <packagefolder> | Specifies the folder for the FlexApp package that should be bundled into a FlexApp One. (Required) |
| -f <flexapp.zip> | Specifies the flexapp.zip to be included in the FlexApp One. (Required) |
| -t <engine.exe> | Specifies the engine.exe to be included in the FlexApp One. (Required) |
| -o <outputfolder> | Specifies the folder in which the FlexApp One application EXE will be created (Required). |
| --licfile <path\licfile,lic> | Specifies the location to the FlexApp_One.lic file. Default: .\ (Current working directory). |
| --seticon | Will set the output file to the package default icon. |
| -i <path\file.ico> | Allows you to specify the icon file that will be used when setting the icon for the output file. Requires --seticon |
| --accepteula | Accept the EULA. (Required) |
| --nocallhome | Disables usage data collection. |
| --plainconsole | Use alternate console text output format. |
| -e <yyyy-mm-dd> | Causes FlexApp One application EXE to expire on the specified date so that it can no longer be executed. |
| -c <cert.pfx> | Digitally sign the FlexApp One with the specified PFX certificate. Note: Certificate must be for Digital Signing and be a Code Signing certificate. Requires saving the PFX password using: Bundler.exe setsigningcredential -p "<pfx password> " |
| --oauth | Require Microsoft Entra ID authentication via OAuth to authorize application access. Requires --appid |
| --appid <app-id> | Application ID (client_ID) of registered app in Azure Portal. Required for --oauth |
| --allowedtenants <domain.name> | Define the Entra ID tenant domain to use during authentication. Optional with --oauthExample: --allowedtenants abc.com --allowedtenants xyz.com |
| -l “<log path>” | Set the log path. Default: "%TEMP%\ProfileUnity" |
Command Line Arguments when Migrating
The following table shows the command line arguments that are available when migrating existing FlexApp One packages to newer FlexApp.zip, Engine.exe, or FlexApp_One.lic files.
These arguments are for the Bundler.exe migrate command.
| Option | Description |
|---|---|
| -p <packagefolder1> -p <packagefolder2> -p <packagefolder3> |
Specifies the folder for the FlexApp package(s) that should be bundled into FlexApp One. Note: At least one is Required |
| -f <flexapp.zip> | Specifies the flexapp.zip to be included in the FlexApp One. (Required) |
| -t <engine.exe> | Specifies the engine.exe to be included in the FlexApp One. (Required) |
| --licfile <path\licfile,lic> | Specifies the location to the FlexApp_One.lic file.Default: .\ (Current working directory). |
| --seticon | Will set the output file to the package default icon. Default: true |
| -i <path\file.ico> | Allows you to specify the icon file that will be used when setting the icon for the output file. Requires --seticon |
| --nocallhome | Disables usage data collection. |
| -e <yyyy-mm-dd> | Causes FlexApp One application EXE to expire on the specified date so that it can no longer be executed. |
| -c <cert.pfx> | Digitally sign the FlexApp One with the specified PFX certificate. Certificate must be for Digital Signing and be a Code Signing certificate. Requires saving the PFX password using: Bundle.exe setsigningcredential -p <pfx password> |
| --oauth | Require Microsoft Entra ID authentication via OAuth to authorize application access. Requires --appid |
| --appid <app-id> | Application ID (client_ID) of registered app in Azure Portal. Required for --oauth |
| --allowedtenants <domain.name> | Define the Entra ID tenant domain to use during authentication. Optional with --oauthExample: --allowedtenants abc.com --allowedtenants xyz.com |
| -l “<log path>” | Set the log path. Default: "%TEMP%\ProfileUnity" |
