Create a build definition and CIP on the processing engine machine

Create a build definition and CIP on the processing engine machine

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

Overview

Use the following procedure to create the build definition document and the customized installation package on one machine.

Procedure

Download the Installation Factory code from the download page for the IBM Installation Factory for WAS and unpack the code.
See the download page for a complete list of tested operating systems.
Use the Installation Factory console and the processing engine on the same machine with a tested and certified operating system.

Mount or access the product installation image for your operating system.
We need the image to create the customized installation package.

Download maintenance packages.
Locate download packages for V6.x of the WAS products on the following Web site: Recommended updates for WAS and Network Deployment. The information also applies to the Express product.

Start the Installation Factory console with the ifgui script.

Use the IF_root/bin/ifgui.sh script.

On Windows use the IF_root\bin\ifgui.bat script.

Create a new build definition or edit an existing build definition.
Click the button for a New build definition
to start two wizards in sequence. The two wizards are the Product Selection wizard and the Build Definition wizard.
Click the button to Open a build definition file
. Opening an existing build definition starts the Build Definition wizard only. If change the product, start a new build definition.

Select the check box for connected mode processing so that you can create a customized installation package later in addition to creating the build definition file.
Browse to select the installation image directory and the maintenance package files.

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

Select the Save build definition file and generate customized installation package option.

Click Finish to generate the CIP.
The amount of time required to generate the CIP depends on the number of maintenance packages and the number of features that you include in the package.
The Installation Factory logs a completion message in the /logs/install/log.txt file when the processing engine is finished.

Installers can now 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 WAS products is the install command in the CIP_directory/WAS directory.

Create a CIP-based custom stand-alone application server profile. Use one of the following methods to create the profile:

After the CIP installation, run the Profile management tool.

After the CIP installation, run the manageprofiles command once to do a create and augment.

After the CIP installation, run the manageprofiles command twice sequentially to do a create and then an augment.
Alternatively, you can run the manageprofiles command once to augment an existing profile.

In a scratch installation, do the following within the CIP installation wizard:

On the Install Sample Applications panel, select the Install profile customizations checkbox.

On the WAS environments panel, select a profile that has profile customization defined.
If the profile that you select has profile customization defined, then the installation wizard will effectively run the manageprofiles command once to do a create and augment. If there is no profile customization defined, you get a regular profile.

If the profile that you create has a configuration archive in it, then it will be imported.

What to do next
In some cases, you might be unable 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 start the processing engine and create the customized installation package.
See Creating a build definition for another machine for a description of 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.

Related information

Developing and installing customized installation packages Creating a build definition for another machine