Installation Factory overview

The IBM Installation Factory for WebSphere Application Server is an Eclipse-based tool which creates installation packages for installing WebSphere Application Server in a reliable and repeatable way, tailored to your specific needs.

The Installation Factory can produce two kinds of packages, a customized installation package (CIP) and an integrated installation package (IIP). A CIP is used to install a WebSphere Application Server product in addition to maintenance, profile customization, and user-defined scripting. An IIP is a larger package which can install an entire WebSphere software stack, such as an application server, a feature pack, and other user files. An IIP can even contain several CIPs.

See the Getting Started with the Installation Factory page to begin creating an installation package.

Note: You must install the Installation Factory on a distributed platform to create installation packages for i5/OS. The Installation Factory does not run on an i5/OS platform.

Customized installation packages

The Installation Factory combines the installation image for a version or release of a WebSphere software product with applicable maintenance packages, a configuration archive, one or more enterprise archive files, customization scripts, and other user files to create a customized installation package. You can significantly reduce the time and complexity of a standard installation process by creating and installing a CIP.

Installing and configuring a WebSphere application server product is usually a multiple step process:
  1. Install the shipped version of the product.
  2. Install the current fix pack.
  3. Install a Java 2 Software Development Kit (SDK) fix pack.
  4. Install one or more interim fixes as needed.
  5. Create and configure application servers and other artifacts.
  6. Deploy applications.

The Installation Factory simplifies the process by creating a single installation image, the customized installation package.

Overview of creating a CIP

After creating the CIP, installing and configuring a WebSphere software product is a one-step process: install the CIP.

Integrated installation packages

Customers who need to install multiple installation packages in an automated and highly repeatable manner can create an IIP which aggregates those packages into a single installable package. As an example, you can have multiple servers on which you need to deploy WebSphere Application Server and some number of feature packs. Instead of having to install each of these products as an independent step on each server, you can create an IIP that will install all of them at once.

The Installation Factory user specifies which installation packages to include in the IIP, the order in which they should be installed, and various other details about the desired behavior of the IIP and each of its contained installation packages.

Each product you include in the IIP can be customized separately for greater flexibility. For example, you could run the WebSphere Application Server product installation interactively and then run one or more feature pack installations silently to obtain a seamless installation of the entire set of packages. There is also flexibility as to which contained installation packages actually get installed on any given invocation of the IIP; in other words you can choose not to install certain packages in the IIP.

One example of an IIP installation scenario is the following:

  1. Install a CIP containing a WebSphere Application Server product
  2. Install a feature pack (or, a CIP created with a feature pack and feature pack fixes)
  3. Install additional user files and directories
  4. Install another instance of the application server CIP in another directory on the machine
There are two scenarios for running an IIP installation on a remote machine:
  • You can create a build definition file and the entire IIP package on a local machine. The IIP might include, for example, WebSphere Application Server, IBM® WebSphere® Installation Factory, and maintenance. You can then ship the package for installation on a remote machine.
  • You can create a build definition file on a local machine and ship it to a remote machine that already has the package. For example, the package might include WebSphere Application Server, IBM WebSphere Installation Factory, and maintenance. You can then run IBM WebSphere Installation Factory on the remote machine and it can use the shipped build definition file to complete the installation.

For more information on remote IIP installation, see the topic Creating a build definition and generating the IIP.

Remote Installation

There are two scenarios for running an IIP installation on a remote machine:
  • You can create a build definition file and the entire IIP package on a local machine. The IIP might include, for example, WebSphere Application Server, IBM WebSphere Installation Factory, and maintenance. You can then ship the package for installation on a remote machine.
  • You can create a build definition file on a local machine and ship it to a remote machine that already has the package. For example, the package might include WebSphere Application Server, IBM WebSphere Installation Factory, and maintenance. You can then run IBM WebSphere Installation Factory on the remote machine and it can use the shipped build definition file to complete the installation.

For more information on remote IIP installation, see the topic Creating a build definition and generating the IIP.




Related concepts
IIP overview
Related tasks
Getting started with the Installation Factory
Developing and installing customized installation packages
Developing and installing integrated installation packages
IBM Installation Factory for WebSphere Application Server
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 6:03:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-iseries&topic=cins_ifactory
File name: cins_ifactory.html