ifgui command

The ifgui command launches the IBM WebSphere Installation Factory console and creates a build definition XML file that identifies configuration information about WAS NDs to include in the customized installation package (CIP) or integrated installation package (IIP). The ifgui wizard can create the package in connected mode, or it can create a build definition in disconnected mode.

The ifgui tool is also referred to as the Build definition wizard for the Installation Factory.

Although the ifcli command-line version of the Installation Factory is supported for all 7.0 platforms with the exception of z/OS, the Installation Factory console (ifgui) is supported for a subset of these operating systems. See the IBM Installation Factory for WebSphere Application Server V7.x download page for more information.

[iSeries]

Use Installation Factory on a Windows platform to create installation packages for IBM i. The Installation Factory ifgui does not run on an IBM i platform.

The Installation Factory uses a version of IBM Eclipse SDK that supports 64-bit operating systems in headless mode only without a user interface. As a result, the ifgui command is not supported on 64-bit operating systems even though it may be present.

class="topictitle2">Location of the command file

The command file is located in the /bin, where is the directory where you unpacked the Installation Factory. The command file...

  • [AIX]

    [HP-UX]

    [Linux]

    [Solaris] <p> ifgui.sh

  • [Windows] <p> ifgui.bat

class="topictitle2">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 package 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 fix packs and interim fixes, or because of insufficient disk space.

[AIX]

[HP-UX]

[Linux]

[Solaris] <p>

class="topictitle2">Syntax for the ifgui.sh command

Displaying help for the command: 
./ifgui.sh -help
Creating a build definition: 
./ifgui.sh 
   -loglevel log_level
   -logfile fully_qualified_log_file_path_name 
   -tracelevel trace_level
   -tracefile fully_qualified_trace_file_path_name

[Windows] <p>

class="topictitle2">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 fully_qualified_log_file_path_name 
   -tracelevel trace level
   -tracefile fully_qualified_trace_file_path_name

class="topictitle2">Parameters

Supported arguments include:

-?

[Windows] <p>

Specifies usage information.

-help

Specifies usage information.

-logfile fully_qualified_log_file_path_name

Log file. The default value is /logs/log.txt.

-loglevel log_level

Level of logging. The default value is INFO. Valid values are:

  • ALL

  • CONFIG

  • INFO

  • WARNING

  • SEVERE

  • OFF (Turns off logging)

-tracefile fully_qualified_trace_file_path_name

Trace file. The default value is /logs/trace.xml.

-tracelevel trace level

Level of tracing. The default value is OFF. Valid values are:

  • ALL

  • FINE

  • FINER

  • FINEST

  • OFF (Turns off logging)

Use the build definition file to create an installation package

Use the build definition file in connected mode to create a build definition file and generate the installation package from within the wizard or use disconnected mode to create the build definition file as input for the ifcli command on another machine. See the description of the for more information.


Related tasks

Related reference


Related information
   


Last updated Nov 11, 2010 1:01:09 PM CST