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 EAR files, and restoring one configuration archive (CAR) file.

Restore a configuration archive to help configure a new stand-alone application server profile. We can also deploy EAR files on stand-alone application server profiles.

Customizations occur when you use the enhanced Profile Creation wizard included in the CIP to create a profile type that has a customization. The enhanced CIP tool implements the customizations automatically.

EAR files deploy with default deployment options. If deploy an EAR file with different options, 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 we can include as user files.

See Creating customized CIP profiles from the command line for information about using the command line to create and restore profiles when we cannot use the enhanced Profile Creation wizard in the CIP.

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 service integration bus (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 cip_app_server_root/if_augmentingTemplates/deleteRegistry.xml file contains the configuration actions. The wasprofile command should normally unaugment any IF customized augments when deleting a profile.

Action Type

Identify the type of configuration action:

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:

Add Scripts...

Opens a file browsing dialog window where we can search for and select scripts to include in the CIP. Scripts can be any of the following supported script types:

Add Enterprise Archives...

Opens a browse dialog where we 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 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.

Add Configuration Archive...

Opens a browse dialog where we 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.

Creating a profile using the enhanced Profile Creation wizard in the CIP automatically restores the configuration archive. Each stand-alone application server profile that you create with the CIP tool creates a profile with the restored configuration archive. Use the Profile Creation wizard under the under app_server_root/bin/ProfileCreator directory to create a stand-alone Application Server without 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 application server in the normal way.

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.

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 Configuration archive files Creating customized CIP profiles from the command line Developing and installing customized installation packages