You can use the profile customization panel to run scripts at profile creation or deletion time. You can also deploy one or more enterprise archive file (EAR) file as part of profile augmentation.
Select Allow creation of new profiles using the customizations to allow the Profile Management Tool to list all available profile types to be created using your customizations.
In the section entitled Profile_type Customizations (where Profile_type is the type of profile you are working with) you can specify the customizations that you want to make on profile creation or deletion.
Specifies scripts that run or files to include after successfully installing the CIP.
Perform such actions as running scripts, including and restoring configuration archives, including enterprise archive (EAR) files, and deploying applications within an EAR file.
Specifies scripts that run when the profile is unaugmented.
At profile deletion time, the CIP can specify additional scripts to run. Generally, these scripts are needed to reverse the customization actions that occurred at profile creation time. If there are any profile deletion time configuration actions to run, then the cip_app_server_root/if_augmentingTemplates/deleteRegistry.xml file contains the configuration actions. The manageprofiles command typically unaugments any Installation Factory customized augments when deleting a profile.
/usr/IBM/WebSphere/ProcServer/cip/cip_uid
/opt/IBM/WebSphere/ProcServer/cip/cip_uid
/opt/ibm/WebSphere/ProcServer/cip/cip_uid
/opt/IBM/WebSphere/ProcServer/cip/cip_uid
C:\Program Files\IBM\WebSphere\ProcServer\cip\cip_uid
/QIBM/ProdData/WebSphere/ProcServer/V61/ND/cip/cip_uid
The cip_uid variable is the CIP unique ID generated during creation of the build definition file. You can override the generated value in the Build definition wizard. Use a unique value to allow multiple CIPs to install on the system.
Action Type
File Name
Specifies scripts, enterprise archive files, or the configuration archive file.
Directory Path
Specifies the directory that contains scripts, enterprise archive files, or the configuration archive file.
Failure Action
Opens a browse dialog where you can search for and select an enterprise application archive (EAR) file to include in the CIP for aWebSphere® ESB profile.
An EAR file is a enhanced Java™ archive (JAR) file, defined by the J2EE standard used to deploy J2EE applications to J2EE application servers. An EAR file contains enterprise beans, a deployment descriptor, and Web archive (WAR) files for individual Web applications.