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 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 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 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
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
cip_app_server_root/bin/wasprofile.sh -create -profileName my_profile -profilePath "cip_app_server_root/profiles/my_profile" -templatePath app_server_root/cip/profileTemplates/minimal
cip_app_server_root\bin\wasprofile.bat -create -profileName my_profile -profilePath "cip_app_server_root\profiles\my_profile" -templatePath app_server_root\cip\profileTemplates\minimal
cip_app_server_root/profiles/my_profile/bin/wasprofile.sh -augment -profileName my_profile -templatePath cip_app_server_root/if_augmentingTemplates/default
cip_app_server_root\profiles\my_profile\bin\wasprofile.bat -augment -profileName my_profile -templatePath cip_app_server_root\if_augmentingTemplates\default
Use the regular default template in this two-step procedure:
cip_app_server_root/bin/wasprofile.sh -create -profileName my_profile -profilePath "cip_app_server_root/profiles/my_profile" -templatePath cip_app_server_root/profileTemplates/default
cip_app_server_root\bin\wasprofile.bat -create -profileName my_profile -profilePath "cip_app_server_root\profiles\my_profile" -templatePath cip_app_server_root\profileTemplates\default
cip_app_server_root/profiles/my_profile/bin/wasprofile.sh -augment -profileName my_profile -templatePath cip_app_server_root/if_augmentingTemplates/default
cip_app_server_root\profiles\my_profile\bin\wasprofile.bat -augment -profileName my_profile -templatePath cip_app_server_root\if_augmentingTemplates\default
Use this two-step procedure to augment a deployment manager profile:
cip_app_server_root/bin/wasprofile.sh -create -profileName my_dmgr_profile -profilePath "cip_app_server_root/profiles/my_dmgr_profile" -templatePath app_server_root/cip/profileTemplates/dmgr
cip_app_server_root\bin\wasprofile.bat -create -profileName my_dmgr_profile -profilePath "cip_app_server_root\profiles\my_dmgr_profile" -templatePath app_server_root\cip\profileTemplates\dmgr
cip_app_server_root/profiles/my_dmgr_profile/bin/wasprofile.sh -augment -profileName my_dmgr_profile -templatePath cip_app_server_root/if_augmentingTemplates/dmgr
cip_app_server_root\profiles\my_dmgr_profile\bin\wasprofile.bat -augment -profileName my_dmgr_profile -templatePath cip_app_server_root\if_augmentingTemplates\dmgr
Use this two-step procedure to augment a custom profile:
cip_app_server_root/bin/wasprofile.sh -create -profileName my_custom_profile -profilePath "cip_app_server_root/profiles/my_custom_profile" -templatePath app_server_root/cip/profileTemplates/managed
cip_app_server_root\bin\wasprofile.bat -create -profileName my_custom_profile -profilePath "cip_app_server_root\profiles\my_custom_profile" -templatePath app_server_root\cip\profileTemplates\managed
cip_app_server_root/profiles/my_custom_profile/bin/wasprofile.sh -augment -profileName my_custom_profile -templatePath cip_app_server_root/if_augmentingTemplates/managed
cip_app_server_root\profiles\my_custom_profile\bin\wasprofile.bat -augment -profileName my_custom_profile -templatePath cip_app_server_root\if_augmentingTemplates\managed
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 apply to any profiles that you create with the enhanced templates and augment with the Installation Factory customizations.
To create a profile without the exact same customizations, in other words, a normal profile, use the normal profile templates in the cip_app_server_root/profileTemplates directory and do not augment the profiles.
What to do next
After installing your customized system, install a Web server and plug-ins, if necessary, and start the deployment manager, the node agent, and the application server to test your applications.Related information
Developing and installing customized installation packages
Profile customization
Configuration archive files
Creating customized profiles
startNode command
startManager command
startServer command