Edit Product Dialog - Launcher Build Page
Launcher is a concept where almost all of the Protection! initialization data (currently presented in standard GUI or Headless code snippet) is placed into the Launcher resource. After Launcher is successfully built Launcher can be loaded at runtime and used to initialize Protection! system. Use of the Launcher provides an easy way to update Protection! configuration (i.e., adding secret storages or changing some other configuration options) without the need to first manually modify source code and then requiring a rebuild of the application for the changes to take effect.
Launcher Build Page provides the developer with the ability to maintain multiple Launcher build configurations. It shows the list of currently available configurations and provides actions to maintain and reorder them. The New/Edit Launcher Build Configuration dialog allows specifying configurations' attributes during creation of a new or changing the existing configuration.
The following configuration's attributes are available:
- "ID" - Indicates unique configuration's ID.
- "Name" - configuration Name
- "Default" - Indicates default configuration. This configuration would be used to build Launcher by default unless specific launcher build configuration is chosen.
- "Target" - Indicates what should be used as a launcher target. The user needs to choose either a file or an archive to generate Launcher.
- "Jar" - If chosen then launcher would be written into the existing jar file as a resource. The exact location where launcher would be created inside the jar file is specified via Entry Name option (see below).
- "File" - If chosen then launcher would be written to a file on the file system.
- "Product Edition" - Indicates for which Product edition Launcher will be built.
- "GUI" - Indicates if Launcher would be build for GUI based application.
- "Headless" - Indicates if Launcher would be build for Headless (GUI-less) application.
- "Verbose Output" - Indicates if verbose output needs to be turned on allowing printing messages and errors to standard output during license reading and checking.
- "Encrypt" - If turned on the generated launcher would be strongly encrypted. Note: encryption must be turned off for building Launchers which may be imported into the Protection! Licensing Server.