Create customized CIP profiles from the command line

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 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 manageprofiles command to manually create profiles and restore the profile customizations that are included in the CIP.

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, 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.

Overview

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 Profile Management tool to create CIP profiles that accept configuration actions that are included in the CIP. Use the application server CIP profile when you are restoring a configuration archive file or other customizations. The Profile Management tool can also create normal profiles that do not accept customizations.

• When you run the Profile Management tool with CIP customized profiles installed, the Environment Selection panel will show environments with -- cip_uid at the end. These are the customized profiles, and each of them will create a regular profile and then apply the customizations through a profile augmentation. If the customized profile that you select contains a configuration archive, then it will be imported.

• The first four environments listed on the Environment Selection panel, which do not have a -- cip_uid at the end, are the regular profile types. If you want a regular profile without customizations, select one of these.

Table 1. Allowed customizations

CIP Profile Type	Include and Run Scripts	Include and Deploy an Enterprise Archive (EAR)	Include and Restore a Configuration Archive (CAR)
Cell (deployment manager and a managed node)	Yes	No	No
Deployment manager (dmgr profile)	Yes	No	No
Stand-alone application server (default profile)	Yes	Yes	Yes
Custom (managed profile)	Yes	No	No

Procedure

• Augment an application server profile that includes a CAR file.

  1. Create the profile from the minimal default template.

     cip_profile_root/bin/manageprofiles 
     -create 
     -profileName my_profile 
     -profilePath "cip_profile_root/profiles/my_profile"
     -templatePath cip_user_data_root/cip/profileTemplates/minimal
     

  2. Augment the profile using the customizations for the default profile.

     cip_profile_root/profiles/my_profile/bin/manageprofiles 
     -augment 
     -profileName my_profile 
     -templatePath cip_profile_root/if_augmentingTemplates/default
     

• Augment an application server profile that does not include a CAR file.

  Use the regular default template in this two-step procedure:

  1. Create the profile from the default template.

     cip_profile_root/bin/manageprofiles 
     -create 
     -profileName my_profile 
     -profilePath "cip_profile_root/profiles/my_profile"
     -templatePath cip_profile_root/profileTemplates/default
     

  2. Augment the profile using the customizations (that do not include a CAR) for the default profile.

     cip_profile_root/profiles/my_profile/bin/manageprofiles 
     -augment 
     -profileName my_profile 
     -templatePath cip_profile_root/if_augmentingTemplates/default
     

• Augment a deployment manager profile.

  Use this two-step procedure to augment a deployment manager profile:

  1. Create the profile from the dmgr template.

     cip_profile_root/bin/manageprofiles 
     -create 
     -profileName my_dmgr_profile 
     -profilePath "cip_profile_root/profiles/my_dmgr_profile"
     -templatePath cip_user_data_root/cip/profileTemplates/dmgr
     

  2. Augment the profile using the customizations (that do not include a CAR or an EAR) for the dmgr profile.

     cip_profile_root/profiles/my_dmgr_profile/bin/manageprofiles 
     -augment 
     -profileName my_dmgr_profile 
     -templatePath cip_profile_root/if_augmentingTemplates/dmgr
     

• Augment a custom profile.

  Use this two-step procedure to augment a custom profile:

  1. Create the profile from the managed template.

     cip_profile_root/bin/manageprofiles 
     -create 
     -profileName my_custom_profile 
     -profilePath "cip_profile_root/profiles/my_custom_profile"
     -templatePath cip_user_data_root/cip/profileTemplates/managed
     

  2. Augment the profile using the customizations for a managed profile.

     cip_profile_root/profiles/my_custom_profile/bin/manageprofiles 
     -augment 
     -profileName my_custom_profile 
     -templatePath cip_profile_root/if_augmentingTemplates/managed
     

Results

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 cip_app_server_root/profileTemplates directory and do not augment the profiles.

What to do next

Related information