2.4.2 Installation Factory
The Installation Factory creates turn-key install packages for installing WebSphere Application Server in a reliable and repeatable way, tailored to your specific needs. 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 standalone appserver profiles.
4. A configuration archive (CAR) file for cloning a standalone appserver profile from a previously installed and customized standalone appserver.
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 disk or in a downloaded image.
Installation Factory consists of both a GUI tool (the ifgui command in the bin directory), and a command line interface tool (the ifcli command).
Before creating a CIP, first create a build definition for the CIP. The build definition is an XML document that defines how the Installation Factory is to customize the WebSphere Application Server product.
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 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 appserver, or it can be applied against an existing installation of the appserver. 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. This is the recommended procedure for automating a WebSphere installation.