WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

ifgui command

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.

Location of the command file

The command file is located in the /bin directory of the directory where you unpack the Installation Factory. The command file is a script named:
  • [AIX] [HP-UX] [Linux] [Solaris] ifgui.sh
  • [Windows] ifgui.bat

Logging

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.

[AIX] [HP-UX] [Linux] [Solaris]

Syntax for the ifgui.sh command

Displaying help for the command:
./ifgui.sh -help
Creating a build definition:
./ifgui.sh 
   -loglevel log_level
   -logfile log_file_path_name 
   -tracelevel trace_level
   -tracefile trace_file_path_name      
[Windows]

Syntax for the ifgui.bat command

Displaying help for the command:
ifgui.bat -help

ifgui.bat ?
Creating a build definition:
ifgui.bat 
   -loglevel log_level
   -logfile log_file_path_name 
   -tracelevel trace level
   -tracefile trace_file_path_name     

Parameters

Supported arguments include:
-? [Windows]
Shows usage information.
-help
Shows usage information.
-logfile log_file_path_name
Identifies the log file. The default value is current_working_directory/logs/log.txt.
-loglevel log_level
Sets the level of logging. The default value is INFO. Valid values are:
  • ALL
  • CONFIG
  • INFO
  • WARNING
  • SEVERE
  • OFF (Turns off logging)
-tracefile trace_file_path_name
Identifies the trace file. The default value is current_working_directory/logs/trace.xml.
-tracelevel trace level
Sets the level of tracing. The default value is OFF. Valid values are:
  • ALL
  • FINE
  • FINER
  • FINEST
  • OFF (Turns off logging)

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.




Related reference
Reference topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rxml_ifgui.html

© Copyright IBM Corporation 2005, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)