[Incident]: Some users report they are unable to access the case portal. Please see this community notice for more information.

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Using a BuildProperties.xml File

Using a BuildProperties.xml File


Information on how to use a BuildProperties.xml file for building installers.


You can use a build properties XML file, such as BuildProperties.xml, to pass build properties to the command-line builder in a single file. To use this properties file, pass the -p argument with the path and name of the build properties file to build.exe:
build.exe C:\MySetups\MyProduct.iap_xml -p C:\Path\BuildPropeties.xml
If you do not provide an absolute path to your build properties file, the builder looks for it in the same directory as your project. The settings that are specified in the .xml file override the build settings in the project.

InstallAnywhere also supports the use of Ant properties in buildproperties.xml. An Ant property can be defined in the buildproperties.xml using:
<property name="ia.home" value="D:\\IA_Codebase\\main" />


Many of the settings that you can configure in the Advanced Designer can also be set in a BuildProperties.xml file. The following tables correlate the options in the Advanced Designer with settings in the BuildProperties.xml file.
OptionFile Setting
General Settings > Send stderr toInstallerStdErrRedirect="<path_to_file>"
General Settings > Send stdout toInstallerStdOutRedirect="<path_to_file>"
Platforms > Default UNIX Installer UI Mode > Installer UI ModeUnixDefaultUI="<Silent/GUI/Console>"
Platforms > Default Windows UI Mode > Installer UI ModeWindowsDefaultUI="<Silent/GUI/Console>"
Platforms > Default Windows UI Mode > Installer UI Mode (Pure 64-bit)Windows64DefaultUI="<Silent/GUI/Console>"
JVM Settings > Valid VM listInstallerValidVMList="<1.5+, 1.8*>"
JVM Settings > Minimum Heap SizeInstallerInitialHeapSize="<16777216>"
JVM Settings > Maximum Heap SizeInstallerMaxHeapSize="<50331648>"
Look & Feel Settings > Auto populate labels when savingAutoPopulateLabels="<true/false>"
Components > Auto-clean when buildingAutoCleanComponents="<true/false>"
Build Installers > Select Build ConfigurationCreate a <configuration> element for each build configuration that you want to build, using the following syntax:
<configuration name="name_of_build_configuration">
<webInstaller enable="true/false" optimize="true/false">
<cdRomInstaller enable="true/false" optimize="true/false" />
<mergeModule enable="true/false" optimize="true/false" readOnly="true/false" />

<target platform="aix/hpux/solaris/hpux/unixwithvm/macosx/java/unix/windows"

Regarding each <target> element, note the following:
? Each <target> element appends one new target to those already in the build configuration.
? There can be multiple <target> elements.
? The outputDir and bundledVM attributes are optional.
? Each <target> element must include a buildWithVM attribute, a buildWithNoVM attribute, or both.
Important: The following subelements of the <configuration> element can also be specified outside of a <configuration> element. However, those elements defined within a <configuration> element override those defined elsewhere.
Build Installers > Build Output LocationBuildOutputLocation="<path_to_directory>"
[Working Directory]BuildWorkdirLocation="<path_to_directory>"
Note: The working directory, which is used to store all temporary files (such as the build log and the locales directory) is set by default to the InstallAnywhere project directory. It is not specifically set in the Advanced Designer user interface.
Build Targets > OS XBuildMacOSXWithVM="<true/false>"
Build Targets > WindowsBuildWindowsWithVM="<true/false>"
Build Targets > Windows_Pure_64_BitBuildWindows64WithVM="<true/false>"
Build Targets > AIXBuildAIXWithVM="<true/false>"
Build Targets > HP-UXBuildHPUXWithVM="<true/false>"
Build Targets > LinuxBuildLinuxWithVM="<true/false>"
Build Targets > SolarisBuildSolarisWithVM="<true/false>"
Build Targets > Unix (All)BuildUnixAll="<true/false>"
Build Targets > UNIX_with_VMBuildNamedUnixWithVM="<true/false>"
Build Targets > Other Java-Enabled PlatformsBuildPureJava="<true/false>"
[Not available in the Advanced Designer]OverrideAllPlatformSettings="<true/false>"
Distribution > Build Web InstallersBuildWebInstaller="<true/false>"
Distribution > Optimize [Web] Installer Size by Platform and TagsOptimizeWebInstaller="<true/false>"
Distribution > Web page displays inThis option is set within a <webInstaller> element inside of a build configuration element, <configuration>:
<configuration name="<name_of_build_configuration>">
Distribution > Build CD-ROM installersBuildCDROMInstaller="<true/false>"
Distribution > Optimize [CD-ROM] Installer Size by Platform and TagsOptimizeCDROMInstaller="<true/false>"
Distribution > Build Merge Module TemplateBuildMergeModule="<true/false>"
Distribution > Optimize Merge Module/Template Size by Platform and TagsOptimizeMergeModule="<true/false>"
Distribution > Read OnlyBuildReadOnlyMergeModule="<true/false>"

Additional Information

InstallAnywhere includes a build properties file template named BuildProperties.xml:
This template file provides a sample of all possible build settings; you can use it as a template to meet your build requirements.

Add Supported Locales At Build Time Through Ant Or A Build Properties File
Setting the Product Version at Build Time
Labels (1)
Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Nov 12, 2018 06:54 PM
Updated by: