The Installation Factory allows for a customized installation package (CIP) to be created that bundles an installation image, maintenance packages, previously exported standalone 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.
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 Profile Creation wizard, use the wasprofile command to restore the customized profiles as described in Creating customized CIP profiles from the command line.
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 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.
You cannot restore a CAR enabled with a feature pack using a CIP at this time. The only available profile type which can be restored in a CIP is an unaugmented stand-alone application server profile.
Profile Creation wizard | Location | Creates Customized Profiles? | Creates Normal Profiles? |
---|---|---|---|
Enhanced IF version | Launch the Profile Creation wizard check box at the end of the CIP installation. (cip_app_server_root/ProfileCreator/) | Yes | No * |
Enhanced IF version | cip_app_server_root/ProfileCreator/ | Yes | No * |
Product version | cip_app_server_root/bin/ProfileCreator/ | No | Yes |
Profile version | cip_app_server_root/profiles/profile_name/bin/ProfileCreator/ | No | Yes |
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.
CIP Profile Type | Include and Run Scripts | Include and Deploy an Enterprise Archive (EAR) | Include and Restore a Configuration Archive (CAR) |
---|---|---|---|
Deployment manager (dmgr profile) |
Yes | No | No |
Stand-alone application server (default profile) |
Yes | Yes | Yes |
Custom (managed profile) |
Yes | No | No |
After creating the profile and restoring the customizations, the installation should have a profile that is configured like the profile in the model product installation that was the pattern for the CIP. Existing customizations for a profile template apply to any profiles that you create with the enhanced Profile Creation wizard.
To create a profile without the exact same customizations, in other words, a normal profile, use the normal product Profile Creation wizard in the cip_app_server_root\profiles\profile_name\bin\ProfileCreator directory.
In this information ... | IBM Redbooks, demos, education, and more(Index) |