IBM Installation Factory V6.0.2.33 for WebSphere Application Server V6.0 release

Downloadable files


Abstract

The Installation Factory creates turn-key install packages for installing IBM WebSphere Application Server in a reliable and repeatable way, tailored to your specific needs.

Download Description

Installing and configuring a WebSphere Application Server is usually a multi-step process:

  1. Install the shipped version of the product.

  2. Install the current refresh pack.

  3. Install the current Fix Pack.

  4. Install an SDK, Java™ technology edition Fix Pack.

  5. Install one or more Interim Fixes as needed.

  6. Create and configure one or more profiles.

  7. Deploy enterprise applications.


With the IBM Installation Factory for WebSphere Application Server, installing and configuring WebSphere Application Server requires just one step. Simply install the customized installation package (CIP) created by the Installation Factory; the other steps are performed automatically by the CIP you created. The Installation Factory combines the installation image for a version or release of a WebSphere software product with optional assets to create a CIP.

Optional assets can include any of the following components:
  1. Applicable maintenance packages.

  2. Scripts or Java classes to be run during install and uninstall, or profile creation and deletion.

  3. Enterprise application archive (EAR) files for applications that you intend to deploy with default deployment options on stand-alone application server profiles.

  4. A configuration archive (CAR) file for cloning a stand-alone application server profile from a previously installed and customized stand-alone application server.

  5. Additional files such as EAR files that you intend to deploy with customized options using a script that you have written.


The only required asset is the WebSphere Application Server installation image, which is either on the product disc or in a downloaded image from the Passport Advantage site. IBM is providing you with the IBM Installation Factory for WebSphere Application Server under the terms and conditions of the International Program License Agreement and License Information document for the WebSphere Application Server and you agree to be bound by such terms upon download and use of the program.



Installation Factory consists of both a graphical user interface (GUI) tool (the ifgui command in the bin directory) and a command-line interface tool (the ifcli command). Use the Installation Factory GUI to create a build definition file, which is an XML document that specifies how to build the CIP (for example, where to find the refresh pack you plan to use). You can generate the CIP directly from within the GUI or you can simply choose to save the build definition file and then generate the CIP outside of the GUI using the provided command-line interface tool.


The CIP you create will contain an installation program that is very similar to the one used by the WebSphere Application Server V6.0 product itself. This installation program can be used to install the CIP either interactively, using the installation wizard, or silently. Further, the CIP can perform a new scratch install of the application server, or it can be applied against an existing installation of the application server. In either case, the resulting installation is at the maintenance level you require, is configured as required, and any applications you have provided will be deployed.


Change history

  • 16 Mar 2009: Update to Version 6.0.2.33.

  • 13 October 2006: Reposted files and updated release dates to 4 Oct 2006 after correcting packaging error.

  • 22 August 2006: Update to Version 6.0.2.13 for Fix Pack 13, V6.0.2.13

  • 19 May 2006: Updated to Version 6.0.2.9 for Fix Pack 9, V6.0.2.9

  • 22 February 2006: Updated to Version 6.0.2.1 for Fix Pack 7, V6.0.2.7

  • 20 December 2005: Initial release, Version 6.0.2



Caution
For creating a customized installation package (CIP) that includes WebSphere Application Server V6.0.2 Fix Pack13 (V6.0.2.13) or above, Installation Factory V6.0.2.13 is required.

For creating a customized installation package (CIP) that includes WebSphere Application Server V6.0.2 Fix Pack 9 (V6.0.2.9) or above, Installation Factory V6.0.2.9 is required.

For creating a customized installation package (CIP) that includes WebSphere Application Server V6.0.2 Fix Pack 7 (V6.0.2.7) , Installation Factory V6.0.2.1 can still be used, but it is recommended to use the latest version of Installation Factory.

For creating a CIP that includes WebSphere Application Server V6.0.2 Fix Pack 5 (V6.0.2.5) or below, Installation Factory V6.0.2 can still be used, but it is recommended to use the latest version of Installation Factory.

WebSphere Application Server is the only supported product in IBM Installation Factory for WebSphere Application Server V6.0 releases.


WebSphere Extended Deployment Installation Factory
IBM Installation Factory for WebSphere Application Server can be extended to create install packages of WebSphere Extended Deployment by adding in the WebSphere Extended Deployment Installation Factory plug-in. Download this plug-in from
http://www.ibm.com/support/docview.wss?rs=180&uid=swg24011498

Prerequisites

The Installation Factory requires approximately 500 MB of system temporary space (such as /tmp directory on Linux or UNIX) for the processing engine to merge the installation image with maintenance packages.

Also, provide adequate disk space for the installation image, the maintenance packages, and the customized installation package. The disk space requirements vary, depending on the product and the number of maintenance packages included.

URL LANGUAGE SIZE(Bytes)
Detailed system requirements US English 100000

Installation Instructions

Download the packed code for your operating system.

Unpack the file before getting started using the Installation Factory.

