CIP mode selection

Use this panel to specify whether to work in connected or disconnected mode, and to specify the target operating system for the customized installation package (CIP).

Mode in which we are working with the build definition file.

Connected mode

Select connected mode to work with a build definition file on this computer, and to optionally create a customized installation package. Connected mode requires direct access to WAS installation image and any optional assets you specified, which must match the operating system and architecture for this computer.

When running in connected mode, 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.

Disconnected mode

Select disconnected mode to work with a build definition file for use on another computer. The build definition file is saved to a location that is relative to this computer. Specify all other directory paths and file names that are relative to the computer where the processing engine creates a customized installation package.

For example, suppose that WAS installation image is on the target machine in the /tmp/IBM/WASimage directory. Specify the location for the target machine where the processing engine must find WAS image to include in the CIP.

Platform for which to build the CIP.

The available platforms vary depending on whether you choose connected mode or disconnected mode. In connected mode we can only choose from those installers that are supported on the current platform. In disconnected mode, we might choose from the entire list of supported platforms. Choose the operating system and hardware platform where the processing engine runs to create the CIP.