IIP mode selection

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

When the Build Definition wizard has access to WAS installation image and other components required to create the IIP, then we can use it in connected mode. In this mode, the Build Definition wizard can validate the files that are provided as input and optionally generate the IIP in addition to creating the build definition file. If the product installation image and other components are not accessible because they are on a separate machine, then we can only use the Build Definition wizard in disconnected mode. In disconnected mode, the Build Definition wizard can be used to create a build definition file for a target platform but it is not able to validate any of the input or generate a IIP. We can copy the build definition file to the target machine and use it as input to the ifcli command to generate the IIP, at which time all of the input that was provided in the Build Definition wizard is validated.

Modes

Mode in which we are working with the build definition file. The mode affects component validation.

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 of this computer.

When running in connected mode the Build Definition wizard can validate connected installation images 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 generates an IIP.

For example, suppose that WAS 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 WAS image to include in the IIP.

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 IIP.

Platforms

Platform for which to build the IIP.

The available platforms depend 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 you intend to run the IIP.

There are different lists of supported platforms for running the Installation Factory GUI (ifgui) and the ifcli tools.

See the IBM Installation Factory for WebSphere Application Server V7.x download page for a current list of all supported platforms for the Installation Factory.



Related reference



Last updated Nov 11, 2010 1:01:09 PM CST