The Installation Factory has two major components:


  • The Installation Factory GUI (the ifgui command in the bin directory)

    Use the ifgui command to start the Installation Factory GUI. Two wizards in the GUI help you create the build definition file.

  • The command-line interface tool (the ifcli command)

    Use the ifcli command on the target operating system to build a customized installation package for that type of operating system.


A possibility exists that you might run the two components on two separate machines. If so, you must download the proper Installation Factory code for each operating system.

Tested systems that support the Installation Factory GUI (ifgui) include:
  • AIX

  • Windows 2000

  • Windows 2003 *

  • Solaris 9

  • Linux RHEL 3

  • HP-UX


* Perform the following procedure to use the Help system on Windows 2003 systems:
  1. Open the Internet Explorer Web browser.

  2. Click File > Add this site to > Local Internet Zone.

  3. Click Add to add http://127.0.0.1.
  4. Click Close.
  5. Close Internet Explorer.
  6. Launch the ifgui Help.

Supported architectures
Supported architectures for running the ifcli tool and for installing the CIP include:
  • HP PA-RISC

  • The Installation Factory ifcli tool runs on 32-bit HP-UX 11iv1 kernels on PA-RISC platforms. The CIP for 32-bit WebSphere Application Server products also provides 64-bit compatibility support for installing on 64-bit HP-UX 11iv1 kernels on PA-RISC hardware platforms.

  • IBM PowerPC32

  • The Installation Factory ifcli tool runs on 32-bit AIX 5L 5.1 systems, AIX 5L 5.2 systems, AIX 5L 5.3 systems, and Linux systems. The CIP for 32-bit WebSphere Application Server products also provides 64-bit compatibility support for installing on 64-bit AIX or Linux kernels running on 64-bit pSeries hardware platforms.

  • Intel IA32

  • The Installation Factory ifcli tool runs on 32-bit Intel and AMD hardware platforms running 32-bit Linux kernels or 32-bit Windows kernels. The CIP for 32-bit WebSphere Application Server products supports Windows 2000 Advanced Server SP4, Windows 2000 Server SP4, Windows 2000 Professional SP4 (development only), Windows Server 2003 Datacenter, Windows Server 2003 Enterprise, Windows Server 2003 Standard, and Windows XP Professional SP1a (development only) on 32-bit Intel and AMD platforms.

  • IBM S/390

  • The Installation Factory ifcli tool runs on 31-bit mainframe hardware platforms running 31-bit Linux kernels. The CIP for 31-bit WebSphere Application Server products also provides 64-bit compatibility support for installing on 64-bit Linux kernels on zSeries platforms.

  • Sun Sparc

  • The Installation Factory ifcli tool runs on 32-bit Solaris 8, Solaris 9, and Solaris 10 operating system kernels on SPARC and UltraSPARC 60 platforms. The CIP for 32-bit WebSphere Application Server products also provides 64-bit compatibility support for installing on 64-bit Solaris 8, Solaris 9, and Solaris 10 kernels.

In some cases, you cannot use the GUI on the operating system platform that is the target for the customized installation package. You have two options in such a case:

  • Create the build definition file using the ifgui command, which starts the GUI.

    1. Download and install the Installation Factory on a supported GUI machine so that you can create the build definition.

    2. Use the Installation Factory GUI on a supported machine to create a build definition file for the target operating system on another machine.

    3. Copy the build definition file to the target operating system.

    4. Download and install the Installation Factory again on the target operating system machine so that you can use the processing engine to create the customized installation package.

    5. Use the ifcli command to start the processing engine and create the customized installation package.

      See "Creating a build definition for another machine" in the GUI help after you start the GUI for a description of such a procedure.

  • Create the build definition XML document using a text editor or an XML editor.

    1. Download and install the Installation Factory on the target operating system machine so that you can use the processing engine to create the customized installation package.

    2. Copy one of the sample build definition documents from the IF_install_root/samples/was directory to get started.

    3. Make your changes to the file.

    4. Validate the build definition document with its XML schema (XSD file) using a validating XML parser or editor.

    5. Use the ifcli command to start the processing engine and create the customized installation package.


Download package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is DD?
AIX 03/16/2009 US English 125189049 FTP DD
HP-UX 03/16/2009 US English 130228224 FTP DD
Linux for Intel 03/16/2009 US English 139227136 FTP DD
Linux for pSeries 3/16/2009 US English 142376960 FTP DD
Linux for zSeries 3/16/2009 US English 132757800 FTP DD
Solaris 03/16/2009 US English 119869677 FTP DD
Windows 03/16/2009 US English 137512165 FTP DD
Notices 12/20/2005 US English 40448 FTP DD
Non-IBM License 12/20/2005 US English 51712 FTP DD

Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express Install and migration AIX, HP-UX, Linux, Solaris, Windows 6.0.2, 6.0 Express
Application Servers Runtimes for Java Technology Java SDK

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
Install

Software version:

6.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

Base, Express, Network Deployment

Reference #:

4009108

Modified date:

2008-07-07

Translate my page

Machine Translation

Content navigation