The Installation Factory allows for a customized installation package (CIP) to be created that bundles an installation image, maintenance packages, previously exported stand-alone application server configuration archives, EARs, user files, and scripts. Note that a feature pack CIP cannot contain configuration archives. An installer can use an existing CIP to install an exact replica of a model application serving environment, with installed maintenance packages, configured profiles, and deployed applications. Installers can use the Profile Management tool in the CIP to create a profile, which automatically restores any profile customizations that are included in the CIP. If you cannot use the Profile Management tool, use the commands described in this topic to create pre-configured profiles.
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 you cannot
use the enhanced Profile Management tool in
the CIP to create and configure profiles, use the manageprofiles command
to perform the task, as described in this topic.
The installer can use the manageprofiles command
to manually create profiles and restore the profile customizations
that are included in the CIP.
See Creating customized CIP profiles for a description of using
the enhanced Profile Management tool,
which is a graphical user interface.
You must have previously installed a CIP to create CIP profiles and restore customizations that are included in the CIP.
If you are restoring a customized profile that uses messaging, you must 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.
A configuration archive is available for an application server CIP profile only. A special profile template enables the importation of a configuration archive file into the application server profile. You cannot create a feature pack CIP with a configuration archive.
CIP Profile Type | Include and Run Scripts | Include and Deploy an Enterprise Archive (EAR) | Include and Restore a Configuration Archive (CAR) | Include and Restore Feature Pack CARs |
---|---|---|---|---|
Deployment manager (dmgr profile) |
Yes | No | No | No |
Stand-alone application server (default profile) |
Yes | Yes | No | No |
After creating a profile and applying the customizations, the target installation should have a profile that is fully configured in the manner as designed by the CIP creator. If a configuration archive was imported, then the target profile should be a fully configured clone of the source profile where the configuration archive was exported.
To create a profile without the exact same customizations, in other words, a normal profile, use the normal profile templates in the app_server_root/profileTemplates directory and do not augment the profiles.
In this information ... | IBM Redbooks, demos, education, and more |