The ifgui command launches the Installation Factory console and creates a build definition XML file that identifies the product to install, the features of the product, and the maintenance packages and other customizations to include in the customized installation package (CIP). The ifgui tool can also create the CIP in connected mode.
The ifgui tool is also referred to as the Build definition wizard for the Installation Factory.
The ifgui command creates a log file that shows whether the build definition file is produced successfully. In connected mode, the log also contains information about the CIP creation. When the build definition file is not successfully built, examine the trace file to determine what is wrong.
The following files record build file definition data:
The tracing and logging output and level are configurable as described in the loglevel and tracelevel parameters.
The success indicator is INSTCONFSUCCESS.
Common problems that can cause failure include mismatched refresh packs, fix packs, and interim fixes, or because of insufficient disk space.
./ifgui.sh -help
./ifgui.sh -loglevel log_level -logfile log_file_path_name -tracelevel trace_level -tracefile trace_file_path_name
ifgui.bat -help ifgui.bat ?
ifgui.bat -loglevel log_level -logfile log_file_path_name -tracelevel trace level -tracefile trace_file_path_name
Using the build definition file to create a customized installation package (CIP)
Use the build definition file in connected mode to create a CIP from within the wizard. Use the build definition in disconnected mode as input to the Installation Factory processing engine to create a customized installation package. See the description of the ifcli command for more information.