Mode selection - WAS 6.x

 

+

Search Tips   |   Advanced Search

 

 

Overview

When the Build Definition wizard has access to the product installation image, maintenance packages, and other components required to create the customized installation package (CIP), that is called connected mode.

The Build Definition wizard can validate the files that are provided as input and optionally generate the CIP in addition to creating the build definition file. If the product installation image, maintenance packages, and other components are not accessible because they are on a separate machine, the Build Definition wizard can only be used in disconnected mode, where a build definition file for a target platform can be created, but no validation is performed. The build definition file can be copied to the target machine and used as input to the ifcli command to actually generate the CIP.

Choose connected mode when the Build Definition wizard and the processing engine run on the same machine. Choose disconnected mode when the Build Definition wizard is creating a build definition file for use on another machine.

 

The mode affects component location specifications

In connected mode, specify local file paths for all components. The processing engine that builds the CIP is also on this machine. Therefore, the processing engine can access the local components.

In disconnected mode, specify component locations in terms of the target machine, where the processing engine will run to build the CIP.

For example, suppose that the product installation image is on the target machine in...

/tmp/IBM/WASimage

Specify the location in terms of the target machine where the processing engine must find the product image to include in the CIP.

 

The mode affects component validation

The Build Definition wizard can validate connected installation images, maintenance packages, and other components while creating the build definition file because everything is on the same machine.

When running in disconnected mode, the Build Definition wizard does not attempt to access components and cannot verify the components. In such a case, the Installation Factory relies on the processing engine to verify all components. The processing engine verifies each component as it includes the component in the customized installation package.

 

The mode affects the target operating system

Disconnected mode provides a selection field to identify the target operating system and hardware platform. Choose the operating system and hardware platform where the processing engine runs to create the CIP.

The command-line invocation tool (ifcli) runs on 32-bit kernels only.

 

Supported architectures

Supported architectures for running the ifcli tool and for installing the CIP include:

HP PA-RISC

The Installation Factory ifcli tool runs on 32-bit HP-UX 11iv1 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 11iv1 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
  • 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 WAS 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 the 64-bit Solaris 10 operating system kernel.

Sun SPARC

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

The CIP for 32-bit WAS products also provides 64-bit compatibility support for installing on 64-bit Solaris 8, Solaris 9, and Solaris 10 kernels.

Related information

Develop customized installation packages
Build Definition wizard panels
Product selection
Build information