The Installation Factory captures the configuration of an existing application server profile and bundles it with an installation image, maintenance packages, and user files and scripts. The resulting bundled model enivronment is a customized installation package, or CIP. An installer can use a CIP to install an exact replica of the model application serving environment, with identically installed maintenance packages, configured profiles, and deployed applications.
Before you begin
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 Network Deployment is bundled with maintenance at the V6.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 V6.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.
Why and when to perform this task
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 in V6.0.2.5 and later versions 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) |
---|---|---|---|
Stand-alone application server (default profile) |
Yes | Yes | Yes |
Deployment manager (dmgr profile) |
Yes | No | No |
Custom (managed profile) |
Yes | No | No |
Steps for this task
Choose the application server profile in the enhanced Installation Factory version of the Profile Creation wizard.
The Profile Creation wizard automatically augments the profile with any customizations that exist for the default application server profile.
Choose the application server profile in the enhanced Profile Creation wizard. The Profile Creation wizard uses the appropriate profile to create an application server that does not require the CAR, but that still accepts other customizations.
The enhanced Profile Creation wizard automatically augments the profile with any customizations that exist for the application server profile.
Choose the deployment manager profile in the enhanced Installation Factory version of the Profile Creation wizard.
The enhanced Profile Creation wizard automatically augments the profile with any customizations that exist for the deployment manager profile.
Choose the custom profile in the enhanced Installation Factory version of the Profile Creation wizard.
The enhanced Profile Creation wizard automatically augments the profile with any customizations that exist for the custom profile.
Result
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.
Related information
Developing and installing customized installation packages
Profile customization
Configuration archive files
Creating customized CIP profiles from the command line
startNode command
startManager command
startServer command