Create customized CIP profiles from the command line

Create customized CIP profiles from the command line

+
Search Tips | Advanced Search

Overview

The Installation Factory allows for customized installation packages (CIP) to be created that bundles...

Installation image
Maintenance packages
Stand-alone appserver configuration archive (CAR)
EARs
User files
Scripts

The resulting bundle is a customized installation package, or CIP.
The installer can use the Profile Management or manageprofiles tools to...

Create CIP profiles
Automatically restore profile customizations 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 SIB. The original SIB configuration is not portable and, therefore, is not included in the CIP.
A CAR is available for an appserver CIP profile only. A special profile template enables the importation of a CAR file into the appserver profile. Use the Profile Management tool to create CIP profiles that accept configuration actions that are included in the CIP. Use the appserver CIP profile when you are restoring a CAR 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 suffixes. 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 CAR, then it will be imported.
The first four environments listed on the Environment Selection panel, which do not have a cip_uid suffixes, are the regular profile types. If you want a regular profile without customizations, select one of these.
The following example creates a customized cell profile.
Create the deployment manager portion of the customized cell profile.
 cd WAS_HOME/bin

./manageprofiles.sh -create
                    -profileName cell_dmgr_name   \
                    -templatePath WAS_HOME/cip/cip_uid/if_augmentingTemplates/cell/dmgr   \
                    -nodeProfilePath WAS_HOME/profiles/cell_appserver_name   \
                    -cellName cell_name   \
                    -nodeName node_name   \
                    -appServerNodeName federated_node_name
Create the appserver portion of the customized cell profile.
 cd WAS_HOME/bin

./manageprofiles.sh -create  \
                    -profileName cell_appserver_name  \
                    -templatePath WAS_HOME/cip/cip_uid/if_augmentingTemplates/cell/default  \
                    -dmgrProfilePath WAS_HOME/profiles/cell_dmgr_name  \
                    -portsFile WAS_HOME/profiles/cell_dmgr_name/properties/portdef.props  \
                    -nodePortsFile WAS_HOME/profiles/cell_dmgr_name/properties/nodeportdef.props  \
                    -cellName cell_name  \
                    -nodeName node_name  \
                    -appServerNodeName federated_node_name
Augment an appserver profile that includes a CAR file
Create the profile from the minimal default template.
 cd WAS_HOME/bin
./manageprofiles.sh -create   \
                    -profileName my_profile   \
                    -profilePath "WAS_HOME/profiles/my_profile"  \
                    -templatePath WAS_HOME/cip/profileTemplates/minimal
Augment the profile using the customizations for the default profile.
 cd WAS_HOME/profiles/my_profile/bin

./manageprofiles.sh -augment   \
                    -profileName my_profile   \
                    -templatePath CIP_HOME/if_augmentingTemplates/default
Augment an appserver profile that does not include a CAR file

Use the regular default template in this two-step procedure:
Create the profile from the default template.
 cd WAS_HOME/bin

./manageprofiles.sh -create   \
                    -profileName my_profile   \
                    -profilePath "WAS_HOME/profiles/my_profile"  \
                    -templatePath CIP_HOME/profileTemplates/default
Augment the profile using the customizations (that do not include a CAR) for the default profile
 cd WAS_HOME/profiles/my_profile/bin

./manageprofiles.sh -augment   \
                    -profileName my_profile   \
                    -templatePath CIP_HOME/if_augmentingTemplates/default
Augment a deployment manager profile
Create the profile from the dmgr template.
 cd WAS_HOME/bin

./manageprofiles.sh -create   \
                    -profileName my_dmgr_profile   \
                    -profilePath "WAS_HOME/profiles/my_dmgr_profile"  \
                    -templatePath WAS_HOME/cip/profileTemplates/dmgr
Augment the profile using the customizations (that do not include a CAR or an EAR) for the dmgr profile.
 cd WAS_HOME/profiles/my_dmgr_profile/bin

./manageprofiles.sh -augment   \
                    -profileName my_dmgr_profile   \
                    -templatePath CIP_HOME/if_augmentingTemplates/dmgr  
Augment a custom profile
Create the profile from the managed template.
 cd WAS_HOME/bin

./manageprofiles.sh -create  \
                    -profileName my_custom_profile  \
                    -profilePath "WAS_HOME/profiles/my_custom_profile" \
                    -templatePath WAS_HOME/cip/profileTemplates/managed
Augment the profile using the customizations for a managed profile.
 cd WAS_HOME/profiles/my_custom_profile/bin

./manageprofiles.sh -augment  \
                    -profileName my_custom_profile  \
                    -templatePath CIP_HOME/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 CAR was imported, then the target profile should be a fully configured clone of the source profile where the CAR was exported.
To create a profile without the exact same customizations, in other words, a normal profile, use the normal profile templates in...
CIP_HOME/profileTemplates

...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 appserver to test your applications.

Related information
Developing and installing customized installation packages
Profile customization
Use CAR files in customized CIP profiles
Creating customized CIP profiles
startNode command
startManager command
startServer command