The Build definition wizard provides a way to include configuration scripts that run after successfully installing the customized installation package (CIP) or before uninstalling the CIP. Such scripts run when the installation is a new installation. If you are updating an existing installation by installing a CIP that includes maintenance, these scripts do not run.
Identify scripts that run after successfully installing the CIP.
Identify scripts that run before uninstalling the CIP during a full uninstall.
Identify the script file.
Identify the directory where the script file resides.
Identify what action to take if a script fails. Valid choices include:
- Fatal error
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)
- JACL scripts
- Jython scripts
- Jar files
The .jar files should have the main class defined in the META-INF/MANIFEST.MF file inside each .jar file.
Scripts are in the cip_uid_root/config/install directory when the CIP is installed. These scripts run as configuration actions after all of the configuration actions run that are in the normal installation procedure.
Select an entry and click Modify to change the file name or the directory path.
Removes selected scripts from the CIP.
Move a script up in the list to make it run earlier than scripts below it.
Move a script down in the list to make it run after scripts above it.
Developing and installing customized installation packages Installing a CIP Using scripting (wsadmin) Build Definition wizard panels Interim fix packages Profile customization