In some instances it is necessary or convenient to
create a build definition file on one workstation for use on another
workstation. The build definition file is the precursor to the customized
installation package (CIP). To install a CIP
on an i5/OS® server, create
the build definition file and CIP on a Windows®, Linux® or UNIX® server in connected mode.
The CIP can then be exported either to the i5/OS server or to a Windows server and installed on the i5/OS server from there.
Before you begin
You must have downloaded and unpacked the IBM® WebSphere® Installation
Factory for
WebSphere ESB on
the server workstation that will be used to create the customized
installation package.
About this task
Use the following procedure to create the build definition
file and the associated CIP and complete the installation on a different
server. For simplicity we will refer to the workstation on which you
intend to install the customized installation package as the
"target
system", and the workstation on which you will create the build
definition file as the
"processing engine".
Procedure
- Mount or access the product installation image for
your target system's operating system.
If you intend to work in connected mode, ensure
that the product media (DVD or download image) with the WebSphere ESB installation
image is accessible from the processing engine.
You need to
know the location of the image so that you can create a build definition
file that points to the image.
Write down the mount point or
the storage location so that you can provide the storage location
to the Build Definition wizard that is running on the processing engine.
- Download to your processing engine the maintenance
packages for the target system's operating system.
Locate
download packages for WebSphere ESB on
the following Web site: Recommended updates for WebSphere ESB.
Refresh
pack and fix pack zipped files are bundled with the Update Installer
for WebSphere Software.
Extract the file to expose the maintenance package (*.pak) file in
the updateinstaller/maintenance directory.
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 processing engine.
- Start the Installation Factory console on the processing
engine 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.
Option |
Description |
Create a new build definition file |
Click the button for a New build definition file. From here
the Installation Factory launches two wizards in sequence. The two
wizards are the Product Selection wizard and the Build Definition
wizard. |
Open an existing build definition file |
Click the button to Open an existing 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 Connected mode and then select
the operating system of your target system from the list.
- Provide all required parameters to identify the product,
installation image, maintenance packages, the enterprise archive file,
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 option to create both the CIP and the build
definition file. Select Save build definition
file and generate customized installation package rather
than the default Save build definition file only.
- Click Finish to save the build definition
and create the CIP on the processing engine.
- Copy the CIP to the target system.
Alternatively you can install the CIP onto i5/OS directly from a Windows server. See the related
task: Installing a CIP on System i® using a Windows workstation graphical interface.
- On the target system install the customized installation
package using the InstallShield 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 ESB is
in the WBI directory and is named: