The Build Definition wizard creates the XML build definition file, which specifies the location for outputting the customized installation package (CIP). The name and location of both files are under your control. The build definition file is always saved to a directory path on the Build Definition wizard machine.
Name the build definition file in the Build definition field.
You can think of the build definition file as a response file for the processing engine. The XML file provides the information that the processing engine needs to locate all of the components for the CIP.
Name the directory where you want to create the CIP in the Customized installation package field. The Installation Factory creates a compressed file containing the CIP and stores the file in the directory name that you specify.
The processing engine reads the CIP location from the build definition file to determine where to store the CIP.
Browse button
You can type directly into each field to identify the file and directory locations, which do not yet have to exist. Or, click Browse in connected mode to search for and select either an existing file (build definition) or an existing directory (customized installation package).
Validation
The file name you choose when creating a new build definition file can be an existing file. You receive a warning message that the file will be overwritten.
The directory for the customized installation package does not have to exist. The processing engine requires an existing directory to be empty, which means no files. The processing engine prompts you for permission to erase existing files in the directory.
Check box for overwriting the content of the CIP directory
The processing engine can erase any files in the CIP directory when it builds the CIP. Select this check box to let the erasure proceed automatically. Otherwise, erase the directory yourself. The processing engine does not build the CIP if you do not allow the tool to erase any existing files.