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.
Before you begin
If you are creating a build definition for the processing engine that runs on another machine, see Creating a build definition for another machine.
Why and when to perform this task
Use the following procedure to create the build definition document and the customized installation package on one machine.
Steps for this task
Tested systems that support the Installation Factory console include Windows 2000, Windows 2003, Solaris 9, and Linux RHEL 3. 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.
You need the image to create the customized installation package.
Locate download packages for Version 6 of the WebSphere Application Server products on the following Web site: Recommended updates for WebSphere Application Server and Network Deployment. The information also applies to the Express product.
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.
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 you must change the product, start a new
build definition.
Browse to select the installation image directory and the maintenance package files.
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/log.txt file when the processing engine is finished.
The Installation wizard for WebSphere Application Server products is the install command in the CIP_directory/WAS directory.
See Profile customization for examples of restoring a configuration archive by way of the command line.
What to do next
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.
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