Create customized CIP profiles

Create customized CIP profiles

Customizing a CIP profile refers to creating a customized installation package (CIP) with the IBM WebSphere Installation Factory that bundles an installation image and maintenance packages, but can also contain previously exported standalone appserver configuration archives (CARs), enterprise apps, user files, and scripts. After a CIP is installed we can create a new profile using the customized template for a repeatable, tailored profile solution. Customizing a CIP profiles differs from the custom profile type, which is an empty node designed to be federated into a cell.
The installer can use the Profile Management Tool to create CIP profiles and automatically restore the profile customizations that are included in the CIP. Or, the installer can use the manageprofiles command to perform the same tasks manually from the command line.
If we cannot use the Profile Management Tool, use the manageprofiles command to restore the customized profiles as described in .
You must have previously installed a CIP to create CIP profiles and restore customizations that are included in the CIP.
If we are restoring a customized profile that uses messaging, also include a script to configure the service integration bus (SIB). The original SIB configuration is not portable and, therefore, is not included in the CIP.

The QEJBSVR user profile must have proper authority to the files and directories involved to run any customized scripts which read or write from the file system.

If you include any customized shell scripts for UNIX operating systems, you must add #!/bin/sh as the first line of the script or the script will fail to run. The series of configuration events for using a configuration archive and other CIP customizations is shown in the following example:

Install the appserver.
Create a default (standalone appserver) profile, deploy applications, and make other configuration changes.
Optionally create a configuration archive of the default profile using wsadmin:

./wsadmin.sh -conntype NONE -c "\$AdminTask exportWasprofile {-archive myarchive.car}"

Avoid trouble: Be sure that \ is in front of $AdminTask

wsadmin.bat -conntype NONE -c "$AdminTask exportWasprofile {-archive myarchive.car}

The first steps above are optional and are only required if a configuration archive needs to be exported for inclusion in a CIP. If configuration archive customization is not required, then the steps above can be omitted.
Use the Installation Factory to create a CIP that includes the appserver product image.The CIP optionally includes a refresh pack as well as a fix pack.

Include scripts to run during install time or uninstall time.
Optionally include the configuration archive in the CIP for a standalone appserver configuration.
Optionally include additional files to be installed on the system.

Distribute the CIP to installers who require the pre-configured system for their users.
Install the CIP.

A configuration archive is available for an appserver CIP profile only. A special profile template enables the importation of a configuration archive file into the application server profile. We cannot create a feature pack CIP with a configuration archive. Use the Profile Management Tool to create CIP profiles that accept configuration actions that are included in the CIP. Use the appserver CIP profile when we are restoring a configuration archive file or other customizations. The Profile Management Tool can also create normal profiles that do not accept customizations.

When you run the Profile Management Tool with CIP customized profiles installed, the Environment Selection panel will show environments with -- at the end. These are the customized profiles, and each of them will create a regular profile and then apply the customizations through a profile augmentation. If the customized profile that you select contains a configuration archive, then it will be imported.
The environments listed on the Environment Selection panel, which do not have a -- at the end, are the regular profile types. If you want a regular profile without customizations, select one of these.

Create and augment an appserver profile that does not include a CAR file.
Choose the appserver profile in the enhanced Profile Management Tool. The Profile Management Tool uses the appropriate profile template to create an appserver that does not require the CAR, but that still accepts other customizations.
The Profile Management Tool automatically augments a CIP profile with any customizations that exist for the profile type.

Results

After creating the profile and restoring the customizations, the installation should have a profile configured like the profile in the model product installation that was the pattern for the CIP. Existing customizations are used only when creating a CIP profile with the Profile Management Tool.

Next steps
After installing the customized system, install a Web server and plug-ins, if necessary, and start the appserver to test the applications.

Related tasks

Related information

Last updated Nov 11, 2010 1:01:09 PM CST