Create a build definition for another machine

Create a build definition for another machine

This procedure describes how to use the Build Definition wizard to create a build definition for the processing engine that runs on another machine.
If you are creating a build definition for the processing engine that runs on the same machine as the Build Definition wizard, see Creating a build definition and CIP on the processing engine machine.

Overview

The download page has a complete list of tested operating systems for the Installation Factory console. In some cases, you might not be able to use the console on the target operating system platform. You have two options in such a case:

Use the console in disconnected mode on a supported machine to create a build definition file for the target operating system on another machine.
Then copy the file to the target operating system and use the command line interface to create the customized installation package. This topic describes such a procedure.

Create the build definition XML document using a validating XML editor.
Copy one of the sample build definition documents from the IF_root/samples/was directory to get started.
After making your changes, validate the build definition document with its XML schema (the Commom.xsd, BaseBuildDefinition.xsd, and BuildDefinition.xsd files) using a validating XML parser or editor. Then use the command line interface to start the processing engine and create the customized installation package.

This procedure describes a configuration where the Build Definition wizard is not on the same machine as the target system. Although the Build Definition wizard cannot access the installation image and the maintenance packages on the target operating system, you can enter the information manually. Use directory paths and file names that exist on the target operating system.
Run the Build Definition wizard on a supported operating system such as AIX or Linux to create the build definition file for an unsupported UNIX-based system. Use the Build Definition wizard on a Windows 2000 or Windows 2003 machine to create the build definition file for another Windows system.
For example, assume that you run the console on a RHEL 3 system that cannot access a target AIX system. The Build Definition wizard cannot browse to file locations on the target system. However, you can type the directory path of the AIX location for the ND installation image and other elements of the customized installation package (CIP).
The Build Definition wizard cannot verify the installation image because the wizard cannot access the directory on the AIX system. Verification occurs later, when the processing engine that runs on the target operating system builds the customized installation package. If the installation image or the maintenance packages are not valid, the processing engine logs the problem.
Use the following procedure to create and install the customized installation package.

Procedure

Download the Installation Factory code that is appropriate for the Build Definition operating system.
Download the code from the download page for the IBM Installation Factory for WAS. Unpack the code on the Build Definition machine.

Download the Installation Factory code that is appropriate for the target processing engine system.
Download the code from the download page for the IBM Installation Factory for WAS. Unpack the code on the target operating system. The target operating system is where you run the Installation Factory processing engine to create the customized installation package.

Copy the Installation Factory code from the Supplements disc to your operating system. For further details, see Getting started with the Installation Factory.

Mount or access the product installation image on the target operating system platform.
We need to know the location of the image so that you can create a build definition file that points to the image.
Write down the mount point or the storage location so that you can provide the storage location to the Build Definition wizard that is running on the other machine.

Download maintenance packages to the target operating system.
Locate download packages for V6.x of the WebSphere Application Server products on the following Web site: Recommended fixes for WAS
Refresh pack ZIP files and fix pack ZIP files are bundled with the Update Installer for WebSphere Software. Unzip the file to expose the maintenance package (*.pak) file in the updateinstaller/maintenance directory.
Write down the storage location of the downloaded maintenance package so that you can provide the location to the Build Definition wizard that is running on the other machine.

Start the Installation Factory console on a supported system such as AIX or Linux with the IF_root/bin/ifgui.sh script.
Or start the Installation Factory console with the IF_root\bin\ifgui.bat script on Windows systems.

Create a new build definition or edit an existing build definition.
Clicking the New build definition icon
starts two wizards in sequence, the Product Selection wizard and the Build Definition wizard.
Clicking the Open a build definition file icon
starts only the Build Definition wizard. If change the product, start a new build definition.

Select the check box for disconnected mode processing because you are creating the build definition for another machine.

Provide all required parameters to identify the product, installation image, maintenance packages, the configuration archive file, enterprise archive files, other files and directories, scripts, the output location for the build definition file, and the output location for the customized installation package (CIP).
All of the locations must refer to locations on the target operating system machine.
The Build Definition wizard cannot verify the installation image, the maintenance packages, or any other files or scripts that you enter in disconnected mode. Always enter directory paths and file names in relation to the target operating system machine and not the machine you are using to create the build definition.

Click Finish to save the build definition file on the Build Definition machine.

Copy the build definition file from the Build Definition machine to the target operating system platform.

Use the command-line invocation tool (ifcli) on the target operating system platform to launch the processing engine that creates the CIP on the target operating system.
The amount of time required to generate the CIP is dependent on the number of maintenance packages and the number of features that you are including in the package.
The processing engine logs a completion message in the /logs/install/log.txt file when the processing engine is finished.

Install the customized installation package using the InstallShield for Multiplatforms (ISMP) Installation wizard that is included in the CIP. Panels in the CIP Installation wizard vary according to the product that you are installing.
The Installation wizard for WebSphere Application Server products is in the WAS directory and is named either install (operating systems such as AIX or Linux) or install.exe (Windows).

Related tasks

Developing and installing customized installation packages Creating a build definition and CIP on the processing engine machine

Related Reference