[AIX HP-UX Linux Solaris Windows]

Creating a build definition and CIP on the processing engine machine

This topic describes how to create a build definition and CIP when the processing engine and the Build definition wizard are on the same machine.

Before you begin

You can also create installation packages for operating systems other than the one on which Installation Factory is running:
  • [AIX] [HP-UX] [Linux] [Solaris] The Installation Factory on these operating systems can create installation packages for all supported platforms.
  • [Windows] The Installation Factory on Windows operating systems can create installation packages for Windows and i5/OS.
  • [iSeries] i5/OS users must install the Installation Factory on a distributed platform. The Installation Factory does not run on an i5/OS platform.

If you are creating a build definition for the processing engine that runs on another machine, see Creating a CIP build definition for another machine.

Avoid trouble Avoid trouble:

As of Version 6.1.0.13 you must keep the version levels of the application server and any installed feature packs synchronized to the same maintenance level. If you have any feature packs installed, then it is recommended that you use the Update Installer to synchronize your environment before installing any additional Installation Factory packages. In fact, you will either be blocked from installing or prompted to upgrade during the installation of a feature pack CIP if your versions are not the same. If you are prompted and do not provide the proper maintenance packages you will be blocked from installing the CIP.

You can slip install, or update, an existing application server that contains one or more feature packs with an IIP as long as all packages in the IIP are at the same maintenance level. You can alsoscratch install an IIP containing the application server and one or more feature packs onto a machine with no existing application server as long as all included packages are at the same maintenance level. Read the Working with feature packs topic for more information. You must use Installation Factory version 6.1.0.17 or later if you want to use an IIP to update a feature pack environment.

If you are installing the Feature Pack for Web Services for the first time, then it is recommended that you create a CIP containing the feature pack and the most recent fix pack. Otherwise if you have already installed the Feature Pack for Web Services with the regular installer, you need to include a mandatory interim fix before installing a CIP containing any feature pack fix packs. See Installing and configuring multiple feature packs for additional information regarding feature pack installation and other considerations.gotcha

About this task

To create a customized installation package (CIP), first create a build definition file, which the Installation Factory uses to generate the CIP. The build definition file describes exactly what the Installation Factory includes in the CIP so that you can achieve the installation customizations that you require. Use the following procedure to create the build definition document and the customized installation package on one machine.

Procedure

  1. Download the Installation Factory code from the download page for the IBM Installation Factory for WebSphere Application Server and unpack the code.

    See the download page for a complete list of tested operating systems.

    Use the Installation Factory console and the processing engine on the same machine with a tested and certified operating system.

  2. Mount or access the product installation image for your operating system.

    You need the image to create the customized installation package.

  3. Download maintenance packages.

    Locate download packages for Version 6.x of the WebSphere Application Server products on the following Web site: Recommended updates for WebSphere Application Server and Network Deployment. The information also applies to the Express product.

  4. Start the Installation Factory console with the ifgui command:
  5. Create a new build definition or edit an existing build definition.

    Click the button for a New customization installation package to start two wizards in sequence. The two wizards are the Product Selection wizard and the Build Definition wizard.

    Click the button to Open a build definition file. Opening an existing build definition starts the Build Definition wizard only. If you must change the product, start a new customization installation package.

  6. Select the check box for connected mode processing 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.

  7. Provide all required parameters to identify the product, installation image, maintenance packages, the configuration archive file, enterprise archive files, other files and directories, scripts, the output location for the build definition file, and the output location for the customized installation package (CIP).
    File paths and file names must comply with the following guidelines:
    • [Windows] Contain 35 or fewer characters on Windows® platforms
    • Start and end with English-only alphabetic characters (A-Z, a-z) or numbers (0-9) only
    • Contain English-only alphabetic characters (A-Z, a-z), numbers (0-9), periods (.) or underscores (_) only
    • Not contain special characters (such as à é í ö û æ ñ ☐)
    • Not contain spaces or these characters: ~ ` ! @ # $ % ^ & ( ) { } [ ] | \ / : ; , ? ' " < = > + *
    Important: During the creation of a CIP, the maintenance packages are not validated for product appropriateness. When creating a CIP and bundling maintenance packages, therefore, make sure that the maintenance packages are for the correct product. If you are creating a WebSphere Application Server CIP and want to bundle maintenance packages, for example, make sure that the maintenance packages are for WebSphere Application Server rather than for any other product. If you are creating a Feature Pack for Web Services CIP and want to bundle maintenance packages, make sure that the maintenance packages are for the Feature Pack for Web Services rather than for any other product. Make sure that you are already at or above the application server version required by any feature pack maintenance packages or the CIP will not install correctly and you will be prompted to apply further maintenance.
  8. Select the Save build definition file and generate the customized installation package option.
  9. 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 IF_root/logs/log.txt file when the processing engine is finished.

  10. Installers can now install the customized installation package using the InstallShield for 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.

    To use the installation wizard for WebSphere Application Server product CIPs, run the install command in the cip_root/WAS directory.

    For CIPs which include Feature Pack for Web Services, run the install command in the cip_root/WEBSV directory.

  11. Create a CIP-based custom stand-alone application server profile.
    Use one of the following methods to create the profile:
    • After the CIP installation, run the Profile management tool.
    • After the CIP installation, run the manageprofiles command once to do a create and augment.
    • After the CIP installation, run the manageprofiles command twice sequentially to do a create and then an augment.

      Alternatively, you can run the command once to augment an existing profile.

    • In a scratch installation, do the following within the CIP installation wizard:
      1. On the Install Sample Applications panel, select the Install profile customizations checkbox.
      2. On the WebSphere Application Server environments 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.

    If the profile that you create has a configuration archive in it, then it will be imported.

What to do next

In some cases, you might be unable to use the console on the target operating system platform. You have two options in such a case:
  • Use the console in disconnected mode on a supported machine to create a build definition file for the target operating system on another machine.

    Then 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 Creating a CIP build definition for another machine for a description of such a procedure.

  • Create the build definition XML document using a validating XML editor.
    Copy one of the sample build definition documents for the product to get started:
    • The application server sample file is located in the IF_root/samples/was directory.
    • The Feature Pack for Web Services sample file is located in the IF_root/samples/websv directory.

    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.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tins_if_createbuild1
File name: tins_if_createbuild1.html