Configuring Applications

Applications are configured on the Screens & and actions step.

The top-level nodes represent the different applications that can be configured for the project. There are 3 types of applications:

Each installer application has a startup sequence of actions. Those actions are executed before the installer application presents a user interface. If any of these actions fails and has a "Quit on failure" failure strategy, the installer application will not be shown.

Properties of installer applications

Common properties of installer applications are:

Custom applications as well as the uninstaller are added to the distribution tree and have additional related properties:

The remaining properties that are specific to the installer are:

Finally, custom installer applications have the following additional properties:

Configuring installer variables

The second tab in the configuration area for installer applications is the Installer variables tab. Here, you can check the bindings for all detected installer variables and pre-define installer variables. For more information, see the help topic on variables.

An additional feature with respect to the variable selection dialog is that you can navigate to a binding by selecting an element in the binding tree at the bottom and click on the Go To Selection button.

Launcher integrations

Custom installer applications have a Launcher integrations tab in the configuration area that helps you to start them when launchers are executed.

One way to start an installer application is programmatically, by using the install4j API. To get the code snippet for starting the selected installer application, click on the Start integration wizard button. The integration wizard will present a number of options that control the condition and possible call backs from the installer application.

Another way to start an installer application is automatically, by defining a launch schedule and a launch mode. The launch schedule is one of

The launch mode is one of

Just like with the API, the installer application can be started in the launcher process itself or in a new process. By default, the installer application is started in the same process. If the "Blocking at start up" or "Non-blocking at start up" launch modes are selected, the look and feel is set to the system look and feel. For the "When first window is shown" launch mode, the look and feel is not changed, so your own look and feel will be used. When the installer application is executed in the same process, the "Shutdown calling launcher" action has a different effect: The whole process will be terminated when the installer application exits.

By default, the selected installer application is started for all launchers in your project. If this is not desired, you can restrict the integration to selected launchers. Note that if "All launchers" is selected and the project is merged into another project, the integration will be performed for all launchers in the main project as well.