Module Editor Using the editors of the Application Composer, module instances of the module tree can be configured and parameterized. The available editors of the module instance open by means of doub

I/O This dialog provides information about the inputs and outputs of the module. Inputs and outputs describe the I/O demand of the modules and can be connected to the following: Inputs and outputs of

Section: IO The input and output definition can be done in this section. All defined inputs and outputs are available in the Map I/Os . SEC IO //optional: yes, modifier: [UPDATE] SEC Input : <input id

Command: Create Clean Sandbox from Setup Symbol: Function : The command opens the Create Clean Sandbox from Setup dialog. You configure which setup (available installation) should be stored as a clean

Command-Line Interface :

Command: --addSandbox Function : The command adds a sandbox to the settings. Call : APInstaller.CLI Table 11 . Options --targetDirectory <string> Required Directory where the sandbox is located A high

Command: --canCreateInstallation Function : The command checks if an installation can be created with the specified version. Call : APInstaller.CLI Table 12 . Options --version <version> Required Setu

Command: --createInstallation Function : The command creates a new installation according to the command-line options. Call : APInstaller.CLI Table 14 . Options --channel <channel> Name of the setup c

Command: --createInstallationFromFile Function : The command creates a new installation. Call : APInstaller.CLI Table 15 . Options --sourcefile <source file> Required Fully qualified path to a setup f

Command: --discoverAddOnUpdates Function : The command finds all updates for installed add-ons in the specified channel. This function is only possible once a day, unless the "--force" option is used.