This procedure describes how to use the Build Definition wizard
to create a build definition for the processing engine that runs on another
machine.
Before you begin
If you are creating a build definition
for the processing engine that runs on the same machine as the Build Definition
wizard, then see Creating a build definition and CIP on the processing engine machine.
Avoid trouble: As of Version 6.1.0.13 you must
keep the version levels of the application server and any installed
feature packs synchronized to the same maintenance level. If you have
any feature packs installed, then it is recommended that you use the
Update Installer to synchronize your environment before installing
any additional Installation Factory packages. In fact, you will either
be blocked from installing or prompted to upgrade during the installation
of a feature pack CIP if your versions are not the same. If you are
prompted and do not provide the proper maintenance packages you will
be blocked from installing the CIP.
You can slip install,
or update, an existing application server that contains one or more
feature packs with an IIP as long as all packages in the IIP are at
the same maintenance level. You can alsoscratch install an
IIP containing the application server and one or more feature packs
onto a machine with no existing application server as long as all
included packages are at the same maintenance level. Read the Working with feature packs topic for more information. You must
use Installation Factory version 6.1.0.17 or later if you want to
use an IIP to update a feature pack environment.
If you are installing
the Feature Pack for Web Services for the first time, then it is recommended
that you create a CIP containing the feature pack and the most recent
fix pack. Otherwise if you have already installed the Feature Pack
for Web Services with the regular installer, you need to include a
mandatory interim fix before installing a CIP containing any feature
pack fix packs. See
Installing and configuring multiple feature packs for additional information
regarding feature pack installation and other considerations.
gotcha
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. In some cases, you might not be able to use the console
on the target operating system platform. You have the following options in
such a case:
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.
You
can run the Build Definition wizard on any supported operating system to create
the build definition file for any other supported 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 Network Deployment installation image and other elements of the 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.
- 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 WebSphere
Application Server. 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 WebSphere Application Server. 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.
- Mount or access the product installation images to be included
in the CIP on the target processing engine system.
You need
to know the location of the image on the remote system so that you can create
a build definition file on the local machine that points to the image.
- Download maintenance packages to the target processing engine system.
Locate download packages for Version 6.x of the WebSphere Application
Server products on the following Web site: Recommended fixes for WebSphere Application Server
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 local machine.
- 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 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 CIP. All of the locations
must refer to locations on the target processing engine system.
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. If
you are creating a feature pack CIP and want to bundle maintenance packages,
make sure that the maintenance packages are for the feature pack rather than
for any other product. Make sure that you are already at or above the application
server version required by any feature pack maintenance packages or the CIP
will not install correctly and you will be prompted to apply further maintenance.
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 ifcli command 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 IF_root/logs/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.
To use the installation wizard for WebSphere
Application Server product CIPs, run the install command
in the cip_root/WAS directory.
For CIPs which include Feature Pack for Web
Services, run the install command in the cip_root/WEBSV directory.