The Build definition wizard provides a way to include profile customizations that include scripts to run at profile creation or deletion, deploying one or more enterprise archive (EAR) files, and restoring one configuration archive file.
EAR files are deployed with default deployment options. If deploy an EAR file with different options, then simply include the EAR file as a user file. Then 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 (CAR) is an exported configuration file from an existing standalone application server profile. Use the AdminTask command scripting interface to create the configuration archive.
Specifies whether the Profile Management tool displays options to use the customizations to create new profiles or augment existing profiles.
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.
Select Allow augmentation of existing profiles using the customizations to allow the Profile Management tool to list all available profile types to be augmented using your customizations.
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.
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.
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.
Action Type Specifies one of the following types of configuration actions:
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 Specifies what action to take if a script fails or a file cannot be loaded. The following choices are valid:
Opens a browse dialog where you can search for and select an enterprise application archive (EAR) file to include in the CIP for an application server 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.
Opens a browse dialog where you can search for and select a configuration archive file to include in the CIP for an application server profile.
A configuration archive file is an exported configuration file from an existing stand-alone application server 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 sthis configuration, including any enterprise archive (EAR) files, can be reliably restored to multiple nodes. Importing a configuration archive also offers some performance advantages over creating a stand-alone application server in the typical 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.
See Administrative command invocation syntax for a description of using an administrative command. See Commands for the AdminTask object for a description of the exportServer, exportWasprofile, importServer, and importWasprofile commands that are available for the AdminTask object.
See Administrative command invocation syntax for a description of using an administrative command. See Commands for the AdminTask object for a description of the exportWasprofile and importWasprofile commands that are available for the AdminTask object.
Modify
Specifies an entry that changes 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
Moves a script, enterprise archive file, or the configuration archive file higher in the list to make that item run earlier than lower actions in the list.
Move Down
Moves a script, enterprise archive file, or the configuration archive file lower in the list to make that item run after higher actions in the list.