The Installation Factory allows you to create customized
installation packages for use on the local workstation or for other
servers. The process for creating a CIP on the workstation which hosts
the build definition wizard is described.
Before you begin
You must be working on a workstation which has the IBM® WebSphere® Installation Factory plug-in
installed.
About this task
Use the following procedure to create the build definition
file and the customized installation package on one workstation.
Procedure
- Mount or access the product installation image for your
operating system. Ensure that the product
media (DVD or download image) with the WebSphere ESB installation
image is accessible from the workstation on which you are working.
You need the installation image to create the customized installation
package.
- Download maintenance packages. Locate download
packages for WebSphere ESB on
the following Web site: Recommended updates for WebSphere ESB.
- 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.
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 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 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 Save build definition file and generate customized
installation package option. Select Save build
definition file and generate customized installation package rather
than the default Save build definition file only.
- 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.
- You can install the customized installation package using
the InstallShield MultiPlatform (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
the install command in the CIP_directory/WBI directory.
- Create a CIP-based custom stand-alone server profile in
one of the following ways.
Option |
Description |
Using the Profile Management Tool |
After the CIP installation, run the Profile Management Tool. Note: You
can only augment the profile if the CIP contains no profile customizations,
or if the CIP does contain profile customizations but you elect not
to use them.
|
Using the manageprofiles command |
After the CIP installation run the manageprofiles command
to create and optionally augment a server profile. You can do this
by running the command once (create and augment) or twice (create
then augment). Note: You can only augment the profile if the CIP contains
no profile customizations, or if the CIP does contain profile customizations
but you elect not to use them.
|
Using the CIP installation wizard |
If you are using a CIP to create a new installation, not an
upgrade or patch, you can create the server profile by doing the following:- On the Feature selection panel, select the Install profile
customizations check box.
- On the Environment selection panel, select a profile that has
profile customization defined. If the profile that you select has
profile customization defined, then the installation wizard will effectively
run the manageprofiles command once to do a create
and augment. If there is no profile customization defined, you get
a regular profile.
|
What to do next
In some cases, you might be unable to use the Installation
Factory console on the target operating system platform. For instance,
on certain platforms the
ifcli command is supported
but the
ifgui command is not. You have two options
in such a case:
Use the console in disconnected mode on a supported workstation
to create a build definition file for the target operating system
on another workstation.
Copy the file to the target operating
system and use the command-line interface to start the processing
engine and create the customized installation package.
See the
related tasks for a fuller description of this process.
Create the build definition XML document using a validating
XML editor.
Copy one of the sample build definition documents
from the IF_root/samples/wbi directory
to get started.
After making your changes, validate the build
definition document with its XML schema (the Commom.xsd, BaseBuildDefinition.xsd,
and BuildDefinition.xsd files) using a validating XML parser or editor.
Then use the command-line interface to start the processing engine
and create the customized installation package.