The
IBM Installation Factory for WebSphere Extended Deployment generates a CIP
according to the details that the build definition file provides. The build
definition specifies the product package to install, the location of the CIP,
the maintenance packages to include in the installation, the install scripts,
and any additional files to include in the CIP.
Before you begin
Gather the components to include in the CIP. Optional assets can
include maintenance packages and additional files to install on the system.
Ensure that all of the assets are available on the workstation on which you
intend to create your CIP.
About this task
The Build definition wizard assists you with the process of creating
a build definition file.
Procedure
- Launch the Installation Factory by running theifgui.bat
(sh) script from the IF_HOME/bin/ directory.
Click the New Build Definition icon.
- From
the Product selection wizard, select the product to include in the build definition
file, and click Next.
You can select any of the following products:
- WebSphere Application
Server Version 6.1
- WebSphere Extended Deployment Operations OptimizationVersion 6.1
- WebSphere Extended Deployment
Compute Grid Version 6.1
- WebSphere Extended Deployment Data Grid Version 6.1
Attention: You must create an individual CIP for each product.
A single CIP used to install all three components cannot be created.
- Select the
appropriate product edition from the list based on your product selection
in step 4, and click Next.
- Select the
appropriate package from the list, and click Finish to launch the Build
definition wizard.
- Select Connected or Disconnected from the Mode
Selection panel. Select Connected 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 operating systems that you intend to create the CIP on, and click Next.
You can install the CIP only on the target operating systems 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 product installation image, and click Next.
- Optionally, type the
location of each of the maintenance packs you want to include in the CIP.
You can choose
to include any available refresh packs, fix packs, or interim fixes.
- Click Add Scripts... to populate the table with
any customized installation scripts. Next, type the location of the script
files, and clear the check box to continue if an error occurs. The default
action is to stop the operation. Click OK to return to the panel.
Organize the script files in the exact order that
they should be performed after the installation process successfully completes,
and click Next. These scripts always run by default and according to
the corresponding operating system, regardless if the process is a new installation
or a slip installation.
You can choose not to run
any custom scripts during the installation by adding the following argument
to the
install command:
-OPT runCustomScripts=false
- Optionally, click Add Files... or Add
Directories... to populate the table with additional files or directories
for the CIP to install, and click Next.
- Optionally,
provide the organization, description, and additional information about the
product, which can be viewed by the person responsible for performing the
installation, and click Next.
- Review the summary of your selections, and click Finish to
generate the CIP. Click Back to make changes to any of the previous
panels.
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.
Results
You created and customized the build definition file, and you generated
the CIP if you chose to work in the connected mode.
What to do next
If the build Definition wizard does not provide
you with the option to generate the CIP from the build definition file, you
can still generate it by running the ifcli.bat (sh) script
from the IF_HOME/bin/ directory. After you
generate the CIP, you can now install it.