This topic describes how to create a build definition and CIP when the processing engine and the Build definition wizard are on the same machine.
If you are creating a build definition for the processing engine that runs on another machine, see Creating build definitions for another machine.
To create a customized installation package (CIP), first create a build definition file, which IBM WebSphere Installation Factory uses to generate the CIP. The build definition file describes exactly what the Installation Factory includes in the CIP so that you can achieve the installation customizations that you require. Use the following procedure to create the build definition document and the customized installation package on one machine.
Locate download packages for WebSphere Application Server products on the following Web site: Recommended updates for WebSphere Application Server and Network Deployment. The information also applies to the Express product.
Click the button for a New customization installation package to start two wizards in sequence. The two wizards are the Product Selection wizard and the Build Definition wizard.
Click the button to Open a build definition file. Opening an existing build definition starts the Build Definition wizard only. If you must change the product, start a new customization installation package.
Browse to select the installation image directory and the maintenance package files.
Panel | Description |
---|---|
CIP product, package and edition selection | Specify the desired product, package, and edition. |
CIP mode selection | Specify whether to work in connected or disconnected mode, and specify the target operating system for the CIP. |
CIP package identification | Specify a universally unique identifier for the CIP. |
CIP build information | Specify the name and location of the build definition file and the CIP. |
CIP product installation image | Specify the location of the directory that contains the installation image for the product to be included in the CIP. |
CIP feature selection | Specify features that you want to include in the CIP. |
CIP maintenance packages | Specify maintenance packages (*.pak files) that you want to include in the CIP. |
CIP installation and uninstallation scripts | Specify configuration scripts that can run after successfully installing the CIP or before uninstalling the CIP. |
CIP profile customization | Include profile customizations that include scripts to run at profile creation or deletion, deploying one or more enterprise archive (EAR) files, adding business level applications, and restoring one configuration archive file. |
CIP additional files | Specify additional files and directories to add to the CIP. |
CIP authorship | Specify an organization and description for the CIP. |
CIP preview | Provides a summary panel for you to review your selections. |
If you want to span the image across multiple discs, then specify the maximum size for each part you want to create. Different installation images might have different minimum sizes for spanned images. If you select a size which is too small you are alerted with an error message that indicates the minimum spanned size of that image. Any additional files, scripts, or configuration archives which you have included are all subject to spanning.
Review the customized installation package information and click Finish to build the CIP. If the installation image is spanned, then you are prompted to specify the location of the next disc or image.
The amount of time required to generate the CIP depends on the number of maintenance packages and the number of features that you include in the package.
The Installation Factory logs a completion message in the IF_root/logs/log.txt file when the processing engine is finished.
To use the installation wizard for WebSphere Application Server product CIPs, run the install command in the cip_root/WAS directory.
Alternatively, you can run the command once to augment an existing profile.
For more information, see the topic manageprofiles command.
In a scratch installation of WebSphere Application Server Base or Express edition, a custom standalone profile will be created during the installation.
In a scratch installation of WebSphere Application Server Network Deployment edition, you can select which profile to create during the installation.
For WebSphere Application Server Base and Express, on the Install Sample Applications panel, select the Install profile customizations checkbox.
For WebSphere Application Server Base, if you select the checkbox and you have application server customizations, they will be used. If you do not have customizations, you get a regular application server.
For WebSphere Application Server Network Deployment, the Web Services feature pack, and the Service Oriented Architecture feature pack, perform the following steps:
If the profile that you select has profile customization defined, then the installation wizard will effectively run the manageprofiles command once to do a create and augment. If there is no profile customization defined, you get a regular profile.
If the profile that you create has a configuration archive in it, then it will be imported.
Then copy the file to the target operating system and use the command line interface to start the processing engine and create the customized installation package.
See Creating build definitions for another machine for a description of such a procedure.
After making your changes, validate the build definition document with its XML schema (the Commom.xsd, BaseBuildDefinition.xsd, and BuildDefinition.xsd files located in IF_root/eclipse/plugins/com.ibm.ws.install.factory.base_7.0.0.0/xsd) using a validating XML parser or editor. Then use the command line interface to start the processing engine and create the customized installation package.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |