You can create a customized installation package (CIP) either using the build definition wizard directly, or by creating a build definition file with the build definition wizard and using a command-line tool to build the CIP.
On i5/OS®,
you must create a customized installation package (CIP) using the IBM® WebSphere® Installation Factory console
on a Windows®, Linux® or UNIX® server.
You can then export the CIP to your i5/OS server
and install the CIP directly or on a Windows server
you can use the install GUI to install the CIP on a remote i5/OS server.
Each panel in the Build Definition wizard prompts you for information about the CIP. For example, prompts exist for the locations of maintenance packages, scripts, and other components that you can include. Another prompt requests the location for generating the CIP. All of this information is saved in the new build definition file, or modified and saved in a build definition file that you are changing.
The last wizard panel provides an option for generating a CIP that is based on the content of the build definition file that you just defined. Alternately, you can save only the build definition file, for later use with the ifcli command. In disconnected mode you do not have the option to create the CIP. The ifcli command generates the CIP outside of the Installation Factory console, perhaps even on a different workstation or operating system.
When
you have completed the Build Definition wizard, save the build definition
file and (if working in connected mode) create the CIP, for later
installation on your i5/OS server.