Profile customization
The Build definition wizard provides a way to include profile customizations which include scripts to run at profile creation or deletion, deploying one or more EAR files, and restoring one configuration archive (CAR) file.
EAR files are deployed with default deployment options. If deploying an EAR file with different options, include the EAR file as a user file, and include a script to deploy the EAR file.
Scripts can run at profile creation or deletion time in the order you specify. A script can call other scripts that you can include as user files.
A configuration archive file is an exported configuration file from an existing stand-alone appserver profile. Use the AdminTask command scripting interface to create the configuration archive.
- Profile creation
- Identify scripts that run or files to include after successfully installing the CIP.
Perform such actions as running scripts, including and restoring a configuration archive, including an EAR file, and deploying the applications within an EAR file.
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.
- Profile deletion
- Identify 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 “undo” the customization actions that occurred at profile creation time. If there are any profile deletion time configuration actions to run, the file...
CIP_HOME/if_augmentingTemplates/deleteRegistry.xml...contains the configuration actions.
The manageprofiles command should normally unaugment any IF customized augments when deleting a profile.
- Action Type
- Identify the type of configuration action:
- Run a script
- Import a configuration archive
- Deploy an enterprise archive
- File Name
- Identify scripts, enterprise archive files, or the configuration archive file.
- Directory Path
- Identify the directory that contains scripts, enterprise archive files, or the configuration archive file.
- Failure Action
- Identify what action to take if a script fails or a file fails to load. Valid choices include:
- Fatal error
- Continue
- Add scripts
Opens a file browsing dialog window where you can search for and select scripts to include in the CIP. Scripts can be any of the following supported script types:
- ANT scripts (*.ant)
- Windows batch files (*.bat)
- Shell scripts (*.sh)
- JAR files (.jar)
- JACL scripts (.jacl)
- Jython scripts (.py)
- Add enterprise archives
- Opens a browse dialog where you can search for and select an EAR file to include in the CIP for an appserver profile.
- Add configuration archives
- Opens a browse dialog where you can search for and select a configuration archive file to include in the CIP for an appserver profile.
A configuration archive file is an exported configuration file from an existing stand-alone appserver profile. Use the AdminTask command scripting interface to create the configuration archive.
The configuration archive contains all of the configuration data for a stand-alone application server, including security settings, resources, defined ports, and so on. The advantage of using a configuration archive is that all of this configuration, including any EAR files, can be reliably restored to many nodes. Importing a configuration archive also offers some performance advantages over creating a stand-alone appserver in the normal way.
See Creating customized CIP profiles from the command line for information about using the command line to create and restore profiles when you cannot use the enhanced Profile Management tool in the CIP.
- Modify
- Select an entry and click Modify to change the file path and file name or the directory path and directory name.
- Remove
- Removes selected scripts, enterprise archive files, or the configuration archive file from the CIP.
- Move Up
- Move a script, enterprise archive file, or the configuration archive file up in the list to make it run earlier than other actions below it.
- Move Down
- Move a script, enterprise archive file, or the configuration archive file down in the list to make it run after other actions above it.
Related information
Build Definition wizard panels
Install and uninstall scripts
Additional files
Use configuration archive files in customized CIP profiles
Create customized CIP profiles from the command line
Develop customized installation packages