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.
About this task
To create a customized installation package (CIP), first create
a build definition file, which the Installation Factory uses to generate the
CIP. The build definition file describes exactly what the Installation Factory
includes in the CIP so that you can achieve the installation customizations
that you require. Use the following procedure to create the build definition
document and the customized installation package on one 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.
- Start the Installation Factory console with the ifgui command:
- Create a new build definition or edit an existing build definition.
Click the button for a New customization installation package 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 customization installation
package.
- 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).
File paths and file names must comply with
the following guidelines:
Contain 35 or fewer characters on Windows® platforms
- Start and end with English-only alphabetic characters (A-Z, a-z)
or numbers (0-9) only
- Contain English-only alphabetic characters (A-Z, a-z), numbers
(0-9), periods (.) or underscores (_) only
- Not contain special characters (such as à é í ö û æ ñ ☐)
- Not contain spaces or these characters: ~ ` ! @ # $ % ^ &
( ) { } [ ] | \ / : ; , ? ' " < = > + *
Important: During the creation of a CIP, the maintenance
packages are not validated for product appropriateness. When creating a CIP
and bundling maintenance packages, therefore, make sure that the maintenance
packages are for the correct product. If you are creating a WebSphere Application
Server CIP and want to bundle maintenance packages, for example, make sure
that the maintenance packages are for WebSphere Application Server rather
than for any other product.
- Select the Save build definition file and generate the
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 IF_root/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.
To use the installation
wizard for WebSphere Application Server product CIPs, run the install command
in the cip_root/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 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.
If
you select the checkbox and you have application server customizations, they
will be used. If you do not have customizations, you get a regular application
server.
If the profile that you create has a configuration archive in
it, then it will be imported.