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.
We 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.
Note: The number of characters in the CIP build directory must be no more than 30 characters.
The processing engine reads the CIP location from the build definition file to determine where to store the CIP.
Browse button
We 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 (CIP).
Validation
Validation will be performed when you click Next.
The build definition file will be created automatically. If the specified file already exists, a warning dialog will pop up when you click Finish verifying you want to overwrite the file.
The directory for the CIP will be created automatically. If the specified directory already exists, a warning dialog will pop up when you click Finish verifying you want to overwrite the current contents.
Related information
Developing and installing customized installation packages Build Definition wizard panels Package identification Product installation image