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


The ifcli command

The ifcli command-line tool invokes the Installation Factory processing engine for a specified build definition file. The processing engine then creates a customized installation package (CIP).

Purpose

The ifcli command-line tool takes 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).

Location

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:

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

For Windows operating system 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 ifcli.sh

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

To display help:

./ifcli.sh -help

To create 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 ifcli.bat

For Windows operating system

To display help:

.\ifcli.bat -help
.\ifcli.bat -?

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

For Windows operating system -?
Shows usage information.
-help
Shows usage information.
-buildDef build_definition_file
Identifies the build definition file created by the Build Definition wizard.
-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.
-silent
Specifies that the processing engine runs in silent mode, without displaying results to the console.
-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 ifcli command to create a customized installation package for a WebSphere® ESB product from a build definition file.

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_ifcli.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).