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. 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 specialized Profile creation wizard in the CIP to create a stand-alone application server, deployment manager, or managed profile, which automatically restores any profile customizations that are included in the CIP. If you cannot use the specialized Profile creation wizard, use the commands described in this topic to create pre-configured profiles.
The installer can use
the enhanced Profile Creation wizard in the
CIP to create profiles and automatically restore the profile customizations
that are included in the CIP. Or, the installer can use the wasprofile command
to perform the same tasks manually from the command line.
If you cannot
use the enhanced Profile Creation wizard in
the CIP to create and configure profiles, use the wasprofile command
to perform the task, as described in this topic.
See Creating customized CIP profiles for a description of using
the enhanced Profile Creation wizard,
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.
Configuration archives are available for use in a CIP only when WebSphere Application Server Network Deployment is bundled with maintenance at the Version 6.0.2.5 level or higher. As you might expect, the configuration archive file must export from a system that has maintenance applied at a maintenance level of Version 6.0.2.5 or higher.
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.
Use the enhanced Profile Creation wizard to create profiles that accept configuration actions that are included in the CIP. Use the minimal default profile template to create an application server when you are restoring a configuration archive file. If the customizations do not restore a CAR, the normal application server template creates the application server profile. Either type of application server profile accepts other configuration actions in the CIP that might deploy EAR files and run scripts.
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(Index) |