When the Build Definition wizard can access the product installation image, maintenance packages, and other components required to create the customized installation package (CIP), you can also run the processing engine (ifcli) to create the CIP on the same machine. When the Build Definition wizard can access the components of the CIP, the Build Definition wizard is in connected mode. If the installation image, the maintenance packages, and the other components are not accessible because they are on a separate processing engine machine, the Build Definition wizard is in disconnected mode. In disconnected mode, the Build Definition wizard is creating only a build definition file for a target platform.
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 the /tmp/IBM/WASimage directory. 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
The CIP for 32-bit WebSphere Application Server products also provides 64-bit compatibility support for installing on 64-bit HP-UX 11iv1 kernels on PA-RISC hardware platforms.
The CIP for 32-bit WebSphere Application Server products also provides 64-bit compatibility support for installing on 64-bit AIX or Linux kernels running on 64-bit pSeries hardware platforms.
The CIP for 32-bit WebSphere Application Server 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.
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.
The CIP for 32-bit WebSphere Application Server products also provides 64-bit compatibility support for installing on 64-bit Solaris 8, Solaris 9, and Solaris 10 kernels.
Related information
Build Definition wizard panels
Product selection
Build information