A build definition file is a an XML document that specifies how
to build and customize the customized installation package (CIP) for the product. The build definition file identifies the product to
install, the features of the product, the maintenance packages, and other
customized components to include in the CIP.
Before you begin
Download the IBM Installation Factory for WebSphere Application Server
and the WebSphere Extended Deployment Installation Factory plugin to your
system.
About this task
The Build Definition wizard, from within the Installation Factory
graphical user interface (GUI), steps you through the process of creating
a build a definition file.
Procedure
- Gather the components to include in the customized installation
package (CIP). Optional assets can include maintenance packages
and additional files to install on the system. Make all of the assets available
on the workstation where you intend to create your CIP.
- Launch the console from the bin/ifgui directory.
- Click the New Build Definition icon after you launch the
console. With this option, you can create a new build definition
file, and optionally generate a CIP.
- Select the product to install from the
Product Selection wizard, and click Next. The
IBM WebSphere Extended Deployment 6.0.2 product CD contains two installation
images. One image installs WebSphere Extended Deployment 6.0.2 on WebSphere
Application Server 6.0.2. The other CD installs WebSphere Extended Deployment
6.0.2 on WebSphere Application Server 6.1.
- Select Extended Deployment for
the edition, and click Next.
- Select Extended Deployment as
the package, and click Finish.
- Select Connected or Disconnected from the Mode
Selection panel in the Build Definition wizard. Select Connected if
you plan to create a CIP on the same workstation that you create the build
definition file. To create the build definition file for use on another workstation,
select Disconnected.
Select the platforms on which you intend to
create the CIP, and click Next. You can install the CIP only on the
target platforms that you select from this panel.
- Type a unique identifier and a version number for the CIP in the
provided fields, and click Next.
The identifier is combined
with the version number to create a full package identifier, which is then
used to create a directory during installation that contains the customization
files for the selected package.
- Type the location of the build definition file, type the location
of the CIP, and click Next. The build definition file is
always saved to a directory path on the Build Definition wizard workstation.
- Type the location of the WebSphere Extended
Deployment 6.0.2 CD installation image, and click Next.
The directory for the installation image must
be in the connected mode. In the disconnected mode, specify the file path
in terms of the workstation on which the processing engine workstation runs.
- Choose the features to include in the
CIP, and click Next.
You can select WebSphere Extended Deployment
enhancements, mixed server environment, or both.
- Provide the maintenance packages you
want to include by typing the refresh pack and fix pack locations.
- Type the interim fix location to provide
the interim fix packages, and click Add to include any interim fix
images.
- Optionally, click Add Files... or Add
Directories... to populate the table with additional files or directories
for the CIP to install, and click Next.
- Type the organization and description
of the CIP to define the authorship of the package, and click Next.
If you chose to create the build definition file
in the disconnected mode, you can save the build definition file, but you
do not have the option to generate the CIP.
A message of completion
confirms that the new build definition file is saved to the directory that
you specified in step 9. By default, this directory is actually the combined
identifier and version number that you specified in step 8.
- Review the Customized installation package
preview summary panel, and click Finish to save the build definition
file and generate the CIP.
If you create the build definition
file in the disconnected mode, you can only save the build definition file.
To generate the customized installation package (CIP), copy the build definition
file to the workstation that is running the target operating system. Start
the processing engine with the bin/ifcli command. The ifcli command
creates customized installation packages (CIP) for all of the supported operating
systems.
Results
You created and customized the build definition file.
What to do next
After you generate the CIP, you can then install it.
Use the InstallShield for Multiplatforms (ISMP) Installation wizard, or run
the installation command.