ifcli command

 

The ifcli command-line tool runs on any supported operating system. The ifcli tool accepts a build definition XML file as input and invokes the Installation Factory processing engine. The processing engine interprets the XML file, locates the product source files and maintenance packages, and then creates a customized installation package (CIP).

The ifcli tool is also referred to as the command-line interface tool or the command-line invocation tool for the Installation Factory. Running the ifcli tool and installing the CIP are supported for the following architectures:

HP PA-RISC

The Installation Factory ifcli tool runs on 32-bit HP-UX 11iv2 kernels on PA-RISC platforms.

The CIP for 32-bit WAS products also provides 64-bit compatibility support for installing on 64-bit HP-UX 11iv2 kernels on PA-RISC hardware platforms.

HP Itanium

The Installation Factory ifcli tool runs on 64-bit HP-UX 11iv2 kernels on Itanium platforms.

IBM PowerPC32

The Installation Factory ifcli tool runs on 32-bit AIX 5L 5.1 systems, AIX 5L 5.2 systems, AIX 5L 5.3 systems, and Linux systems.

The CIP for 32-bit WAS products also provides 64-bit compatibility support for installing on 64-bit AIX or Linux kernels running on 64-bit pSeries hardware platforms.

IBM p5 and pSeries Power4

The Installation Factory ifcli tool runs on AIX System p5 and pSeries Power4 - 64 bit or 64-bit Linux kernels.

Intel IA32

The Installation Factory ifcli tool runs on 32-bit Intel and AMD hardware platforms running 32-bit Linux kernels or 32-bit Windows kernels.

The CIP for 32-bit WAS products supports Windows 2000 Advanced Server SP4, Windows 2000 Server SP4, Windows 2000 Professional SP4 (development only), Windows Server 2003 Datacenter, Windows Server 2003 Enterprise, Windows Server 2003 Standard, and Windows XP Professional SP1a (development only) on 32-bit Intel and AMD platforms.

IBM S/390

The Installation Factory ifcli tool runs on 31-bit mainframe hardware platforms running 31-bit Linux kernels.

The CIP for 31-bit WebSphere Application Server products also provides 64-bit compatibility support for installing on 64-bit Linux kernels on zSeries platforms.

IBM System z9 and zSeries

The Installation Factory ifcli tool runs on Linux z9 and zSeries - 64 bit.

Opteron / EM64T

The Installation Factory ifcli tool runs on Opteron or EM64T hardware platforms running 64-bit Linux kernels, Windows 2003 x64 editions, or the 64-bit Solaris 10 operating system kernel.

Sun SPARC

The Installation Factory ifcli tool runs on 32-bit Solaris 9 and Solaris 10 operating system kernels on SPARC and UltraSPARC 60 platforms.

The Installation Factory ifcli tool also runs on the 64-bit Solaris 10 operating system kernel on SPARC platforms.

The CIP for 32-bit WebSphere Application Server products provides 64-bit compatibility support for installing on 64-bit Solaris 9 and Solaris 10 kernels.

 

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:

• ifcli.sh

• ifcli.bat

 

Logging

The ifcli command creates a build log file that shows whether the customized installation image is produced successfully. When the CIP is not successfully built, examine the trace file to determine what is wrong.

The following files record CIP creation data:

• trace.xml is a detailed trace log in XML format

• log.txt is the log file

The tracing and logging output and level are configurable as described in the logLevel and traceLevel parameters.

 

Syntax for the ifcli.sh command

Displaying help for the command:

./ifcli.sh -help

Creating a customized installation package:

./ifcli.sh -buildDef build_definition_file 
   -silent
   -logLevel log_level
   -logFile log_file_path_name 
   -traceLevel trace level
   -traceFile trace_file_path_name                  

 

Syntax for the ifcli.bat command

Displaying help for the command:

ifcli.bat -help
 ifcli.bat ?

Creating a customized installation package:

ifcli.bat -buildDef build_definition_file 
   -silent
   -logLevel log_level
   -logFile log_file_path_name 
   -traceLevel trace level
    -traceFile trace_file_path_name     

 

Parameters

Supported arguments include:

-?

Shows usage information.

-buildDef build_definition_file

Identifies the build definition file that the Build Definition wizard creates.

-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)

-silent

Specifies that the processing engine runs in silent mode, without displaying results to the console.

-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)

Use the customized installation package to install the product

Use the Installation Factory installer program for WebSphere Application Server products to install a customized installation package for a WebSphere Application Server product. Each supported product has its own installer program. See the install command for more information.

---

 

Related tasks

Developing and installing customized installation packages

 

Related Reference

 

Related information

Build definition file
install command

 

Reference topic