WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


The ifgui command

The ifgui command launches the IBM® WebSphere® Installation Factory console which can be used to create a build definition XML file that identifies the product to install, the features of the product, the maintenance packages, and other customizations to include in a customized installation package (CIP). The ifgui tool can, when used in connected mode, also create the CIP directly.

Purpose

Note: The Installation Factory console is sometimes referred to as the Build Definition wizard.
The ifgui command gives you access to the Installation Factory console, which is the simplest method of creating build definition files.

Location

The ifgui command file is located in the /bin directory of the directory where you unpack the Installation Factory. The command file is a script named:

For AIX operating systemFor HP-UX operating systemFor Linux operating systemFor Solaris operating system ifgui.sh

For Windows operating system 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:

  • IF_working_directory/logs/trace.xml is a detailed trace log in XML format.
  • IF_working_directory/logs/log.txt is the log file.
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 insufficient disk space.

Syntax for ifgui.sh

For AIX operating systemFor HP-UX operating systemFor Linux operating systemFor Solaris operating system

To display help:

./ifgui.sh -help

To create a build definition:

./ifgui.sh 
   -logLevel log_level
   -logFile log_file_path_name 
   -traceLevel trace level
   -traceFile trace_file_path_name        

Syntax for ifgui.bat

For Windows operating system

To display help:

.\ifgui.bat -help
.\ifgui.bat -?

To create 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

-?
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 for logging of messages. Valid values for log_level are:
  • ALL
  • CONFIG
  • INFO
  • WARNING
  • SEVERE
  • OFF (Turns off logging)
The default value is INFO.
-traceFile trace_file
Identifies the trace file. The default value is current_working_directory/logs/trace.xml.
-traceLevel trace_level
Sets the level of tracing. Valid values for trace_level are:
  • ALL
  • FINE
  • FINER
  • FINEST
  • OFF (Turns off tracing).
The default value is OFF.

Usage

Use the build definition file in connected mode to create a CIP from within the wizard. In most instances it is advisable to use the build definition wizard in connected mode, even if you are creating a CIP for a different operating system. Use the build definition in disconnected mode as input to the Installation Factory processing engine to create a customized installation package. See the ifcli command for more information.

reference Reference topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/rins_ifgui.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).