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.
- Download the Installation Factory code from
the download page for the IBM Installation Factory
for WebSphere Application Server 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.
You need the image to create the customized installation
package.
- Download maintenance packages.
Locate download packages
for Version 6.x 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.
- Start the Installation Factory console with the ifgui script.
Use the IF_root/bin/ifgui.sh script.
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 you must 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/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 WebSphere Application Server products is the install command
in the CIP_directory/WAS directory.
- Restore a configuration archive for a stand-alone
application server profile by using the Profile creation tool in the cip_uid_root/cip/ProfileCreator directory.
See Profile customization
for examples
of restoring a configuration archive by way of the command line.