The IBM® WebSphere® Installation Factory is an Eclipse-based tool which creates installation packages for installing WebSphere software stack in a reliable and repeatable way, tailored to your specific needs.
An IIP is an installation package which can install an entire WebSphere software stack, such as an process server, a feature pack, and user files. An IIP can even contain several CIPs.
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 Process 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 in a defined sequence.
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 Process Server product install interactively and then run one or more feature pack installs silently to obtain a seamless install 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:
Contributions
An IIP consists of contributions, which are WebSphere products, feature packs, or sets of files. A given contribution can be invoked multiple times if desired. Each of these is referred to as an invocation. For example, you might add an invocation of the contribution for installing WebSphere Process Server multiple times in different directories on the same workstation.
Some examples of contributions are the following:
Defined Installation Packages
IBM has provided several pre-configured contribution types which allow the Installation Factory to provide enhanced support for adding them to the IIP and controlling their behavior at IIP runtime, which reduces user effort, the possibility of mistakes, and so on.
Installation Integration Bus
Installation packages and related tools can be easily included in the IIP by the user, and Installation Factory will automatically integrate this install package with others that might already exist in the IIP, saving time and effort. This integration between the contained installation packages is accomplished by passing information from one package to the next. The underlying infrastructure which enables this integration is referred to as the Installation Integration Bus (IIB, or just “Bus”). The design allows installation packages and other install-related commands to be plugged in, wired together, and executed via the Bus in a uniform manner, allowing otherwise separate installation packages to work together. You can use macro substitution to take advantage of this underlying infrastructure. See IIP macro replacement for more information.
For example, when installing WebSphere Process Server and one or more feature packs using an IIP, the -installLocation option used for the process server can be automatically reused as the default installation location for each of the feature packs with a macro (for example, $RESV ) so you do not have to specify that location more than once. In many cases you will have to do nothing more than add the feature pack package into the IIP, and Installation Factory will do the rest in terms of integrating it with the other packages. The Bus enables this end-to-end flow of all included packages.