WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Creating a customized installation package to use on the processing engine workstation

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
  1. 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.
  2. Download maintenance packages. Locate download packages for WebSphere ESB on the following Web site: Recommended updates for WebSphere ESB.
  3. Start the Installation Factory console with the ifgui script.
    • For AIX operating systemFor HP-UX operating systemFor Linux operating systemFor Solaris operating system Use the IF_root/bin/ifgui.sh script.
    • For Windows operating system Use the IF_root\bin\ifgui.bat script.
  4. Create a new build definition or edit an existing build definition.
    Option Description
    Create a new build definition file
    The image shows a standard file icon, a sheet of paper with a folded corner. In the center of the paper is a hub and spoke line image representing communication between computers. A starburst effect is shown in the upper left of the image, to indicate that this icon creates a new 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
    The image shows a standard file icon, a sheet of paper with a folded corner. In the center of the paper is a hub and spoke line image representing communication between computers. Wrapped around the icon is an arrow indicating that the file is being reused.
    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.
  5. 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.
  6. 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).
  7. 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.
  8. 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.

  9. 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.
  10. 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:
    1. On the Feature selection panel, select the Install profile customizations check box.
    2. 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:

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_if_create_local_cip.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).